@ blenderman911 – I’m also having some unexpected difficulty with 2.57rc2. Using specs I used successfully in 2.56beta, I can’t get anything, either – the error message (in the Info menu bar at the top of the UI), reports “Cannot initialize video stream” no matter what selection of settings I use under MPEG. I assumed 2.57 would work the same but apparently not. Unfortunately I ditched my version of 2.56beta but will d/l & try it just to confirm that this seems to be a new issue.
That error usually points to a missing codec problem, but I know I have the needed codecs for the formats I tried.
Sorry about the confusion, that’s just life as usual in Blenderland, especially during a development cycle.
EDIT: I did a few tests and found out one thing for sure – 2.57rc crashes more often when using the VSE than any other version I’ve yet used. It’s ridiculous. Nine times out of ten, after successfully writing a muxed file out, I switch codecs, hit “Animation” and boom, crash city. That is completely annoying. No reason switching to a different codec should cause that behavior.
And other behavior is very puzzling. I was able to use the following specs to successfully write a muxed file:
DVD preset with AC3 audio
AVI with MPEG-4 video codec and MP3 audio
Quicktime with MPEG-4 video codec and MP3 audio
I could not use the Xvid or H.264 video codecs without getting the error message noted above. This is very strange because when not using MPEG for muxed output, I can write silent AVI with the Xvid codec, and silent Quicktime with the H.264 codec. I know these codecs are on my system, as I have used them with other apps than Blender.
I really think Blender’s management of such resources as codec libraries is very weak and inconsistent. The whole subject is confusing enough without creating even more puzzlement.