Thats such awesome news Ole!

I haven't had time to dig in further on the asserts that came up for me but will have a better clue next week I estimate. Knowing that the file has lived a long life across updates is a good clue for us to know if something inadvertently changed along the way.

There are logs that you can enable under the Help top bar menu in AE. I'm not sure how helpful the logs would have been in this instance though.

Let me get a better understanding of what the specific corruption was and see if I can get you an alternative answer.

Thanks so much for your patience with all of this!

Cheers,
Dacia

Hi Dacia,

Your copy-paste trick into a new comp saved my mogrts! They are working now. Thank you so much. They come from a long-lived .aep file, that contains our Airlook and has gone through a few AE upgrades, so might be a cause.

As an enduser, is there something I can enable in a preference somewhere to get errors in a log or otherwise and see if my comps are messed up?

/ o

Oops,

Those attachments didn't go through so I added to this folder:
https://drive.google.com/drive/folders/1L3SEipbj8B-VfzfWzARKmuL8fqeSySoY?usp=sharing

Hi Ole,

Boy this one really has got me in knots.

I first tried to remove any time-based expressions thinking that maybe that was the cause of some buggy calculations happening when stretching the clip in PR. But that did not get me anywhere.

I then just started hacking away at the layers and getting to the core animation of the highlight box and even then I could still repro the bad re-timing issues with no problem.

I finally just decided to create a new comp and copy and paste the layers to start fresh and thats when AE started throwing asserts which are like tiny red flags that something has gone wrong.

Very interesting and more to investigate... but I was ultimately able to create a working Mogrt for you!

It seems like the original Parent Comp "highlight_text_line" was corrupted. After creating a new comp and copy/pasting all the existing layers and then adding new Protected Regions, I am getting the expected timing in Premiere that matches a non-stretched version of the original Mogrt.

I will circle up with devs to better understand the asserts I ran into today but there is a workaround for you for now.

I've attached the new Mogrt and some video for you to check out.

Please let me know if it works for you!

Cheers,

Hi Dacia,

I've tried your suggestions. Alas to no avail.

Attached is a collected Premiere project.

As you can see I've dived into the hierarchy of nested comps and exported the highlight_text_line comp directly as a mogrt and placed it along with a stretched version of the one with the nested precomps.

This should avoid the issues you mention, as this makes only one top layer of protected regions, but I'm afraid it doesn't

Hope that this example is useful. I've made a zip of a collected Premiere project for you to download:

https://files.denfrievilje.dk/sharing/TmENnFrH2

best / o

Hi Ole,

Thank you for your patience with this! There have been a lot of projects on the stove.

I took a look at the .AEPs for both Mogrts, and my main theory and the primary thing that stands out as a root cause of the retiming issues is that the GMAB_DR_STARTBOARD precomp is Time Re-Mapped in the Startskilt_Broken.aep.

Its stretched to 316.5%. Responsive Time Mogrts use Time Re-mapping under the hood and you are adding another layer of re-mapping to that. I think this is what is throwing the timing off.

There are no time-remapped layers occurring in the Toplogo_Working.aep. All layers are stretching uniformly, in other words.

My main recommendation would be to make the Pre-Comp layer the length of the Master Comp to maintain consistent Time Stretch Values (100%).

The other thing to note is that the only Protected Regions that are understood once the Mogrt is in Premiere Pro are the ones that are in the Master Comp. Any Protected Regions that are set in the Nested Comps are ignored on export as a Mogrt. This might actually be the real root of your issue because AE is able to process Nested Protected Regions while PR cannot.

I need to rebuild a few projects to confirm this but I wanted to give you some information to tinker with in the meantime.

Please let me know if my suggestion above does the trick for you,

Cheers,
Dacia

Dear Dacia

I would again like to hear if you have had any progress on this issue...

best / o

Hi again

Did you receive any progress on the issue?

/ o

Awesome thanks for sharing. I'll be in touch as soon as I learn more.

Thanks, Ole!

Here's a screencast where i introduce the problem

https://files.denfrievilje.dk/sharing/U648Tbmod

Also of note - the comp does work as expected when used internally in After Effects

Thank you Dacia for the quick response.

I'm working on macOS Mojave 10.14.6

The problem is that the protected in- and out- regions stretch proportionally with the duration in the non-working example. The expected behaviour is that they will retain their original timing.

Hi Ole,

Thanks for sharing these files and bringing this to our attention. Would you mind describing a little bit more about the failure to guide what I'm looking for? Is the issue that one of the nested comps is not respecting the Protected Regions and not re-timing?

Also are you on a Mac or Win?

Thanks so much and hope to have some answers for you soon,
Dacia

could it be related to the use of motion blur?