Adobe Premiere CS6 & Media Encoder: Unkown Error

OddBirdman

Carbonite Member
I had an adventure in learning how much I don't know about rendering today. Ever since I've upgraded to CS6 from 5.5 the freeze ups during editing have been replaced by the 'Unknown Error when rendering.' My particular issue has been rendering .wmv files. I don't like the black bars around the .avi format, and stretching the film reduces the quality. I'm sure there is some way around this but I have no idea.

I tried rendering the piece 8 times in various formats, search through all the forums looking for solutions. Sometimes all it takes is a restart. Other times you can copy the timeline and then past it into a new sequence. I didn't like the look of the finished piece of film. I tried moving over to Media Encoder as a stand alone. I was introduced the fact that my computer has an audio sample of a sheep on it. When it fails it goes "Baaaaaaahaha."

I tried modifying the frame rate of the whole project to 29.97 but that didn't work either. I exported the whole finished piece to a P2 clip, and tried rendering that. I still got the error. I tried converting the .mxf and the .avi to .wmv in an external convertor which left me with interlaced film. Usually the error is caused by a bad effect somewhere on the timeline. It can also be caused by the Auto-save.

In the end the solution was to run it through Media Encoder, using one variable bit rate pass, and then wait for it to fail. It shows thumbnails of the progress so you can see the exact frame in the footage that is causing the hang up. I found the bad section of frames, removed them - which changed the end result a but from what I had intended.

I've had this problem consistently with this machine. I wish Adobe would put out a patch for that problem. I ended up spending 8 hours rendering something that only supposed to take take 25 minutes. There is scattered information out there of how to fix this. Anyone else come up with alternative solutions to this problem do the end film doesn't have to change?
 
This doesn't sound like something that a software patch ever could fix. Particilarly since PPro5.5 and 6 both failed, but in different ways. I'd be looking for overheating, or a bad memory module - I.e., a hardware fault that kicks in when the processor is working hard.
 
This is the first period of time I have ever had this problem. With 5.5 the renders would freeze occasionally, but that was very rare. Since it's only with a particular file type - on my system .wmv - and much larger renders in other formats don't have the same problem I'm wary to blame it on a memory failure. About month ago I had a memory module go bad. I ran 3rd party memory diagnostics which isolated the bad stick of RAM. Running it now shows my system is working correctly. When I say software patch I mean it would be nice for them to assign an error code, or some form of timeline diagnostic that can isolate the bad frame, or show the moment in the timeline where the footage is corrupt. I have a video posted in the new members section of the guy who is dancing next to a newspaper box that - on my old system - would cause the render to fail. For that piece of film I didn't need the whole clip so I trimmed the ends off of it. Now I am able to use it. There is information about the error on the Adobe site so it's a known issue. The last time it happened to me I was using the warp stabilizer. Removing the effect solved the issue. I also have one piece of footage in .mxf format from a previous project that I have never been able to use because the file is corrupt for some unexplained reason. When I was using Media Encoder on 2 pass variable bit rate it would make it through the first pass. The second pass would then fail in some arbitrary place that wasn't related to where the bad piece of footage was located. I was surprised where the bad frames were because the particular piece of footage - which has been a part of almost ever piece of film I have ever put out because it's an "opening credits" piece for Wayward Traveler - but clipping the ends off the file seems to have fixed the problem. I'd be interested to see if the same timeline on another system would cause the error or if it's just related to this machine specifically.
 
Back
Top