-
Previously rendered section of sequence becoming unrendered
Recently a final cut pro project has begun exhibiting strange behaviour in rendering. First off when the project was opened, Final Cut sent a message reporting 100 offline media all of which were render files. A doublechecking of the workflow confirmed that everything was where it ought to be and there was no reason that files should be missing. Nonetheless it was necessary to regenerate all 100 files. At one stage in this process it was reported that there wasn’t enough memory for the job, which is very odd as there certainly would have been. One theory I have regarding this is that perhaps it was because many sequences were open at one time but worse has been seen in this regard on lesser machines and without incident. Fortunately this problem has not re-occurred but now there is one strange thing left.
One section of one sequence in the project has an unrendered red line over it. There are several layers of video so it’s hard to pinpoint if there’s any problems with the source media in this section of the sequence but a ‘reveal in finder’ check of every clip that is partly or entirely covered by this section of the sequence doesn’t seem to show any problems with their having somehow been corrupted or deleted or linked to a different location to all the rest of the project media.
Rendering again will successfully render this section but any changes made to the project that require rendering will result in a red line over the newly edited section as expected and the red line appearing over that same section as before. Any changes made to the project cause this section to revert to unrendered no mater how recently a render has been performed.
Trashing the preferences hasn’t helped, the media is all where it should be and the initial problem of offline media has not happened again. Also, the unrendered section is not reporting any offline media either, just unrendered. It’s very weird.
-
2 Replies
-
Is there a piece of media in that section that is h.264 or some flavor of .mp4? Or is there audio there that is not 48khs, 16bit stereo, .aif? Either of those will often cause what you’re talking about. Just something for you to check out.
Tony Brittan
Island Shore Productions
Posted from my iPhone -
Interesting thought, just checked. All footage is Apple Pro res 422 and the audio is .m4a AAC format 44.1 KHz 32 bit floating point. Why it’s in .m4a I don’t know and that’s probably not ideal, but it wasn’t presenting itself as a problem before.
I tried trashing the preferences when the problem first occurred on Friday but this didn’t help. This morning I opened up the project to double check what you were saying about the audio and video and it’s miraculously fixed itself. I guess I should point out that the project was in it’s later stages and that this problem had not occurred before friday. It’s good that it’s working now, though I hope it’s not due to happen again. If anyone thinks they know what caused this I’d appreciate the help.
Reply to this Discussion! Login or Sign Up