Inspiring

Open for Voting

P: Nested sequence time remapping bug

155 replies
26704 views
Translate

I've submitted this bug several times now. 2 things: how do we know if adobe has acknowledged a bug? do they respond to let you know?

2nd thing, the bug itself:

take a nested sequence, insert it onto timeline. Add another layer in the nested sequence, apply time remmapping. Sequence will go black before it reaches the end of the sequence. This vid below demonstrates that it is not the normal behavior of a time remmapped clip. Most of the time when I encounter this bug it is when the original footage is not the same res as the final sequnce.

[hyper link removed by author request]

[Typo removed from title. — Mod.]

Performance or Stability

Show previous replies

P

Peter24170174dlfj

Participant

This bug is really causing me a lot of pain right now. The fact that this only happens when using GPU acceleration makes it extremely clear this is a bug. Please fix this, or if it's not possible to fix please just remove time remapping from premeire entirely.

Translate

M

Mikael23718359fyps

Participant

Changing rendering settings to software-only worked for me.

Translate

L

larrypizza69

Participant

Mikael237...... HAS THE FIRST HELPFUL ANSWER! So glad I read this thread all the way to the end.

File > Project Settings > Video Rendering and Playback > Mercury Playback Engine Software Only

The problem is the default "Mercury Playback Engine GPU Acceleration (Metal ) - (Recommended)" renderer with multiple layers of time remapping breaks for some reason.... A BUG PERHAPS!

I remapped 2 different clips so the timing matched in a picture in picture, then nested and attempted to apply new time remapping keyframes to my nested sequence. I got the black screen error. Software only seems to be working!

Translate

C

Clemens5C68

Participant

Just encountered this bug too. Really frustrating! What is the best working workaround?

Translate

C

Clemens5C68

Participant

Ok DanCoes method works:

"I nest the sequence and then increase the speed duration of the nest (to say 200%) . I then create the time remapping and slow down the first part of the clip. Effectively creating the same result. I don't know why this works, but simply ramping the speed up from 100% speed duration doesn't?"

Translate

Joost van der Hoeven

Community Expert

This forum is to for users to help users. If you feel strongly about a (new)feature or (bug) fix and you want the Adobe developers to take a look, please post it here: https://adobe-video.uservoice.com/forums/911233-premiere-pro

Translate

G

gethoAuthor

Inspiring

Dood, do you have any idea how insulting it is to have this post marked with a correct answer?

Since 2017 I have posted on uservoice, phoned Adobe, posted here, contacted various Adobe employees directly, tweeted at them.

In fact the only things I haven't tried are semaphore and carrier pigeon.

Not only have I never seen any evidence of Adobe responding to feedback about bugs Ive never seen anyone who has. You have YouTube film makers with hundreds of thousands of followers who try, give up, switch to resolve. The only reason I'm still here is because I'm a multimedia masochist.

Adobe removed it's bug reporting feature entirely, leaving only uservoice. If you look me up on it you'll see I have outlined this and the other showstopper bug in great detail. Conplete with demo videos.

To everyone here that has experienced Adobe's lack of responsiveness I say, vent away.

Translate

Jeff Bellune

Legend

Just because they don't respond to you personally or in public doesn't mean they aren't taking the reports seriously.

UserVoice is our channel to report problems with the software that we think are bugs. This forum is to help each other find workarounds until/if those bugs are fixed.

And I agree; if the arrangement I outlined isn't satisfactory to you or anyone else, then vent. But maybe try UserVoice instead of the forum? Your vent here will find a very limited Adobe audience here that could possibly do anything about it.

Translate

A

Anonymous

Found a workaround. For me, it occurred when the layer on top of my video film inside the settled succession finished. I just made a still casing on the last casing of the top layer and extended its length to equivalent to the one beneath. I at this point set a keyframe to bring down the opacity of the top layer to 0 on its unique endpoint, so it would in any case be staying there however imperceptible.

Translate

tombkn

Participant

2021 and still not fixed. fails around 400% on the time remap...

screen goes black on the main sequence, however when clicking into the nested clip you can see there is still plenty of footage that isn't being shown

🙂

Translate

G

gethoAuthor

Inspiring

and since ppro2020 there have been bigger time-remapping bugs with interpreted footage. I've learnt to live with this the nested sequence bug, but the interpreted footage one is a show stopper for me. I'm still using ppro2018. I wont upgrade until it's fixed (which in reality means I'm more likely to move to resolve).

Translate

K

kurtv47853677

Participant

Found a workaround. For me it occured when the layer on top of my video footage inside the nested sequence ended. I simply created a still frame on the last frame of the top layer and stretched it's length to the same as the one below. I then set a keyframe to lower the opactiy of the top layer to 0 on it's original endpoint, so it would still be sitting there but invisible.

Definitely no bugfix, but a workaround.

Translate

K

kurtv47853677

Participant

EDIT: Was not able to reproduce the workaround. But it definitely has to do something with the end of the top layer. Sorry!

Translate

J

Jim Curtis

Inspiring

It's now August of 2018, and I just encountered this. So, it's not fixed in Pr 12.1.2 Mac.

I described how I get the bug in detail here, before I found this post:

major problem with CUDA and Nests

Translate

J

Jim Curtis

Inspiring

And it's STILL not fixed in Pr CC 2019, 13.0.2

Translate

DanCoe79

Participant

I've seen this error several times and recently found a simple fix. If I have a nested sequence and then want to time re-map with a gradual increase in speed (for example), I do the following:

Translate

R

RodHarlan

Participating Frequently

This bug has been reported for years and there are a number of threads about it here on the Adobe Forums going back years.

Here's one over 3 years old:

Time remapping a nested sequence results in black/empty video

It's honestly easier to click on this Google link to see all the postings about this issue here on the Adobe Forums:

premiere pro cc time remap nested sequence bug site:forums.adobe.com

Translate

G

gethoAuthor

Inspiring

what is easier?

Or is that directed at adobe staff?

Heyyyyyyy!!!!!!!!! ADOBE!!!!!! Helooooooooo!

Translate

R

RodHarlan

Participating Frequently

LOL! :-) Yes, at our friends working hard at Adobe. I know they are busy. I just wanted to point out that this has been a known and reproducible issue for many years. It has been analyzed from all sides (as the many posts on this forum show) and now someone just needs to take ownership of it and get it fixed.

Translate

NavMotion

Participant

I have found this same problem. I have created a project with lots of time remapping using nested sequences. Which works fine. The problem is I was then asked to add some 3d after effects text to the shots. Using the un-remapped footage within the nests I created my animations. Adding the AE projects or rendered footage to cover or replace the small sections that need it within the nests leaves empty ( or black) gaps in the main project. It seems that the remapping effect isn't being applied to everything within the nest, just the original footage with which the nest was created. I have a lot of varying speed-ramps so to match the animations over the top is quite a challenge. Is there a setting I can change to make the other exported footage work within the time re-mapped nests?

Translate

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.