(Note: all the video I shot for this project was in front of a green screen and then the green was keyed out with ultrakey).
I have a 20-second frame hold in my top video layer (V9). There is some motion animation in the first 5 seconds of the frame hold. Then another sequence begins in a lower video layer (V3). When the V3 layer sequence begins, the V9 layer immediately goes blank, even though in the timeline the frame hold is still going on for 15 more seconds and the V9 layer is obviously on a higher layer. I have tried deleting and re-adding the frame hold, adding more motion keyframes to trick Premiere into keeping the layer visible, shutting down premiere, shutting down my Mac.
Could my V3 layer somehow be set to not allow video in other layers?
Any help would be appreciated.
Just to check - are you preview rendering at the point where V9 goes blank. If not try preview rendering that section to see if it appears once rendered.
Thank you very much for your reply! This in combination with another reply solved the problem.
sometime it's simpler to export a still frame (in a format that supports transparancey) rather than a frame hold... and edit it into the timeline.
When you have a frame hold over a cross dissolve it makes the frame hold disappear, not sure why but just a heads up for anyone else having the issue
It does happen, resetting preferences doesn't change it
Can't edit comments for some reason on here, but it's not cross dissolve it is just any change in sequence, if there's a cut above or below the frame hold will disappear, unless you nest all the footage around it it just doesn't work
by any chance is your source from a smartphone or screen recording? If so, your clip probably has a variable frame rate which is problematic in Premiere and would explain why there might be issues with a frame hold.use mediainfo to determine whether your source is variable or constant frame rate
if it's variable use handbrake to convert to constant frame rate
and here's a tutorial on how to use handbrake
It's not a variable frame rate it just happens over cross dissolves for some reason
Nope turns out it is over any frame change, it just disappears?!