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.
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:
Andrew Moore commented
This is still happening. Come on
Steven Hammer commented
Wow, this is pathetic that this is still an issue. The difference in render time between using hardware acceleration and using software only is about 10 times longer with software only. Come on, Adobe, get with it.
andres raudjalg commented
Any updates? 3 years since this bug report... and still? Is there even any point in reporting these sort of things if there is no help to be found? Very sad.
EDIT (half solution):
Using right click and Speed/Duration to speed the clip up works - but when doing it with Time Remapping keyframes it makes the clip black in proportion to how much you speed it up...
Nathan Powers commented
Jesus Christ how is this not fixed by now?????
Isra Velzen commented
Still the same problem in 2021. Why is this not solved!
mantas malevskis commented
!!! Please read this comment!!!
Just edited my video, the same issue happened. Only that if I understand correctly the issue everyone talks about I know the "solution" if that is the appropriate name for that until it gets fixed.
From what I understand when you make a nested sequence it is the sum of all videos combined. When you speed up, adobe premiere for some reason it speeds up those videos so fast that it shows only part of them and fills up the other part with black screen as if they weren't there. Also it leaves the entire nested sequence the same length before time remapping
When I realized that, I double clicked on it and did time remap on each video separately inside nested sequence.
Only now it shows up as completely correct time remap that I did inside, none of the media was chopped with that black screen and the only thing was left is to cut out the unnecessary black screen thing.
Hope that helps to understand what the problem is.