How can we improve Premiere Pro?

← Premiere Pro

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
https://forums.adobe.com/search.jspa?q=time%20remap%20nested%20sequence

but I did not find it listed here, so I am posting it now.

88 votes
Sign in Sign in with Adobe ID
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Rod Harlan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

37 comments

Sign in Sign in with Adobe ID
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Eric Laska commented  ·   ·  Flag as inappropriate

    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).

  • James Curtis commented  ·   ·  Flag as inappropriate

    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.

  • Alex Krylov commented  ·   ·  Flag as inappropriate

    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.

  • Orestis Chatzitheodorou commented  ·   ·  Flag as inappropriate

    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

  • Sebastian Van Eickelen commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    I'm having this problem too, almost every project, which makes editing a frustrating process

  • Daniele Salvadorini commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    @ 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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    Had the same issue....The software is called PRO..... WOW really professional Adobe! Big applause for NO DEBUGGING!

  • Thalia Reyes commented  ·   ·  Flag as inappropriate

    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!

  • Eric Laska commented  ·   ·  Flag as inappropriate

    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.

← Previous 1

Premiere Pro: Editing

Categories

Feedback and Knowledge Base

(thinking…)