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.
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).
Peter Kortvelyessy commented
Same here. Please fix
James Curtis commented
There's a workaround. It shouldn't be necessary, but you can finish your project. Nest your clips, render, import, place the rendered clip on the topmost video track. Go back to the sequence containing the nest, and do your speed ramping on the nest. Alternatively, you can replace the nest with the rendered movie file. It's a PITA, but it works.
Kevin Christopher commented
This just really bit me ******* a national ad campaign. Agency did not want to hear excuses.
Alex Krylov commented
I just encounter this problem, tried to google it and found this thread. More than year from the first bug report! Nice to see that something is stable in this world.
On the bright side now I know that in this particular case it's not me who is half-assed.
Johannes Höhn commented
SUCH A PAIN!!!! ALWAYS HAPPENS. How can this be professional software?!!?!?
Orestis Chatzitheodorou commented
That's not nice... playback shows a freezed frame from the beginning of the clip while scrolling or paused will show the right selected part of it.
As said switching to "Mercury Playback Engine Software Only" will fix this but i can not consider it as a work around for a pro software.
MBP16 // PP v 14.0
Sebastian Van Eickelen commented
Spent 2 hours in speed ramping a nested sequence, after a while there was only a black screen and in the nest I stilll had footage playing. This is so frustrating, people paying for this and working with deadlines are very unhappay right now .
MBP 16 METAL PP V. 14.0
Bob Pearson commented
I have spent half of my day trying to figure out why I can't speed ramp a set of nested photos. As soon as the speed increases, I get black frames and the images disappear. I even exported the nested photos as a video and then reimported that video back into PP to try to speed ramp that... it did not work either. WTF Adobe. I am going to Davinci, this is crazy, this project is due tomorrow and the client specifically wants the slideshow to increase speed with the music. The entire video should have taken me 4 hours total and now I have an entire day in this and a blank timeline. IT SHOULDNT BE THIS HARD!!!!
Edit: Davinci is downloading as we speak. DONE WITH PREMIERE. DONE!!!!
Joni Millar commented
I'm having this problem too, almost every project, which makes editing a frustrating process
Daniele Salvadorini commented
I wish we customers could charge you our hourly fee for the amount of time because of this bug.
It was first reported 4 years ago and still nothing has been done. Way to go Adobe.
Kristiyan Nikolov commented
@ Cyril Grosse, Same man, switching to Resolve and have never been happier. Sure, there is a learning curve, but that program is a game changer. Also, I don't have to tolerate bugs like this while selling my kidneys for it.
Cyril Grosse commented
This and so many other major bugs that Adobe refuses to address is why I've switched to Resolve and I'm never looking back. Will be downgrading to just photoshop very soon.
Gerald Hahn commented
Had the same issue....The software is called PRO..... WOW really professional Adobe! Big applause for NO DEBUGGING!
sergio solorzano commented
Using Mercury Playback Engine Software Only also freezes frames when playing with Bezier curves