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

[M Sohaib27216431dwsw]

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

[lucian_5446]

Yesss to this! We need to be compensated for the literal WEEKS of our lives we waste trying to work around the damn bugs that have proliferating in Adobe since forever! But no, your Prosumer's time is worth nothing.

[pixeljazz]

Kicking this thread awake again - Adobe really needs to fix this.

It's insane to let this be around for nearly a decade and now just "aknowledging" it.

[Mikayel29522588bi8a]

It's always that you are aware of the bug, but can do nothing about it, it's 2025, the guy who had the issue originally asked how to solve it in 2017. it's 8 years. 8 YEARS.

[Ari35548927ego8]

in my peremiere sequence i have a Nested sequence that also contains a speed ramp when ever i pu a text overlay on top of it it becames black , if i disable or remove the text layer the footage is back on again once i re-enable it the footage is black again

[Ann Bens]

Not seeing this on my end

Try resetting preferences  and trash media cache.

If that does not work:

How to Report a Problem

[jamieclarke]

Hi @Ari35548927ego8 - This is a known issue I will merge your post with the primary thread so that you are notified of any updates.  sorry for the frustration.

[getho]

@Ann Bens The speed ramp needs to be over 300%. You might not notice this isn't working unless you have a clip with a known endpoint.  Also this is a cuda bug, so if your not on windows or using amd you won't see it.  If you are using NVIDIA and are not seeing the bug let me know and I describe how to reproduce it.  ( and it has now been acknowledged by adobe, but that was over a year ago iirc)

[Ann Bens]

Yes windows 11 pro and nvidia

Yes please describe how to reproduce.

[getho]

ok there are some variables that I cant guarantee aren't important - like the fact my media is all resized and interpreted from 50 or 29.97 to 25fps. If you want to match what I do then take a clip and interpret to a lower frame rate.
Put it in a 1080 sequence with the same framerate. Fit to frame and nest it.
Do a speedramp to eg 1000%

Go into your nested layer, and add another clip at the end

now return to your original sequence and you'll find the extra clip that you added will not play, the sequence goes transparent before it gets there.You can try extending the nested clip on the original timeline, and it still wont play to the end.
I have tried this with quitcktime HQ422 with the same result (so its not a h.264 issue).

(I've got it on a color matte so you can see that its not going to black, its going transparent).
If you are not seeing this result, let me know. As i've had it over the lifespan of 3 or 4 different computers. 

[Ann Bens]

Yes was able to reproduce but not all the time. if you put a clip/text over the full length in the original sequence or cover the corresponging speed change it won't go to black.

[getho]

Yes that provides a workaround for specific instances, but i've found that sometimes all you need to do is introduce a cut in a single clip and it will stop working. Sometimes it will work fine for a while, and the next session it wont. 
This wont work, and making it a nest wont work. 

But this as you pointed out will

Here's some more info for the devs to ponder:
This will play the last frame

but this wont

nor will this