Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

What does Muxer BitRate too high really mean?

My lip synch thread has morphed into this, and I really need some help here.
"Muxer Bit Rate too high" is really just a general error isn't it- I mean changing the rates has very little bearing on anything. All the clips on the timeline have been compressed with Compressor at standard rates anyway, the whole project is only 10minutes long. My current problem is that my project just won't build, but it gets so close. Latest incarnation ends with a jpeg and this is the thing that seems to be causing the problem now, even though the image has been used before without a problem.

PowerBook G4

Posted on Feb 19, 2008 10:38 AM

Reply
19 replies

Feb 22, 2008 6:15 AM in response to James Forbes

Have you tried running Diskwarrior or Hardware tests to see if that helps or something is going on from that end? As an aside (and sounds like not related) what were the video encoding rates? Just went back through the thread and did not see it. May still be related to that, though doubtful...

I have run into a similar issue on one of my machines where DVD SP 3 started acting strange periodically and DiskWarrior would help for a bit. Was not consistent in the little gotchas and I think something became corrupted (or continues to get corrupted) or I added some update I did not realize along the way, may have been a QuickTime (not sure which one you are running, but one version of QT was strange, also as an aside DO not upgrade QT as a fix. 7.4 seems to have issues in general, 7.4.1 fixed some, but on my main machine I am running an older one 7.1 or so.) DVD SP on 10.3.9 for me was overall very stable, it was Tiger when I ran into DVD SP 3.02 issues, and only more recently.

DVD SP 4 would open the same projects on the same machine (4.03) and also other computers running flavors of DVD SP 4 would work. The kicker was DVD SP 3 on a clean install of the OS and software would work (which meant probably not a hardware issue). Do not know if you have a partitioning utility or a FW drive you can install a clean OS and copy of DVD SP 3 to see if that works for you as a test. A bit of a pain, but it will give you an idea if it is system related somehow, becuase I think you went through the main troubleshooting steps so far.

It may still be related to an actual corrupt asset but does not sound like that..

Feb 22, 2008 7:13 PM in response to Drew13

Hey Guys,

One of the things I have noticed with Apple's Compressor MPEG-2 (DVD) *.m2v files is that at the end of the video, the bit rate falls off the chart with MPEG analyzers. This is inherent in Compressor, Main Concept, Optibase and the good ole' Spruce MPX 3000.

Although audio bit rate does have a direct correlation with video bit rate on your mux, it seems that James Forbes did all the right trouble shooting techniques.

One of the things that I didn't notice him mention is saving to a different volume. Also James, were you compressing the JPEG in the DVD SP timeline? I only ask because DVD SP has it's own built-in compression settings (albeit it uses the Compressor's engine).

It would make sense that you can view your partially multiplexed *.VOB in MPEGStreamClip, since a program stream in it's very nature builds as it's being written (unlike transport streams).

The wrench in this fascinating equation is that on another Mac, the project muxes with no problems.

I would say try muxing to a different directory. If that doesn't work, use your friends machine for all your projects (kidding).

Believe it or not, I am coming to same conclusion that James has about the "BitRate Too High" error.

Mikey M. 🙂

Feb 22, 2008 8:06 PM in response to Mikey M.

Mikey, dude how are you?

Mikey M. wrote:


One of the things that I didn't notice him mention is saving to a different volume.


You know something I have some weirdness when saving/building to different volumes where I chalked it up to related to permissions or files not copying properly. I also thought there may be something related to which computer/compressor version I was using and if I moved to build the project on another computer. Kind of nebulous and I did not go too far trying to track it down.

The wrench in this fascinating equation is that on another Mac, the project muxes with no problems.


Fascinating is not the word I would use, but I get the idea 😉

What does Muxer BitRate too high really mean?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.