Responsive Design - Time is still not 100% accurate
The Reset Duration saved our team from the ongoing timing issue.
However, when I stretch the mogrt in the sequence, the protective region gets stretched a little bit. It's more noticeable when I stretch it more than 1000%. It's a problem when I need to add more than one template with different durations.
For now, the only way to fix it is by Reset Duration.
The fact that I have to hit Reset Duration over and over when the timing gets changed is annoying, and also our team is not allowed to update Premiere Pro to CC 2020 yet which has the Reset Duration feature.
Thanks to great information from users, we were able to nab what appeared to be the true root of the issue, a problem with the timing getting wiped from the project if no explicit interaction had been made with the timeline (like muting or unmuting a track).
If you head over to the Creative Cloud Desktop App and navigate to the Beta Apps section, you can download the Beta version of Premiere Pro (any version after 14.6 × 46) and the fix should be in!
Please let me know if the issues still occur for you, though. We want to put this one away for good, and are hopeful this time. Those zombie bugs are wild though!
The Reset Duration option is still available if needed as well.
I talked to one of the devs that created Responsive Design - Time and the mapping of the calculations needed to deliver the correct frame after a retime are more likely to get out of sync the greater the stretch.
From your observations, do you know how many frames the protected regions are being extended by? If you could share a screen recording and the Mogrt in question that would be really helpful.
Sorry you are unable to upgrade to the latest release yet. The new Reset Duration function is really helpful and was meant to address some of the frame rate issues that can occur.
I'm curious what the scenario is when you say: "The fact that I have to hit Reset Duration over and over when the timing gets changed is annoying." All of the reports we have received related to re-timing issues have been happening after a project close and re-open, or when users were opening the same project across different machines. Is your experience that the re-timed Mogrts are losing the expected speed within the same session? I would definitely love to get a sample project and screen recordings in house if thats the case.
Side note, it is possible to multi-select all of your Mogrts at once and use the Reset Duration one time. Hopefully that will cut down on some of the extra clicks.