Skip to main content
Inspiring
November 19, 2017

P: Nested sequence time remapping bug

  • November 19, 2017
  • 50 replies
  • 26092 views

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.]

50 replies

AndrewTheGreat
Known Participant
April 7, 2026

I discovered another bug in Pr 26.0.2 which is worth giving attention to, and it’s connected with the use of time-remapping with nests.

I wanted to make a sequence of images gradually speeding up. A simple task when you put your images on the timeline, nest them and use a time-remap curve to speed it up:

In the example above I have 32 minutes of images5 seconds each. So I switched on the time-remapping graph and made this curve and it turns out in this scenario Premiere shows only half of the images:

Your normal reaction would be - ok, it sped up so much (it’s only a 500% speed curve) that the images just ended before the sequence ended, right? Well, first of all, when you pull up this speed up curve the sequence gets shorter accordingly. Second - I went inside the nest and trippled the amount of pictures there (the purple ones are the original quantity):

… and guess what, nothing changed - the images just go black at this timestamp:

Steps to reproduce:

  • Create a sequence, put the needed amount of images in it
  • Select all the images and nest them
  • Open the Time-remapping curve, place the marker somewhere at the beginning of the nest and drag the curve up to make it speed up. See the result.

Pr  26.0.2, 14700K, 4080, Win11 25h2, all drivers up to date.

Stop trying to edit and EDIT!
Participant
November 13, 2025

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..

Participant
November 11, 2025

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.

gethoAuthor
Inspiring
September 10, 2025

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 
 

Inspiring
August 31, 2025

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.

Participant
August 10, 2025

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

gethoAuthor
Inspiring
July 23, 2025

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

Mr. Wallet
Known Participant
April 21, 2025

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

Participant
April 21, 2025

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

Mr. Wallet
Known Participant
January 10, 2025

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