BUG REPORT: Time remap of nested sequence results in black/empty video using GPU
Only work-around seems to be to switch to "Mercury Playback Engine Software Only" which is brutal with 4K nested sequences.
This has been discussed for years on the Adobe Forums
but I did not find it listed here, so I am posting it now.
Been struggling with this exact issue (4k nested footage blacking out), spent a while redoing the work, then looked up a bunch of tutorials to find out what I was doing wrong. Nothing I found told me to do anything different so just googled the error and this is top result. As usual with most Premiere Pro problems, I find it to be a years old bug that has never been fixed.
Already started learning Davinci Resolve. I've decided that every time I hit an Adobe bug / issue in future, I will watch 1x YouTube tutorial on Davinci. That way, I figure it's in Adobe's hands how quickly I move away from Premiere Pro!
Peter Whidden commented
Help! I'm also having this issue and it's cost me dozens of hours trying to work around it! Being an adobe customer is absolutely humiliating.
Garret Griffin commented
QUICK FIX: Select all clips that you would have tried to nest. Right click and select "Replace With After Effects Compostion". Export it from AE, import it back to PR and time remapping should work. (follow last steps if you don't want a dynamic link muddying up your project speeds)
Ben Kamprath commented
Also experiencing this bug when trying to remap a nested sequence. Using latest version of Premiere 2022.
rik verstijnen commented
Another workaround, which worked for me: Go to the source of the nested sequence. Select all tracks; enable multi-cam; disable multi-cam again. After that, the track containing the nested sequence did not show black screens anymore...
Pierre Trevidy commented
WTF Fix it for god sake
Pierre Breckler commented
Quand je fait du montage sur première pro je passe plus de temps sur les forums à chercher comment contourner les bugs que finalement faire mon montage.
Ca commence sérieusement à me casser les couilles!!!
Jordan Mecikalski commented
Hey guys, been a few months but I have some new insight on this: Clearly if you do anything significant with frame holds, time remaps, stabilization, etc. then you are expected to use Adobe After Effects.
For a couple years I was getting by just fine on premiere pro and only very rarely needed to do any advanced editing, and so I didn't have After Effects on my subscription. I encountered many many many many bugs regarding frame holds, time remapping, framerate mismatch, etc.
Recently I upgraded my license and it turns out After Effects doesn't have any of these bugs. The implication is clear: The large majority of professionals using these tools are not complaining to Adobe about this because the "standard" workflow through After Effects (using Premiere Pro just to stitch things together) is actually working pretty much fine. Even the Warp Stabilizer gets ASTONISHINGLY better results than the one in Premiere Pro, with exactly the same options.
The consequences of this are equally clear: Adobe is never going to fix this because it already "works" for enough people. Your options are to live with awkward workarounds and bugs, or suck it up and shovel more money at them for an upgraded license.
Sujit Panigrahi commented
STILL not fixed after almost 4 years :l
alexis borthiry commented
Same issue here.. Any news from Adobe regarding this horrendous behavior?
Mathew Pintauro commented
POSSIBLE FIX: I'm in PPRO 15.4.1 and I was trying to speed ramp two clips joined together (approaching a doorway, and going through the doorway) and the second clip was going black when speed ramping the nested sequence. I then nested both clips individually, then nested the individual nests and speed ramped that.
Wham bam thank you ma'am it worked.
Jordan Mecikalski commented
I had an outsourced support guy tell me "audio sync is hard, maybe look up some youtube videos", it was absolutely the most condescending support experience of my life.
It really comes down to frame holds and time remaps being janky as **** in nested sequences. Unfortunately we have no choice as nested sequences are the only good way around things like "remap + warp stabilizer" or "Premiere is barfing all over itself on the last frame because the clip has a different framerate than the sequence".
Hadi Mroueh commented
I've had this issue for a while now, and now that I thought it through, I dont think its a bug...
The problem is that we've been mistaking the idea of a nested sequence with the idea of merging or join clips... the way to solve this issue is to render and replace rather than nest.
Nesting is the process of putting a few clips under one tab in order to perform edits collectively however this doesn't apply to time remapping or warp stabilising.
Thanks all, hope that helps.
Sam Johnson commented
seriously Adobe, you need to get this sorted.
John Pooley commented
Alyosha Zeifman commented
I regret the day I ever made a nested sequence. Endless problems. Tried different work around suggested. nothing worked. FU!
L'ile Gøwf commented
Please fix. ****
Rajjeet Phull commented
Please fix. this is causing me hours of work here. My sad workaround is just not time mapping my clips and using the unnested version.
Rod Harlan commented
My original link showing the Adobe Forum posts going back to 2016 reporting this problem no longer works in my original Bug Report post above because of site changes.
Here is the new link:
Gethin Coles commented
I first posted about this in 2017, I've seen posts from 2016 about it. But this is a mild snafu compared to the current time-remapping bug which is stopping me using premiere 14&15. As detailed: