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.
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.
Zerak Hussain commented
same, just had this same bug. Wish they would fix this
Caleb Brown commented
Just ran into this and a plethora of other issues which switching to "Mercury Playback Engine Software Only" fixed. I was having an incredibly frustrating problem where I had a nested sequence on V2 and when a non-nested sequence clip started on V1, the sequence on V2 would just completely disappear. Made NO SENSE because the nested sequence was on the top track. Sure enough, switching renderers solved it. Thanks for wasting hours of my life Adobe. Seriously considering the switch to Davinci Resolve 16.
Scott Milholland commented
I can confirm that if you switch to "Mercury Playback Engine Software Only" in the Project Settings, it does work, but playback is incredibly slow with 4k footage.
Isaac Ryan commented
Why has this not been fixed yet?! I'm running the latest version of PP in 2020 and still having this silly issue.. whether its cache issues or graphics switching or SOMETHING it doesn't mattter! We creatives need our programs to be reliable and working.. It's impossible to work with issues like this. ADOBE FIX THIS ASAP thanks.
Brian Peters commented
Please fix I hit this and it cost me hours :/
Please fix this really annoying bug Adobe. Experienced the same bug when using speed ramps with nested sequences.
Marius Wickli commented
I had the same problem with the speed ramped part going black.
It worked out for me to switch to Mercury playback software only, then rendering the nested clip and then switching back to Mercury playback Metal again.
not sure though if this is a permanente solution (just figured it out before posting this comment)
Eric Laska commented
Another way to cause the bug is simply to resize the composition, or render out at a different resolution (e.g. add to Media Encoder Queue then change export settings from there, not even from in Premiere).