Motion Graphics - Limits & Frustrations when put to actual use.

[Premiopolis]

Here are some of the limits we ran into testing for use in an actual post-production workflow.

Presumes the following environment:

- Complex timelines with many Motion Graphics templates and many instances of each template both in one sequence and across multiple sequences

- On-the-fly changes being made a) to the design of the templates, b) to the text and properties in the instances, c) quantity of property controls passed from AE to PPRo

#1: The only way we're able to introduce a MOGRT (Motion Graphics) file into the project is by dragging it into a timeline.  Can't drag to a the project panel, a bin, or even the Essential Graphics-generated "Motion Graphics Templates Media" bin.   Dragging into the timeline is not exactly optimal.  Risky.  Easy to accidentally over-write existing timeline cuts.  This is more of an inconvenience than a deal-breaker.  The following are more problematic

#2: We haven't found a way to update an existing Motion Graphic at the PPro project level.  If we update a template in AE we're forced to re-import/re-introduce the updated version to our PPro project.  It arrives as a new (same-named) template that can't be linked or merged with the prior.  In order to update sequences with the new template, we have to select all related instances and execute a "Replace Clip With..."  That's ok for smaller, simpler projects.  It's a deal-breaker for larger, more complex ones.  Why...

• In a complex project there's no easy way to quickly and accurately select all the timeline instances relating to one particular template, shy of using dedicated tracks, or some JSX.
• If there are multiple sequences all sharing multiple instances of Motion Graphics of Templates the prospect of constantly updating all of quickly becomes daunting.
• It's an inefficient, time-consuming process.

#3: Even after updating Motion Graphics timeline instances, the updated instances don't reflect certain changes made at the AE context, namely additions or changes in property controls.  The only solution to that we've been able to come up with involves over-cutting the new Motion Graphic into the timeline.  That means losing any text entries or property settings.  That takes more time, introduces more risk than #2 above.

Curious to know if we're just over-looking something -- that there is some way to replace Motion Graphics at the project level that includes all style and property changes.  Would love to know we can overcome these limitations.  Otherwise, for our purposes, Motion Graphics are a brilliant, promising new development with great potential but which are self-defeating in a complex, professional post-prod workflow.  And yet that's precisely the environment to which Motion Graphics seem best suited.

[SquareEyz]

Thank you so much for your time describing your workflow!  Sounds awesome

All the best, fingers crossed for MOGRTs getting developed into something we can really use!

D

[jstrawn]

Indeed. A way to update your ae-mogrt designs without changing the textual content of the ae items in your timeline is clearly needed. The reason you can't just relink, or something like that, is because they just work differently. So there is no simple fix and there are many contingencies to plan for, like what happens when the user adds or removes editable params on the Ae side before re-exporting.

Pr-mogrts, on the other hand, already have most of what you need in the form of Responsive Design and Master Styles.

[Premiopolis]

jstrawn  wrote

The reason you can't just relink, or something like that, is because they just work differently.

I imagine, of course.  Though considering LTTs are capable of handling updates of all kinds, it would seem possible (not necessarily easy) to achieve the same with a MOGRT.  Really I'm angling to have my cake and eat it too.  The features in both LTTs and MOGRTS are really forward thinking and mighty welcome.   The moment you see sliders, or the ability to pass or limit controllers in a PPro Mogrt you want them in an LTT.

jstrawn  wrote

Pr-mogrts, on the other hand, already have most of what you need in the form of Responsive Design and Master Styles.

In our case we're looking at design that is not just "responsive" but dynamic, driven by external datasets.  Whether it's game show data or science-heavy shows, we're looking to develop design ideas influenced by increasingly elaborate ideas.  For that we need expressions, hence AE.

[MyerPj]

jstrawn  wrote

like what happens when the user adds or removes editable params on the Ae side before re-exporting.

But that should be on the user. If the user removes editable params, they should be removed at the instance also. If they add a param, then is should become available and use the default value of whatever is in the comp - even a blank value.

[jstrawn]

That was just one example of the sorts of things that need to be considered. All these things must be thoughtfully designed and then built.