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.
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
Thalia Reyes commented
Common Adobe! You are taking excesive ammount of time to fix this bug. It's been there for years and there's still no answer.
Please fix, pity please!
Valon Imeri commented
Hey Adobe, Please fix bugs before doing new stuff
Eric Laska commented
I make a lot of timelapse videos, and am forced to forgo smooth speed transitions because of this bug. That's like half the use cases for me, which I've spend thousands on this software for (the other being 360 video editing, but now Sony Vegas has it).
Unurprisingly, the free tool FFMPEG is becoming my primary "editing" tool for timelapse ingest, since it can do things like time remapping, stitching and concatenating folders of image sequences without taking literal hours.
Caitlyn Bole commented
Issue is happening to me too, this really needs to be fixed.
Dustin Glendinning commented
Still having this exact issue as described here. PLEASE FIX
Laura Willaert commented
I support this report. I edited in Premiere a 360 VR that is only a few seconds long and I included on it a time remapping. Once exported to After Effects in an arbitrary point becomes black and stays this way until the end.
Ashley Jones commented
It's July 2019 and I am still seeing this issue. If the product was able to use the multicore processors we have in 2019, switching off the GPU wouldn't be such a big deal.
1. Switch the render to Software only (Not OpenCL or Metal) in both Adobe Premiere and Adobe Media Encoder if you're using it.
2. Close your project file, go to Documents and rename the 'Adobe' file 'Adobe OLD'.
3. Try exporting again.
Having this problem as well. Time remapping nested sequence results in black frames. Turning to "software only" doesn't fix it, and the black frames are there after export too.
So Adobe Technical support solves me the problem removing the folder of common in roaming. but it happens again when you make some changes in the sequence. So every time you have the issue you must close premiere and delete the folder. Looks it's a problem of the cache previews.
Rogier van der Voort commented
Seems the problem isn't fixed yet? Also working with 5K footage, render and replace + warp stabilizer doesn't work just like nesting the clip and then adding warp stabilizer doesn't work: both instances render partly black clips...
Moises Navarro MN VIDEOS commented
It doesn't help to switch to only software. If I export is black also