Nested sequence time remapping bug

Report · Nov 19, 2017

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

Report · Jan 24, 2023

QUICK FIX: Select all clips that you would have tried to nest. Right click and select "Replace With After Effects Compostion". Export it from AE, import it back to PR and time remapping should work. (follow last steps if you don't want a dynamic link muddying up your project speeds)

Report · Jan 24, 2023

Help! I'm also having this issue and it's cost me dozens of hours trying to work around it! Being an adobe customer is absolutely humiliating.

Report · Jan 24, 2023

Been struggling with this exact issue (4k nested footage blacking out), spent a while redoing the work, then looked up a bunch of tutorials to find out what I was doing wrong. Nothing I found told me to do anything different so just googled the error and this is top result. As usual with most Premiere Pro problems, I find it to be a years old bug that has never been fixed.

Already started learning Davinci Resolve. I've decided that every time I hit an Adobe bug / issue in future, I will watch 1x YouTube tutorial on Davinci. That way, I figure it's in Adobe's hands how quickly I move away from Premiere Pro!

Regards, aTomician

Report · Jan 24, 2023

bro what is wrong with Adobe, address this please! doesn't do this in windows

Mod note: Profanity removed. Please do not use profanity.

Report · Jan 25, 2023

@baarokun by virtue of it not having been fixed, I'd have to disagree with you there. Rather, my experience as a software dev leads me to suspect that Adobe's products are incredibly laden with technical debt, rendering even "simple" changes nearly intractable. For example, the integration of keyframes and time remapping is also jank (as well as leaving extraneous transforms after enabling Bezier curves (e.g. my footage is moving vertically when literally no keyframes change the Y coordinates, because in the past there was a keyframe doing so)).

Report · Jan 25, 2023

Hi, @Elaskanator,
Welcome to Adobe forums. I hope I can assist. Sorry about your issue. I'm not on the Premiere Pro staff—I'm in support. I'll see if I can reproduce your error and file a report here.

Providing a project file and a short sample of media from that project is the ultimate test. If possible, upload it to Creative Cloud, Drop Box, or whatever you like. You can follow up with me via PM with the link. I will deliver the assets to the product team.

In the meantime, give us the details about your computer, including the GPU and driver (if on Windows). Give workflow steps and information on how to re-create the bug.

I can help more by receiving sample files from you or after learning more details about your setup and media.

To work around any GPU issues, you might reduce the need for GPU interaction. Sounds like you have many things going on there! Try working with "optimized" media instead of native camera files. Editing codecs like ProRes (DNxHR or Cineform OK) files are superior in effects creation, as there is no H.264 decoding trying to compete with the Mercury Playback Engine. When you take H.264/HEVC decoding out of the chain, you can handle effects creation more nimbly. Please try this out. Let me know if this works for you.

Thanks,
Kevin

Report · Jan 25, 2023

Welcome to Adobe Forums @baarokun!

Sorry for the issue you're having. Give us computer specs, footage details, and any workflow steps you took so I can reproduce the bug (currently, I cannot). PM me a link to your project file and source files if you like, and I'll pass them on to the Premiere Pro product team (I am an employee but not a developer).

Thanks,
Kevin

Report · Feb 03, 2023

This is crazy. I'm using 1080 and it's not working. Lots of people talking about switching to davinci I'll check it out now

Report · Mar 08, 2023

Hi @Kevin-Monahan I'm happy to help provide anything you need to look into this, maybe you could ping me a message or use my adobe registered email address. I don't really want to provide stuff in a forum because it's quite time-consuming and I've been down that road before - with this bug. I'm happy to invest the time if I know it's actually going to get looked at, and not dismissed as what my Mrs calls "idiot user error"

Report · Jun 15, 2023

I'm having the same problem. I have 3 videos having 3 seconds each that are inside a NESTED. When I try to apply a speed ramp in the middle of the sequence, the video turns black.

I've been going through this for several years and today I came here in the community to research

Report · Jun 16, 2023

I found a work around. The problem dosn't accure then ther is only one video nested. As soon as I place two or more video's in the nested sequence the black video's apear. It works when you nest eatch video file separate.

Report · Oct 14, 2023

The new update has been released and the problem continues. In Brazil, see with each update video editors abandoning the program and switching to DaVinci Resolve

Report · Apr 02, 2024

Hello is there any news on a fix for this @Kevin-Monahan - I have a 15second edit with 8 time-remapped nests in it. The nested shots are A/B cameras and the ramps applied at the edit points.

The second shot in every nest is showing as black in program monitor and render.

Is there any workaround other than export the nests as a solid clip and applying the time-remapping to the new clip?

Report · Jun 06, 2024

This is STILL a problem in PP 24.4!

Report · Jun 10, 2024

Hey @jmvdigital, Hi @getho, @Odobe, @Águia Films and @Isra Velzen,

Thanks for the message. This bug report requires more information for the team to reproduce the bug. You can also send me a private message with links to files that produce this error. See: How do I write a bug report?

The behavior may be "as designed," but we need more info to determine that.

I hope we can help you.

Take Care,
Kevin

Report · Jun 10, 2024

Add a few clips together in a nested sequence. Place said nested sequence on a timeline. Use keyframe within timeline to adjust speed ramp... notice how the footage disapears (black frame) randomly depending on speed ramp keyframe settings.

It seems really disingenious to chime in after this post being live for over 7 years, and now stating that you need more info to reproduce it?! Crazy.

Report · Jun 10, 2024

Hello @jmvdigital,

Thanks for the message.

It seems really disingenious to chime in after this post being live for over 7 years, and now stating that you need more info to reproduce it?! Crazy.

This bug report was carried over from User Voice a long time ago. It was then migrated to these forums and has not been picked up by the product team.

Recently, the product team has asked my team (support) to come into these bug forums to triage legacy bug reports. I didn't intend to be disingenuous. I'm only trying to help here. I hope I can help. I am unsure why the product team did not respond to this bug. I'd ask them to comment, but even so, they do not comment on every bug report. Sorry about that.

I tried to replicate the issue and saw some black frames when attempting to get a high percentage of speed in the nest. I suspect that the effect is out of additional frames to affect. I will ask the team to respond to see if the issue is expected behavior or a longstanding bug that needs action.

Thanks,
Kevin

Report · Jun 11, 2024

Hi Kevin,

Willl send you a DM

Report · Jun 12, 2024

This is 100% a pretty severe bug. If you nest a long group of clips and try to time remap the nested clip, the clip will only partially time remap, and after a certain point everything goes black. That's all you have to do to reproduce it.

Report · Jun 12, 2024

@Kevin-Monahan I appreciate you being here for whatever reason 🙂 have sent you a dm

Report · Jun 12, 2024

@Kevin-Monahan AS @jmvdigital said

Add a few clips together in a nested sequence. Place said nested sequence on a timeline. Use keyframe within timeline to adjust speed ramp... notice how the footage disapears (black frame) randomly depending on speed ramp keyframe settings.

or as I said back in the mists of time

1. take a nested sequence, insert it onto timeline.

2. Double click on that nested sequence

3. Add another layer say halfway through that nested sequence,

4. Go back to your timeline and apply time remmapping (eg>300)

Result:

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

Here's a video
https://www.youtube.com/watch?v=CoUYqRoHXEo

Report · Jun 13, 2024

This problem is persisting for years. Nobody at Adobe cared, because bells and whistles are the hot stuff.

Now the "product team" asks the "support team" to "triage" old bug reports.

Is this a joke?!

Report · Jun 13, 2024

Hello, @andreask85831847,

Thanks for the response on this issue. I have asked the team about the issue and why it is persisting, and I will let you know what they say. Sorry for the frustration; only trying to help here.

Thanks,

Kevin

Report · Jun 17, 2024

video showing the error

Report · Jun 17, 2024

Hello @Águia Films,

Thanks for your video and bug report. The team is aware of the issue, has a repro case, and is working on a fix. I'm hoping we see this fix in the application soon.

Thank You,
Kevin

Adobe Community

Nested sequence time remapping bug

2 Pinned Replies