P: Nested sequence time remapping bug

Same problem here, it is the same in all Premiere versions I had 😞

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

video showing the error

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

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?!

@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

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

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. 

Hi Kevin, 

Willl send you a DM

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