P: Nested sequence time remapping bug

[getho]

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

[getho]

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

[getho]

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

[federico27799673890i]

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

[jmohan00]

Bizzare workflow bug.
A clip : Stabilized > then nested > then Time Remapped> then nested > then Transformed.....
Goes black.

I am not familar with "SubSequences" yet.

Please correct me if my workflow is incorrect.

[Kevin-Monahan]

Hi @jmohan00,

Thanks for the note. What are the system and media specs? What about the size of the sequence and nested sequences? Are they oversized? Do you have scaling going on, as well? You might be out of VRAM. We need more info, please. See, How do I write a bug report?

Thanks,
Kevin

[jmohan00]

Hello Kevin, thnks for responding...

I am working with 4k 60fps videos.
The unexpected solution was to nest 1 final time (the final nest is 3 deep)

Bit bizzare , or my inexperiece with editing (vfx artist). or a bit of both.
I'm on Mac.
Regards,
JMohan

[Kevin-Monahan]

Thanks for the note. That's a little weird, but it's good to know, @jmohan00. I'm always suspicious of Xeon-based Macs. They were only out for one rev and may not have the goods you need for specific formats. For example, are you using H.264 or HEVC? I cannot verify if the CPU has Quick Sync, which is crucial for video processing in that format, especially when compositing or creating video effects.

See if changing to an editing codec like ProRes might perform as expected. Hope to hear back from you soon!

Take Care,
Kevin

[jmohan00]

The files are 60fps 4k directily from iphone, and reads as .mov in Premiere.

As it turns out, my additional nest failed. I ended up just rendering out that nested sequence as ProRes and dropped it back into timeline. No issue so far.

[Kevin-Monahan]

Good idea. That's what I usually do, as well.

[Uroš34682631qnwu]

How is this still not resolved?!?!

[jamieclarke]

Updating Status