-
render files – causing problems in playback
hey, i did a cursory search, didnt find any threads on this.
i am having problems with rendered regions having a memory of what was rendered there before, even after rolling new footage into the space on the timeline where the previously used/rendered source footage sat on the timeline. The only trick is just to nuke the whole sequences render files. that worked this time, but in the future with a client in there or with long slow-to-render 1080 sequences, this will be a huge drag.
does that make sense. this is at the studio where i work, and it reminds me of my freelance days where a similar problem, where even at dv25 resolution, video play back would freeze whenever the playhead would hit or come off of the grey rendered footage bar.
what is the consensus on this? is fcp just not great at handling rendered files, has anyone seen these problems?
if there is a document at one of the many sweet fcp/dv sites, by all means, send me there. this is probably the most buggy part of a generally solid app, to me at least.
thanks
-
3 Replies
-
I’ve seen this in rendered transitions before, when copying a clip that has an end in a transition (only selecting the clip, not any portion of the transition), when pasted, the portion of that clip that was in the transition would play back the transition render files up to the end of the clip,, even after re-rendering. The only way around this that i’ve found is to right click and “remove attributes,” then re-render. You dont need any of the box’s checked off,, just leave them blank and click OK.
still leaves you with the headache of having to re-render the clip though…
Colin McQuillan
Vancouver BC -
Ya know I run into this the render-memory thing from time to time in both audio and video. The way I work around it is to highlight the offending clip in the timeline then move the clip left or right a few frames then back. I find it easiest to use the bracket keys to perform this. Normal keystroke would be Shift-Left bracket, then Shift-Right bracket – MOST of the time it dislodges the stuck render.
Hope this helps.It would be nice if this were fixed or at least if there was a tool or command to verify render files…
jason
-
I have seen this (although not in a while and it usually happens when copy/pasting from other timelines). The easiest way to dislodge a render from clip is to select it in the timeline and the hit control-b to disable that clip and then control-b to re-enable. That should shake loose any renders. What happens is that the render files are named after the sequence, and if you then copy and past that render file into a newly named sequence, FCP seems to get wigged out.
Here’s to a more robust FCP database.
Jeremy
Reply to this Discussion! Login or Sign Up