P: Nested sequence time remapping bug

It freaks out if you change anything in the nest after adding time remapping to the nest. Even if the duration stays exactly the same, it can’t handle having more than one clip in there or anything changing. This is an issue when you’re trying to replace ungraded footage with graded footage. The colorist should only be working with the part of the clip that’s actually in the final timeline. This is a professional workflow, Adobe. So if the nest is way longer than needed, I need to send the colorist trimmed clips to grade. The I bring in the graded trimmed clips into the nest, KEEPING THE DURATION OF THE NEST THE SAME (using ungraded clips to keep the duration the same). And it turns black in my timeline.

The only work around that works for me is to export the contents of the nest in prores and then bring that prores clip into the nest so that the nest only has a single clip again. This is ridiculous.

why is this still an issue 8 years later...

Currently dealing with this 14/08/2026.
Bummer

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.

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?