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.
This bug is really causing me a lot of pain right now. The fact that this only happens when using GPU acceleration makes it extremely clear this is a bug. Please fix this, or if it's not possible to fix please just remove time remapping from premeire entirely.
Would be great if an Adobe employee on the bug team could share where this bug is in the queue.
There is certainly a Jira board or Project/Prod manager that's sole purpose is to make sure bugs are getting solved, daily, weekly, and monthly. With daily stand-ups, with the devs. Is this Bug stuck as a blocker and lost in the queue?
This was logged back in 2015 from what I've seen. It's almost been a decade since this bug has been resolved.
If the Adobe team simply shared the internal bug board it would eliminate a bloated support forum from duplicate posts spanning years. The work is already being done and managed. Just share what is being worked on and where in the roadmap we are.
If this bug roadmap already exists please link me.
I've had direct contact with adobe about this bug - they failed to acknowledge it as a bug (because they didn't try hard enough!)
I'm so used to it now I have 2 main workarounds: If a nested sequence includes a cut/more than one layer and you need to do a speed ramp on it in another timeline you can:
1. render it out. I now have a "bump" folder for every project for such things. Re-import it into premiere.
2. turn off cuda in prefferences, nest the ramped sequence and render that out as above
I've also got used to just avoiding it: for instance for doing property boundaries instead of using paths I used lumetri plus masks to do the same thing.
The more people complain about this, the more likely it is to be addressed. There used to be a lot of uservoice stuff about this bug, but I believe thats been deprecated or removed. I'm not sure at the mo how you even report bugs. TBH I'm in aholding pattern until I have the time to start using that Davinci Resolve licence I bought a year ago
54
Replies
AdChoices