Can Adobe please make it very, VERY clear BEFORE the actual Premier Pro upgrade which banishes the extremely useful, reliable, easy and effective Legacy Titler into the rubbish bin of time? We will NOT upgrade PP after that date and are already looking at alternative edit systems. It is NOT a joke for many of us as learning a lesser tool to please the encoders is not what we want. I'm sorry, but there we are. We 'fix' ,version, tag, legalise and distribute many hundreds of TVCs made by others each year. 99% of static captions and legal supers are easily done with the LT. Why use After Effects and mogrt etc for everything? The LT upgrade path is NOT working - and we have little enough hair between us as it is.....Can someone out there suggest an aftermarket plugin which will do the same job as the LT???

Hey guys just want to bring a major bug to the attention of Adobe Staff here in Premiere Pro, every instance of bringing in a MOGRT from After effects containing a precomp I encounter that the 'Frame Hold" and "Insert frame hold segment" feature results in a blank or black frame rather than the desired still frame.

Another test using the same MOGRT animation without items within a precomp from After effects r appeared to work but only at the expense of losing 'Time Responsive' capabilities which are crucial to MOGRT workflow.

Other examples of imported MOGRT templates the Frame hold features are completely greyed out. total mystery.

I know i'm going to be told that I must utilize the Export frame workaround as I have seen this answer to this question answer said repeatedly in these forums in almost 6 years of Premiere Pro updates. But trust me I have a client who has to edit over multiple 3hr episodes with a ton of graphics who cannot afford to spend time doing this hundreds of times manually. And to sacrifice the 'Time Responsive capabilities' for layers from AE in my second example will also completely defeat the purpose of creating or using MOGRTS.

This clear bug which has been identified yet hasn't been fixed in nearly six years has unfortunately screwed our whole project pipeline. Many Hours digging through forums and trying work arounds has not given a direct answer to feature which should be working by now. Im basically a sitting duck here.

If any experts here can shed some light here on a solution or some intention in future to finally fix this bug (among many other issues) between AE and Premiere pro MOGRT workflows that would be fantastic.

Attempted these workflows on both 2020 and 2021 versions of both software

Thank you

I haven't Quite figured out the actual cause yet, but it's definitely a bug. Plus, in my opinion, it's Adobe's job to figure out the cause, not the consumer.
I have a sequence that has lots of clips and nested sequences. Some of them required some AfterEffects links. I think there are 3 different AE files being referenced.

Seemingly randomly, Premiere will tell me some, but not all, of the media is missing. If I save in premiere, close, then open again everything is found and fine. All of the after effects files are in the same location, and only a couple folders away from the premiere project file. So if one file is found, they All should be found. It's a bug.

Here's what I Think is happening, but have yet to confirm. I am guessing Premiere is assuming that all of the dynamic links are in the same AfterEffects project once you open one of them. I think this is only happening when I have Premiere and AE open at the same time.
In my case, one of the AE projects existed already and was imported into premiere. But then while that was open, a couple sequences were sent over to AE. As you probably know if you are reading this far, when you "Replace with AE composition" it sends it to whatever AE file is already open, or if none is open then it creates a brand new AE file.
My guess, is since Adobe is trying to do some path connections automatically, someone screwed it up and it doesn't work in cases that you have mixed methods of direct link, OR it just messes up occasionally if the premiere file is referencing multiple AE files.

It's time for a Christmas wish:

Port Premiere Pro, together with PS and LR and other Adobe CC products, to Linux.

As you are well aware, your competitor DaVinci Resolve is available on Linux. This was no doubt a decision to support professionals in the movie industry.

For the past 10 years I had to run these programs inside a Windows virtual machine with VFIO passthrough to be able to use Adobe products (see https://www.heiko-sieger.info/creating-a-windows-10-vm-on-the-amd-ryzen-9-3900x-using-qemu-4-0-and-vga-passthrough/).

It would be a lot more convenient to have it available on Linux, natively. I'm sure Hollywood would appreciate it, and so would many other users around the world.

Thank you in advance for consideration.