Skip to main content
aTomician
Inspiring
April 12, 2018
Open for Voting

Add the ability to keyframe an imported After Effects MOGRT

  • April 12, 2018
  • 71 Antworten
  • 16392 Ansichten
It would be extremely useful to be able to keyframe the controls in Premiere Pro for a MOGRT (Motion Graphic Template) created in After FX. I create a template in AFX, add it to CC libraries, I can import this into Premiere and adjust the controls, but I can't keyframe them. This would take the power of MOGRT's to a whole new level.

I have extensively documented the process I'm trying to do here: https://forums.adobe.com/thread/255599

71 Antworten

Paul Slemmer
Participating Frequently
July 27, 2023

Thank you for the extensive suggestions for how to work around this! Genuinely helpful and there are some real gems in this.

Is there a reason why that communication between Pr and its tiny version of Ae can't be the subject of future development? Surely it can't require a complete rebuild of that version of Ae running within Premiere, just* a new pipeline for getting data into it? It seems like the reward on this one would make it worthy of some development resources.

*all this said, I know "just" may not be the appropriate word for the task at hand.

R Neil Haugen
Legend
July 27, 2023

Dacia, you really provide some wondrous help and ideas.

 

Thanks!

Everyone's mileage always varies ...
DaciaSaenz
Inspiring
July 27, 2023

Hi Y'all... 
This isn't supported because properties that get added to the Essential Graphics Panel and get exported to Mogrtland can only represent 1 value at a time. 
The control in Premiere can only tell Tiny Inception After Effects (nested inside Premiere Pro to make Mogrts work) “make this Opacity 60” ... it can’t tell Tiny Inception AE, “make the opacity go from 20 - 60 in 3 seconds from time 1 to time 4.”

 

It's a limitation in how the communication between Premiere and Tiny Inception AE works. 

One control can only be one value once we're in Premiere Pro.

 

But there are a couple of workarounds if we just abstract things a bit.

 

You can add add a few keyframes to a property and then add controls to those individual keyframes so that you can change those values once you're in Premiere. 


There are a couple of ways to accomplish this.

We could:

  • Add two sliders to control the value for each of the keyframes and then use a linear expression to make it all come together.

  • Or we could even hook up text controls to be the input control for those values.

I've added two example mogrts with each of these approaches in this link.

 

You can open up the Mogrt natively in AE with the following steps:

  1. Launch AE
  2. Use File > Open
  3. Select the Mogrt file
  4. Follow the dialog that pops up and asks you what folder you want top extract the project to
  5. and boom you've got the .aep
    Every Mogrt has the .aep and related media inside 
     

     

The Number Range mogrt uses two sliders to drive keyframe 1 and keyframe 2 values + a linear expression.
This is the most basic set up and the drawback here is that the animation gets distracting when the number goes from singles, to tens, to hundreds. We'd prefer the first number not to move on the first digit and just expand from there. You may already have an expression that is performing this for you in your project so you may need to do some work to marry these functions.

The second Mogrt in the link uses two text controls and a slightly different approach than the first to keep the numbers counting up smoothly. I wanted to be able to change the font and font style so I chose to use text controls. This means the end-user can only input numbers into the text control. But a comment in the Mogrt can easily guide this.

 

You may notice something different about this expression setup when you open it. I'm using a .jsx file with functions that make it a little bit easier to do some complex stuff. The .jsx file stores a ton of complex code that allows us to use simpler terms for functions, and add arguments to those functions in a clearer way. It's kind of like "wiggle()"... wiggle is actually a really complex block of code that got abstracted to something easier to use.

The .jsx file in the Mogrt I shared is a collection of functions that are meant to make complex expressions a bit easier to get into, and can improve performance.

 

There are about 40 functions that were designed with Mogrt authors in mind. 

 

My favorite solution to the "can't keyframe in Premiere problem" limitation is to use a combo of a few functions called "keyframesToControllers" and "retimeKeyframes" that give you the power to not only change the values of specific keyframes but also slip them in time. The other amazing thing about both of these functions is that your curves are respected even after making changes. Add Responsive Time to your Mogrt and rig some controls to some stand-in keyframes and you've got some basic keyframing-actions (i.e. setting values and changing them in time) in Premiere. 


Here are some links if you want to learn more about these.

 

 

