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.
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!!!!
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
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. Very dissapointing. MBP16 // PP v 14.0
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.
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.
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).
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)
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.
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.
Part of the problem with this bug is that in all the interactions I've had with adobe staff, they have all intimated that the existing behaviour is correct: sort of "you're not holding it right", type feedback.
I have listed this bug at least twice.
Here is a new video demonstrating the problem. I am happy to help with this. I use remapping all the time. For the last 3 years I have been having to render interim files for nested sequences that have layers.If anything is still in anyway not clear, or if anyone thinks this behavior is still as expected, I'm all ears. https://youtu.be/CoUYqRoHXEo
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.
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.
Hi Adobe 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...
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.
77
Replies
AdChoices