Inspiring

P: Nested sequence time remapping bug

Forum|Forum|8 years ago
November 19, 2017
49 replies
25898 views

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

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.

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

🙂

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

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.

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!

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

J

Jim Curtis

Inspiring

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

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:

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

G

gethoAuthor

Inspiring

what is easier?

Or is that directed at adobe staff?

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

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.

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?

jstrawn

Community Manager

The steps aren't clear enough to tell exactly what you did and there is no longer any screencast attached. But since you mentioned 'adding a layer' that makes me think that you put a video clip layer inside of a Graphic and then slowed down the whole Graphic with time remapping. If so, seeing the video end before the Graphic is expected behavior if the clip is not as long as or longer than its Graphic container. Only the Graphic clip is affected by the time remap, not any media layer(s) within. To see it the way you want, you need to edit the clip in the timeline with a time remapping or speed/duration change, re-export that (preferably in some virtually lossless format) and then put that into your Graphic. Clip Layers are mainly intended to be used with still images (for logo bugs and thing) which is why we do not allow any sort of real editing to clip layers within a Graphic.

We mainly acknowledge bugs by fixing them and delivering those to users. However we sometimes reach out privately to users when we know a critical bug has been fixed. But we generally never promise TO FIX something until it has actually been fixed. That sort of risky over-promising is called 'side arrangements' and it is never a good corporate practice. That's why we typically don't say a lot about what we have in progress until it is announced publicly. Not to mention the time it would take to respond to every user about every bug submitted through the wishform.

G

gethoAuthor

Inspiring

you need to read the thread, and you'll see 2 videos,

premiere pro nested sequence time remapping bug - YouTube

its a bug not a feature Video 2017 11 21 120138 - YouTube

G

gethoAuthor

Inspiring

also there is a bug on these forums that if you paste an external link (cant say all, but definitely with youtube), and then continue typing it jumps to the top of the page meaning you cant see what you're typing. (terrifiic).

@jstrawn Sorry but I'm getting annoyed by people who havent understood the issue - as you said yourself - saying its expected behaviour. I can tell you its not, and assume that you don't understand it if you think it is.

Here they are broken down again:

G

gethoAuthor

Inspiring

you can see in the vid I make the clip about half the length of the video layer below it, so no that's not the case. I don't know why or where the bug comes from but it's causing me a lot of faff and I wish somebody from adobe would at least look at it.

hello... Adobe... Are you there?

stefan_gru

Inspiring

hello... Adobe... Are you there?

getho: Many of the product experts are away for the Thanksgiving weekend, unfortunately. Maybe jstrawn can weigh in on the technical side of things or log this as a bug. You should also post this experience yourself: Feature Request/Bug Report Form