P: Nested sequence time remapping bug

bro it's still cut at a specific time (and hence trimming my clips) no matter how long black video I put in the nest..

When a bug isnt fixed after 8 years, the next workaround is switching to Davinci Resolve. It honestly is getting to the point where im about to switch over after being a long time Adobe user. Hardware Improves year by year, yet the software lags behind.

Premier pro beta 25.6.0 still has the bug 

New features! More bugs!  Worse performance!  Why am I still here?  I'm a adobe masochist 
 

It's August 31st, 2025, and I'm still facing this bug.

My usual workaround is to create a black video and add it on V1 below everything else inside the nest, and then trim it way beyond the actual videos I need to remap.

Absolutely ridiculous that we as professionals still have to deal with this after being kept in a jail of repeatedly paying the overpriced subscription and then adobe steals more of our time just to try to find work arounds for their errors. Its absolutely ridiculous and will be migrating after this project. Seriously cant give a rats a$$ for adobe anymore

@jamieclarke Since your reply you now need to restart premiere in order to access software only rendering making one of the workarounds much more difficult.  Any progress?

3 months! 😂 This issue was open for 7 years before it was simply acknowledged. Come now Chris27119490qjvb, let's be realistic here.

It has now been 3 months since this reply - is there any update to this fix @jamieclarke ? Making things very difficult. 

@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!