This content has been marked as final. Show 10 replies
Okay, I rendered another part of it and now I'm getting an error message:
After Effects error: Flushing file "filename.mov" - bad file reference-number (-51)
Anyone care to translate?
I have some blurb on this for image sequences on my site (http://www.mylenium.de/ae_errors/ae_errors_0-5.html) but that does not apply here, so the case must be different. Could you provide some more info on the output settings and possibly the source footages?
Well, it's not a memory issue... I just rendered at quarter rez and it failed.
I have one 1080p ProRes video layer and the rest are just layered Photoshop and Illustrator files. (no image sequences). The weird thing is that this project is based on a project I did last week that rendered perfectly.
I'm going to see if there's some layer has an in-point at that time index. It must be having trouble reading it from disk or loading into memory.
--Just checked my precomp timelines. There is one comp in-point five frames away from the fail point.
Well, i could never figure it out and the project was due yesterday. So I took the last frame and the first frame and dissolved them together to make the missing frame that wouldn't render.
has anyone seen this error message:
error making movie:bad parameter
Usually, you have to scold the parameter, and then it listens.
What kind of source footage are you using? What are your project/comp/machine/OS details?
In the future, it might help to start a new thread specific to your topic.
As Steve said: Please provide more info or this is going nowhere. Most likely you are using an resolution, framerate or audio sample rate with a CoDec that does not allow to mix these settings, but more specific info would help to track this down more clearly.
This problem has popped up again. Very annoying. Looked for any corrupt frames at the fail point and can't find anything wrong with my source files (All image sequences of TIFFs). My RAM Preview also fails on this frame. Just stops. No error, no nothing.
Use might have to solo each layer at that specific point and try to do a RAM Preview, turn off all effects as well until you find what is causing it.
- Jonas Hummelstrand
Yeah -- I found it. It was one corrupt frame in 26,000 frames. It made Photoshop and GraphicConverter crash when I tried to open it.