@eduardo

Hi. I downloaded your zip and opened snap_bubble_rounded_arrow.mogrt in AE. There is no protected region marker in the comp 05_Bubble_rounded_arrow which is why it does not have responsive time in Pr.

Mike

Not, it is not solved at all.

All update (AE and PR) and it still not working!!!!

Sorry for the delayed response - I don't think I was notified when you answered, or at least not via email.

The important part: I have since "solved" (ie. "worked around") the bug by using separate folders for each project file. It creates separate Motion Graphics Template Media folders and presumably prevents collisions.

There was no particular reason for using the same folder for all, so it won't be a problem to separate things this way going forward.

As for the details:
- When I refered to a "master Mogrt" I was refering to the .mogrt file as exported from AE. In that terminology, the .aegraphic would be the "post-import, project-specific Mogrt" - I didn't realize these files were the byproduct of importing a .mogrt when I used the "master Mogrt" expression, sorry for generating additional cryptic terms.
- I don't think Reset Duration worked *all the time*, but I didn't capture a situation where it didn't so maybe I'm not remembering it right - in any case, I reimported the .mogrt with my new folder setup and it worked fine

Thanks for jumping on the case anyway, I'll make sure to record examples if it resurfaces.

NO Pierre!! Say it isn't so!

Can you please share a screen recording of what you're seeing and the Mogrt in question?
Is it possible that you have a couple of different versions of the same (named) aegraphic in the Motion Graphics Template Media folder in your project panel?

Often times this bug has happened when there are multiple versions of the same Mogrt (which when added to the sequence is unpacked as an .aegraphic and that's what lives in your project panel). Relinking can end up reconnecting to a different version of the .aegraphic than what was used to set the re-timing in the first place. Deleting any duplicates is a great place to start. Have you tried the Reset Duration option to force the Mogrt back to the timing defined by the length of the track item?

I'm not sure what you mean by Master Mogrt but would love to know more.

Thanks and apologies for the inconveniences,
Dacia

I'm sorry to report that the zombie big is alive - as of 15.4.1 for Mac, at least.

Is there a way to organize my files that would make the bug disappear?

From reading the back-and-forth below, I think I understand it to be related with MOGRT instantiation. Would I be able to have separate "master MOGRT" for each project to avoid conflicts across projects?

** UPDATE!! **

Thanks to some great information from Alexander Toth (a few comments below)... 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 x 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!

Cheers,
Dacia

Reset duration is good, but not a real fix. The timing problems have gotten bad and frequent. At this point I'm not very comfortable sharing project with people since they will likely need to reset duration and might not know to. I really shouldn't have to tell them to do that either.

Anyone still experiencing this issue? Our customers are reporting that it's still happening, moreover the "Reset Duration" feature doesn't seem to always work.

I've added sample my project here: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38046811-mogrts-with-protected-regions-created-in-ae-are-so

~ Alexander

It is my mistake. I had put the protected regions in a comp subordinate to the comp the mogrt was based on. Moving the protected regions to that comp corrected the problem. Thanks much to Adobe support engineers!

It doesn't seem to be resolved. I am using AE 17.1.1, and PPro 14.3.0 build 38, Windows 10 Pro version 10.0.18362 buld 18362. I created a mogrt in AE with a protected area on the beginning and ending of the mogrt. In Premiere Pro, when I used the rate stretch tool to change the duration of the mogrt, the beginning and ending protected areas lengthen along with the mogrt, instead of staying constant. The "reset duration" item on the "graphics" menu is greyed out.

I am attaching the mogrt. The only animation on this mogrt is a two-second opacity fade-in at the beginning and fade-out at the ending. I double the length of the mogrt with the rate stretch tool in Premiere Pro, and both animations double to four seconds. "Reset duration" is greyed out.

If I use the selection tool in PPro, it won’t let lengthen the Monet on the timeline, and if I shorten it, the ending animation just gets chopped off.

thks!

Thanks Dacia! Now please give us a chance to Render & Replace MOGRTs in sequences that are 1080 pixels wide. We need ProRes 4444 in addition to Cineform with Alpha. :)

Hi All!

I'm thrilled to finally be able to announce that the Premiere Pro v. 14.0.1 that was released last night has new functionality to help resolve issues that happen when the retiming of a Responsive Time Mogrt gets out of whack.

We've added a new function called “Reset Duration” in the Graphics top bar menu, which will use the length of the track item in the timeline as the single source of truth for how long the Mogrt should be retimed to. So if anything ends too early all you have to do is select the Mogrt in the timeline, use the Reset Duration command in the top bar Graphics menu, and voila!

This will also work with multiple selections at a time.
No more manual re-trimming or redundant work.

The primary source of the issue stems from relinking to the Mogrt's aegraphic file in the Motion Graphics Template Media folder. Having multiple projects pointing to the same root aegraphic or moving the project around and relinking to a different version of the same Mogrt can also get users into this state.

Hopefully this will help resolve some of the headaches that y'all have been experiencing. We tested a ton of scenarios, but you creative powerhouses work in a plethora of amazing ways that we cannot always predict. Please feel free to reach out if anything weird continues.

Hope everyone's New Year is off to a great start,
Dacia

...same problem. Any solutions so far?

..with the difference that I'm on a mac.

I have the exact same problem. https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38046811-mogrts-with-protected-regions-created-in-ae-are-so?edit=1

Super huge shout out to Jessie and her team!

They were able to provide a few key insights that finally helped us set up the proper environment to get this bug to reproduce here for the developers.
The bug is officially filed and we are investigating a fix.

Thanks for all your patience y'all. I know this is a pain point for many of you and I will update the channel as soon as I can publicly announce the fix.

I have the same problem.
I know how to reproduce it. 1) you create a heavy mogrt with protected regions that are within the comp that is also with protected regions and already retimed in the first level comp. 2) you edit it in premiere change speed and duration stretch etc, duplicate several times. change its controls, then save the project and reopen. It won't be the same. somewhere randomly especially at the end animation of each mogrt you might see it freezed or cut the end animation or hide the controls (like Premiere's not loading the whole mogrt).
also could provide built mogrt that envisions this bug.

Dacia, thanks for responding!

I'll respond to your email with the attachments. Not sure why they didn't go through :(

To answer your second comment, the 2 editors at my workplace, plus myself, who've experienced the problem can't see when the glitch happens, they only catch it after playing back the video in the timeline after time has passed. In one Editor's case, the project was left open overnight, and in the other's, Premiere was closed for the night and then reopened the next day.

I'll email you more details!