There is also another collection of functions that are really cool too if you want to go down a rabbit hole.

 

 

I hope this gives you enough to get your Mogrt where you want! And please reach out if you have any follow-up questions.

Cheers,

Dacia

- Dacia Saenz, AE & PR Engineering Teams
Participant
January 24, 2023
Bump. Running into this issue now and could use this feature request
Participant
January 24, 2023
Bumping this again! Being able to keframe e.g. the Position of a layer inside the EGP would make EG sooooooo much better! I have already read in this thread that I am not alone with MOGRTs that have lines running from a POI to the corresponding text layer. It already is great that you can adapt the position of the POI but on a video that point never is still, so being able to keyframe that POI and animate its position seems so sensibel! Please, Adobe. Make! It! Happen!
Inspiring
January 24, 2023
Hello Adobe, time to take the next step and make Premiere Pro even more PRO? 🙂
What is the status on this one?
Participant
January 24, 2023
For my use case, a 'List' animation is created, where the keyframing could be used to expose indexed lines in a text animation. It would be very convenient to keyframe the active lines so that the client could control when list entries become visible. Graphical personality could then be introduced at the animation level as well. This could keep the clients workload down to "write the list" and "select visible lines" with optional fade-in / fade-out mechanisms.

It would also be convenient if the mogrt in PrPro could utilize markers to indicate progress. This would allow parameters to be enforced uniformly across all transition points. I yield that this is slightly trivial since keyframes could accomplish all of this, but there are already supported effects (Opacity Flash - Layer Markers) that provide this sort of a workflow and it seems reasonable to consider such a mechanism.

Crude example attached. The start/end essential properties support a dynamic keyframing that the user can control, but they have to splice multiple mogrts back-to-back to simulate list progression over talking points. Keyframing would just allow a single slider to indicate the end of the list, or even start/end sliders could be separated and used.
aTomician
Inspiring
January 24, 2023
Thanks Mike, really appreciate your response.

Paul and Levi, this may or may not help but I've had some success with a few workarounds:

- One thing I've done is add duration controls, and tied the animation in with a duration. I can set the duration of either the whole mogrt or an individual effect, and the animation changes it's speed or timing based on that.

- For following a tracking point, I've overlaid 2 mogrts before where one entire clip follows the motion tracking using the standard Motion controls, the other clip is static but both tie together at the same position which can be entered into both mogrts. Hacky but it did the trick.

- I also considered making a script that could insert a mogrt over and over, each is one frame duration, and the script would set certain values for the controls, effectively a makeshift animated mogrt. I haven't needed it enough yet to seriously look into this though and whether it can be done.

I've attached an screenshot of one that uses a duration slider to control how long before the graphic animates out. I think this one also used the length of the text to change some animation timings too. So simple animating can be done by building it in, but it's much more complex.
Regards, aTomician
Adobe Employee
January 24, 2023
Hi Paul -

The complications are not at the UI/UX level. They are at the communication level between the Pr and AE code, particularly for mogrts that require dynamic link.

Mike
Paul Slemmer
Participating Frequently
January 24, 2023
I'll add my voice to this thread and say this feature would be extremely useful for the creation of more detailed text templates as mogrts.

I'm the creator of a very simple but widely used preset for text in AE. Myself and now my users have noticed the benefit of using this preset in mogrts for Premiere. That's already been done with much success, but exposing the timing functionality to Pr would only be possible if keyframe and/or marker tracks were modifiable in Pr.

As mentioned in the forum thread, the UI for this is all there if you right click the fx icon on a mogrt in the timeline. To be a little bold, I find it unacceptable that adding this functionality has not been addressed in the almost 4 years since its posting, as it affects a flagship feature of not one but two apps. In fact, the presence of a vestigal UI that does nothing should qualify this as a bug not a nice-to-have.

In addition to the use cases described, this is a relevant topic to some time artifacts when using Protected Regions, namely that any looping/random motion in the unprotected regions is sped up. Short of overhauling that feature, the addition of keyframe-able essential graphics properties would give mogrt creators a different pipeline to use if such time artifacts affect them.

If any of the complications mentioned are related to decisions in functionality (how keyframes are overridden, etc) I would be more than happy to work with the development team to understand how those decisions would be perceived from the user's end.