P: Nested sequence time remapping bug

Well they did update the status to acknowledged. Whatever that means.

How is this not fixed yet, have adobe acknowledged an issue yet. Its nearly 2025 guys. This was 8 years ago

Updating Status

How is this still not resolved?!?!

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

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.

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

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

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

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.