P: Nested sequence time remapping bug

@defaultn0suc8y3vov2 Having wrestled with this a lot several years ago, I can't give any sure-fire work arounds but perhaps a good way to think about it. Premiere has a tendency to ignore the underlying asset and "clip" things according to the pre-remapped time. So for example if you have a nested sequence with 10 seconds of video, and set the speed lower than 100%, it will tend to turn black exactly at the 10 second mark. This is the simplest example but most cases of the video blacking out usually involve an oddly-convenient coincidence like this.

The best way I found to solve it is to try and create as much "time buffer" as possible, in as many places as possible. Make the nested sequence longer than it needs to be in proportion to the amount of time remapping (not the "out", but actual "rendered stuff" time; fill it with repeat video you won't use, if necessary), and then simply reduce how much of it you use in the outer sequence. If you have anything repeating or on a hold frame, copy-and-paste is always better than time stretch (and un-nested is always better than nested). Slow-downs should be as far "inside" as possible in a simple sequence because the pre-slowed duration is when it's going to turn black, so once you get it solved at that layer all the outer ones will fall into place no matter what you're composing together. Be aware that an entire sequence might be turning black because one single clip/sequence nested inside of it is remapped (putting a non-remapped dummy layer that goes from the start to beyond the end of the sequence may help). And when in doubt, add one useless layer of nesting just to see if it helps. Basically you just have to fiddle with it until you trick it into working, though it may take an hour each time until you get a feel for it. Best of luck!

I've been facing this recurring issue in Adobe Premiere Pro: When I place a nested sequence into my main sequence and speed ramp (Time Remapping), upon playback, the speed-ramped nest plays for the first few frames and then displays as a black screen. Is there a way to solve this?

I have looked through the forum and seen answers like the 'nest needing more frames.' That, however, does not seem to be the issue in this case, as the nested sequence contains a longer duration of footage (therefore more frames) than I need in this section of the speed ramp. 

I thought maybe I could solve it by switching the video/playback renderer but that option is greyed out for me (it would be good to know why that is, too.)

I'm using Premiere Pro 25.1 on an Apple Mac Mini M2 Pro chip with 32GB memory. 

Any suggestions, help or advice would be greatly appreciated. Thank you!

Well they did update the status to acknowledged. Whatever that means.

How is this not fixed yet, have adobe acknowledged an issue yet. Its nearly 2025 guys. This was 8 years ago

Updating Status

How is this still not resolved?!?!

Good idea. That's what I usually do, as well.

The files are 60fps 4k directily from iphone, and reads as .mov in Premiere.

As it turns out, my additional nest failed. I ended up just rendering out that nested sequence as ProRes and dropped it back into timeline. No issue so far.

Thanks for the note. That's a little weird, but it's good to know, @jmohan00. I'm always suspicious of Xeon-based Macs. They were only out for one rev and may not have the goods you need for specific formats. For example, are you using H.264 or HEVC? I cannot verify if the CPU has Quick Sync, which is crucial for video processing in that format, especially when compositing or creating video effects.

See if changing to an editing codec like ProRes might perform as expected. Hope to hear back from you soon!

Take Care,
Kevin

Hello Kevin, thnks for responding...

I am working with 4k 60fps videos.
The unexpected solution was to nest 1 final time (the final nest is 3 deep)

Bit bizzare , or my inexperiece with editing (vfx artist). or a bit of both.
I'm on Mac.
Regards,
JMohan