Skip to main content
mark.west0675
mark.west0675
Participant
September 15, 2021
Answered

mogrt with RDT not working in Premiere Pro

  • September 15, 2021
  • 1 reply
  • 1439 views

Hello. I have created the attached lower third for a client and need to export it to them as a .mogrt for them to use.  I have been trying to get the responsive time to work properly in Premiere, but when I export it as a mogrt and import into the essential graphics template in Premiere, it does not maintain the protected regions / behave as expected in the timeline.  I have been searching for an answer for days.  Please help me get past this issue.  Thank you in advance!

 

AE- v 18.4.1

PrP- v 15.4.1

This topic has been closed for replies.
Correct answer Rick Gerard

I looked at your project. It's way more complicated than it needs to be with lots of keyframes and a nested comp, and something is going on in the main comp that is fouling up the Protected regions. 

 

Try creating a new comp, copy all of the layers in the Main Comp and paste them into the new one, add a comp marker at the first frame (0:00:00:00) and convert it to a protected region, then select all layers and press U to reveal the keyframes in the comp. Use the K key to move to the first keyframe that starts the ending animation and add another comp marker by pressing * and convert it to a protected region. Now drag the end of the protected region to the out point of the longest layer and set the work area to the same point. 

 

Finish setting up your Extended Graphics Panel, pick the new comp as the source and add your controls. That should fix the problem. It did for me. 

 

Somehow, when you were creating the project, one of the markers you added fouled up the comp so that deleting markers and protected regions and resetting markers would not fix the problem. 

 

I have seen this kind of thing before. I'm not sure what causes it, but the workflow I just described should fix the problem.

1 reply

R
Community Expert
Rick GerardCommunity ExpertCorrect answer
Community Expert
September 16, 2021

I looked at your project. It's way more complicated than it needs to be with lots of keyframes and a nested comp, and something is going on in the main comp that is fouling up the Protected regions. 

 

Try creating a new comp, copy all of the layers in the Main Comp and paste them into the new one, add a comp marker at the first frame (0:00:00:00) and convert it to a protected region, then select all layers and press U to reveal the keyframes in the comp. Use the K key to move to the first keyframe that starts the ending animation and add another comp marker by pressing * and convert it to a protected region. Now drag the end of the protected region to the out point of the longest layer and set the work area to the same point. 

 

Finish setting up your Extended Graphics Panel, pick the new comp as the source and add your controls. That should fix the problem. It did for me. 

 

Somehow, when you were creating the project, one of the markers you added fouled up the comp so that deleting markers and protected regions and resetting markers would not fix the problem. 

 

I have seen this kind of thing before. I'm not sure what causes it, but the workflow I just described should fix the problem.

    mark.west0675
    mark.west0675Author
    Participant
    September 16, 2021

    That worked!  Thank you.

     

    You're right.  This animation is built in a lot more complex format than it needs to be...but there's a logical reason.  This "simple" animation is actually leveraging "approved" assets from a much larger array of show elements (open, bumpers, close, etc.) with many more variables all tied to simple controls in those sequences (mogrts).  This is easily the simplest element of all of them (and thus frustrating for me that it was giving me such issues.)  My thought was, after all of the back and forth with the art directors and so on through different versions and tweaks, copying the "approved element" layers out of the more complex sequences and pasting them into a new sequence to create the lower third would be the simplest way to make avoid any chance that an art director would make further adjustments.  In hindsight, it would have been much easier to just recreate the elements from scratch and avoid the issues I've had with this comp/mogrt. ...but who knew.

     

    Thanks for your help in cracking the case!

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices