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

[scottm94441964]

I can confirm that if you switch to "Mercury Playback Engine Software Only" in the Project Settings, it does work, but playback is incredibly slow with 4k footage.

[getho]

Part of the problem with this bug is that in all the interactions I've had with adobe staff, they have all intimated that the existing behaviour is correct: sort of "you're not holding it right", type feedback.

I have listed this bug at least twice.

Here is a new video demonstrating the problem. I am happy to help with this. I use remapping all the time. For the last 3 years I have been having to render interim files for nested sequences that have layers.If anything is still in anyway not clear, or if anyone thinks this behavior is still as expected, I'm all ears.
https://youtu.be/CoUYqRoHXEo

This is the closest I have ever got at interacting with Adobe staff. Unfortunately they failed to read my post properly, and vanished once hoops had been jumped through:
https://community.adobe.com/t5/premiere-pro/nested-sequence-time-remapping-bug/td-p/9493724?page=1

[Caleb_B]

Just ran into this and a plethora of other issues which switching to "Mercury Playback Engine Software Only" fixed. I was having an incredibly frustrating problem where I had a nested sequence on V2 and when a non-nested sequence clip started on V1, the sequence on V2 would just completely disappear. Made NO SENSE because the nested sequence was on the top track. Sure enough, switching renderers solved it. Thanks for wasting hours of my life Adobe. Seriously considering the switch to Davinci Resolve 16.

[zerakh55607113]

same, just had this same bug. Wish they would fix this

[mantas malevskis]

!!! Please read this comment!!!

Just edited my video, the same issue happened. Only that if I understand correctly the issue everyone talks about I know the "solution" if that is the appropriate name for that until it gets fixed.

From what I understand when you make a nested sequence it is the sum of all videos combined. When you speed up, adobe premiere for some reason it speeds up those videos so fast that it shows only part of them and fills up the other part with black screen as if they weren't there. Also it leaves the entire nested sequence the same length before time remapping

When I realized that, I double clicked on it and did time remap on each video separately inside nested sequence.
Only now it shows up as completely correct time remap that I did inside, none of the media was chopped with that black screen and the only thing was left is to cut out the unnecessary black screen thing.

Hope that helps to understand what the problem is.

[Isra Velzen]

Still the same problem in 2021. Why is this not solved!

[nathanspowers]

Jesus Christ how is this not fixed by now?????

[andresr83054175]

Hi Adobe
Any updates? 3 years since this bug report... and still? Is there even any point in reporting these sort of things if there is no help to be found? Very sad.
EDIT (half solution):
Using right click and Speed/Duration to speed the clip up works - but when doing it with Time Remapping keyframes it makes the clip black in proportion to how much you speed it up...

[andrewm88104368]

This is still happening. Come on

[StevenPKT]

Wow, this is pathetic that this is still an issue. The difference in render time between using hardware acceleration and using software only is about 10 times longer with software only. Come on, Adobe, get with it.

[getho]

I first posted about this in 2017, I've seen posts from 2016 about it. But this is a mild snafu compared to the current time-remapping bug which is stopping me using premiere 14&15. As detailed:
https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/40471309-bug-time-remapping...

[RodHarlan]

My original link showing the Adobe Forum posts going back to 2016 reporting this problem no longer works in my original Bug Report post above because of site changes.

Here is the new link:
https://community.adobe.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&...

[Rajjeet5DC5]

Please fix. this is causing me hours of work here. My sad workaround is just not time mapping my clips and using the unnested version.

[BRGN]

Please fix. ****

[alexl1574]

I regret the day I ever made a nested sequence. Endless problems. Tried different work around suggested. nothing worked. FU!

[johnpooley3]

Please fix

[the-visuals-team]

seriously Adobe, you need to get this sorted.

[Hadi Mroueh]

I've had this issue for a while now, and now that I thought it through, I dont think its a bug...

The problem is that we've been mistaking the idea of a nested sequence with the idea of merging or join clips... the way to solve this issue is to render and replace rather than nest.

Nesting is the process of putting a few clips under one tab in order to perform edits collectively however this doesn't apply to time remapping or warp stabilising.

Thanks all, hope that helps.

[Mr. Wallet]

I had an outsourced support guy tell me "audio sync is hard, maybe look up some youtube videos", it was absolutely the most condescending support experience of my life.

It really comes down to frame holds and time remaps being janky in nested sequences. Unfortunately we have no choice as nested sequences are the only good way around things like "remap + warp stabilizer" or "Premiere is barfing all over itself on the last frame because the clip has a different framerate than the sequence".

Mod note: Profanity removed. Please do not use profanity. We have minors reading here.

User note: I respectfully disagree. The way I was treated by the support staff representing Adobe absolutely merits the use of profanity. Also, I never evade word filters, so how about implementing one like a proper bulletin board?

[mathewp63812871]

POSSIBLE FIX: I'm in PPRO 15.4.1 and I was trying to speed ramp two clips joined together (approaching a doorway, and going through the doorway) and the second clip was going black when speed ramping the nested sequence. I then nested both clips individually, then nested the individual nests and speed ramped that.

Wham bam thank you ma'am it worked.

[alexisb52811999]

Same issue here.. Any news from Adobe regarding this horrendous behavior?

[Mr. Wallet]

Hey guys, been a few months but I have some new insight on this: Clearly if you do anything significant with frame holds, time remaps, stabilization, etc. then you are expected to use Adobe After Effects.

For a couple years I was getting by just fine on premiere pro and only very rarely needed to do any advanced editing, and so I didn't have After Effects on my subscription. I encountered many many many many bugs regarding frame holds, time remapping, framerate mismatch, etc.

Recently I upgraded my license and it turns out After Effects doesn't have any of these bugs. The implication is clear: The large majority of professionals using these tools are not complaining to Adobe about this because the "standard" workflow through After Effects (using Premiere Pro just to stitch things together) is actually working pretty much fine. Even the Warp Stabilizer gets ASTONISHINGLY better results than the one in Premiere Pro, with exactly the same options.

The consequences of this are equally clear: Adobe is never going to fix this because it already "works" for enough people. Your options are to live with awkward workarounds and bugs, or suck it up and shovel more money at them for an upgraded license.

[Pierre21867288g4w8]

Quand je fait du montage sur première pro je passe plus de temps sur les forums à chercher comment contourner les bugs que finalement faire mon montage.

Mod note: Profanity removed.

[rik verstijnen]

Another workaround, which worked for me: Go to the source of the nested sequence. Select all tracks; enable multi-cam; disable multi-cam again. After that, the track containing the nested sequence did not show black screens anymore...

[motionben]

Also experiencing this bug when trying to remap a nested sequence. Using latest version of Premiere 2022.