P: Nested sequence time remapping bug

[getho]

I've submitted this bug several times now.  2 things: how do we know if adobe has acknowledged a bug? do they respond to let you know?

2nd thing, the bug itself:

take a nested sequence, insert it onto timeline.  Add another layer in the nested sequence, apply time remmapping.  Sequence will go black before it reaches the end of the sequence. This vid below demonstrates that it is not the normal behavior of a time remmapped clip.  Most of the time when I encounter this bug it is when the original footage is not the same res as the final sequnce.

[hyper link removed by author request]

[Typo removed from title. — Mod.]

[federico27799673890i]

Same problem here, it is the same in all Premiere versions I had 😞

[jmohan00]

Bizzare workflow bug.
A clip : Stabilized > then nested > then Time Remapped> then nested > then Transformed.....
Goes black.

I am not familar with "SubSequences" yet.

Please correct me if my workflow is incorrect.

[Kevin-Monahan]

Hi @jmohan00,

Thanks for the note. What are the system and media specs? What about the size of the sequence and nested sequences? Are they oversized? Do you have scaling going on, as well? You might be out of VRAM. We need more info, please. See, How do I write a bug report?

Thanks,
Kevin

[jmohan00]

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

[Kevin-Monahan]

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

[jmohan00]

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.

[Kevin-Monahan]

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

[Uroš34682631qnwu]

How is this still not resolved?!?!

[jamieclarke]

Updating Status

[MUK22692521dm6t]

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

[Uroš34682631qnwu]

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

[defaultn0suc8y3vov2]

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!

[Ann Bens]

Tried rendering?

[defaultn0suc8y3vov2]

I have tried to export the video and unfortunately, it's the same in the render

[jamieclarke]

Hi @defaultn0suc8y3vov2 - What type of media is in your nested sequence?  Can you post a screen recording of your issue?

[defaultn0suc8y3vov2]

Hi @jamieclarke. Inside the nest is another nest ('Timer'), an adjustment layer with Lumetri properties and video footage. I have since tried to move the 'Timer' nest assets into that same sequence and then speed ramp/time remap the main sequence but the same results occur.

I've also attached a screenshot of the nested timeline for your reference.

[jamieclarke]

Hi @defaultn0suc8y3vov2 -  We’re aware of this bug, and we apologize for the frustration it’s causing. While using the software renderer could serve as a workaround, our goal is to fix the issue rather than rely on workarounds. The problem occurs when time-remapping a nested sequence containing two or more clips, which results in black frames appearing.

[Mr. Wallet]

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

[Chris27119490qjvb]

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

[Mr. Wallet]

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

[getho]

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

[lucian_5446]

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

[Sami Succar]

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.

[getho]

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