I made a template for a diagram in AfterEffects and two CSV - one with 2-values (22,23) and one with 10-values (100,99,98,97,96...) - which i display via 10 text-layers. If a value is not given in the CSV the text-layer gets invisible.
Now when i import the MOGRT to Premiere it works fine, with the first CSV with all 10 values displayed (PP displays 10 values with 100,99,98,97...)
BUT when i import the same MOGRT-template a secound time into the same Premiere timeline and exchange the CSV of the MOGRTs with the CSV with only two values (22,23)... it displays only two text values BUT it uses the values of the first table. So instead of showing 22&23 it just displays the first two values of the original table (100,99)....

The same happens in After Effect when i import the project multiples times in a project to make multiple diagrams.

It is unfair that Premiere Pro users can only download the NVIDIA "Studio Driver" updates and not the "Game Driver" updates.

I use my PC heavily more for gaming and also Premier Pro for video editing. I updated my "game driver which lead to my Premier Pro freezing then crashing my whole PC every time I used it. I had to uninstall and go back a driver version. The issue was the "game driver" was not compatible with Premier Pro so I can only download the "Studio Driver" updates if I want to use Premier Pro...... this seems SO wrong and SO unfair.

Adobe - you're basically saying if we want to use your software, then we have to choose between, running our priority built high-end gaming PC's at half their potential because we are missing out on bug/glitch fixes as well as new software improvements, etc. or using your editing software. Because we cannot update our game drivers as this causes Premiere Pro to crash the entire PC.

PLEASE fix this issue so that Premier Pro & your software is compatible with BOTH the "Game Driver" and "Studio Driver"

This is a real serious issue!

When looking for a specific font, you begin to type the font name, but you can only type the first letter. For example, if I want to use a font called French-Script, I type F, and the first one on the list is Fabriche. Than, I have to scroll through dozens of fonts until I get to the one I want. If I'll type r (the next letter of the font's name) it will just "throw" me to the list of fonts starting with r.

Typing several letters is basic, just like when looking for something in a search engine. To get to Adobe you don't just write A, you write ado...

I have created a fairly basic animation in a MOGRT for lower thirds. There are two boxes that size responsively to the length of name and title. The animate on using track mattes. When imported into premiere on my machine they work fine. On a colleagues machine they do not. We both run Mac OS Catalina, latest version as of today. We also BOTH updated AE and Premiere to the latest version as of today. I'm attaching the MOGRT along with what the colleague sees. I'm hoping you'll actually get a different result if you import it yourself. (OK it appears I cannot upload .ZIP or .mogrt files. I'm happy to share these with you in some other way).

I have created a fairly basic animation in a MOGRT for lower thirds. There are two boxes that size responsively to the length of name and title. The animate on using track mattes. When imported into premiere on my machine they work fine. On a colleagues machine they do not. We both run Mac OS Catalina, latest version as of today. We also BOTH updated AE and Premiere to the latest version as of today. I'm attaching the MOGRT along with what the colleague sees. I'm hoping you'll actually get a different result if you import it yourself. (OK it appears I cannot upload .ZIP or .mogrt files. I'm happy to share these with you in some other way).

I have created a fairly basic animation in a MOGRT for lower thirds. There are two boxes that size responsively to the length of name and title. The animate on using track mattes. When imported into premiere on my machine they work fine. On a colleagues machine they do not. We both run Mac OS Catalina, latest version as of today. We also BOTH updated AE and Premiere to the latest version as of today. I'm attaching the MOGRT along with what the colleague sees. I'm hoping you'll actually get a different result if you import it yourself. (OK it appears I cannot upload .ZIP or .mogrt files. I'm happy to share these with you in some other way).

After typing a new title in the EGP, it's frustrating to have to press both 'Esc' followed by 'V' before the title can be moved or resized in the Program Monitor.

The approach used in the Legacy Titler is much better:
When typing a title, hitting 'Esc' automatically exits typing AND reverts back to the Selection tool in a single step.

This is a better approach for 3 reasons:
1. 1 step is easier/faster/less frustrating than 2 steps.
2. MANY titles consist of a single block of text, so while the EGP's approach does make it easier for a user to create additional blocks of texts (2 steps [Esc + click on new text location] vs 3 steps like in the Legacy Titler [Esc + T + click]), users would most often benefit from saving a step to modify their newly created title rather than saving a step to create an additional block of text within the same title.
3. It would keep the workflow consistent with the Legacy Titler, which isn't just more logical and useful, but also more familiar to long time Pr users.

Little quirks like this might not seem like a big deal, but they present repeated points of frustration. Pain points should be eliminated as much as possible when forcing users to transition from a legacy tool to a newer version of it.

The Render & Replace feature in Premiere Pro is great, especially for complex MOGRTs that will not play smoothly. It's much better than rendering the sequence, since we can still move the clip around without re-rendering. It's fantastic!

But the only option for MOGRTs that are not full screen (and most are not) and need an Alpha channel is GoPro Cineform. That's a very good codec, but it has some limitations that makes it unsuitable for non-broadcast frame sizes: The frame width must be evenly divisible by 16 and the frame height by 8. Adobe knows this: https://helpx.adobe.com/premiere-pro/using/gopro-cineform-codec.html#TipstoworkwiththeGoProCineFormcodecbr

This means that Render & Replace will fail in a 1080x1080 or 1080x1920 sequence for social media.
1080/16 = 67,5 – which is not an integer. The same is true for sequences that are 1350x1080. 1350/16 = 84,375 – which is not an integer.

These sizes are widely used in videos for Social Media! And we can't use Render & Replace (with alpha) when editing videos for them.
We can't have this nonsense anymore!

We need ProRes 4444 with alpha in addition to Cineform with alpha for Render & Replace. ProRes is much more flexible. Oh – and we need to be able to choose the default format. Or at least it should be sticky, so we don't have to change it every time.