Using After Effects 18.2.1 (2021), when Mercury Transmit is active, switching to a Composition that has different settings than the current one will cause the program to freeze.

I've tested Comps with different resolutions and frame rates and both changes cause the program to freeze.

I will try to describe a couple example scenarios below:

1) With Mercury Transmit active, if I have a 1920x1080 comp and I switch to a comp that has a 4K resolution, I get a spinning wheel (the program freezes) and my only option is to force quit.
Here is a video of this specific scenario:
https://vimeo.com/567992281/66425523fe

2) In a blank project I create and open a 4K 24fps CompA, and then duplicate CompA to make CompB. I open CompB and while it's open, change the frame rate to 29.97. (This works - changing comp settings while that comp is open doesn't seem to trigger a freeze.) Then I duplicate CompB to make CompC, and double click CompC to open it. So far everything works, and I can switch between CompB and CompC. However, if I switch back to CompA, which has a different frame rate, the program freezes.
Here is a video of this specific scenario:
https://vimeo.com/568009711/aab68cd83a

3) Finally this is just a weird example that shows how confusing this behavior can be:
https://vimeo.com/568015180/555eb55279

The examples above are specific but I should emphasize that working with Comps that have different settings with Mercury Transmit active is impossible for me to do normally without encountering freezes.

A solution is to toggle transmit on & off when switching between comps of different settings. Ideally though this wouldn't be necessary.

It's quite possible this is a bug that's specific to me and my setup, but I thought I would report it here anyway.

Here are my computer specs:
MacOS Mojave 10.14.6 - MacPro (Mid2010)
2.2.66 GHz 6-Core Intel Xeon / 128GB RAM - 1333 MHz DDR3
Radeon RX 580 8 GB
I'm using a dual monitor setup with the Mercury Transmit going to the 2nd 1920x1080 monitor (DELL U2417H) which is connected via HDMI cable. More details are at the end of the linked videos.

EDIT: It looks like this is the same issue as this one; I just didn't find it when searching for Mercury related bugs. I suppose I'm glad I'm not the only one encountering this.

https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/43035621-after-effects-2021-hangs-on-composition-opening

I've also attached a sample of the process while it was hanging.

When you create a new project through the "collect files" option, and try to render any output from that newly created file through AErender, it will fail to render. It appears that any mp4 used in the original project can be found initially - but doesn't have the correct icon which is strange - and then as soon as that file is called to be rendered, for example when the layer the file is on starts, the render crashes with the error that the cannot be found.

The issue goes away if you open the file manually once, to have it find all files, save it and close it - but this is a big issue for automated behaviour.

The full error messages reads as follows -
"The Motion Graphics Template has corrupt metadata and cannot be installed".

Is it possible to refresh the metadata in AE?

I have about 200 props in the EGP and will rather not have to rebuild the entire EGP again; especially when there's possibility of another breakdown.

Restarting AE didn't help. Importing the AEP into a blank AEP didn't help. Renaming the Comp didn't help.

A very strong possibility of this metadata mess seems to manifests itself with props in the EGP disappearing. They're still there since trying to re-populate the EGP with the missing prop throws an error stating the prop is already in the EGP. With such issues, closing and re-opening the Comp or EGP helps. However, user should have the ability to refresh/clean the metadata or something that helps to clean up the mess that starts when props disappear from the EGP.

Any assistance will be greatly appreciated.

Been having issues with latest AFX version (18.4.1) where the preview will freeze, or eventually become black, or not even display.

Latest NVIDIA drivers installed (471.68). Swapping between CUDA or Software rendering makes no difference. Same with hardware accelerating the interface.

As a side note, I am currently utilising Roto Brush 2, it's occurring when working on the layer or back into the main comp.

I am having to restart AFX to clear the issue and it's wasting a lot of time.

Update 23:05 - It seems to be more problematic when using the tilde key to expand the preview window. That seems to be a fairly sure fire way of causing the issue...

Dear Adobe, with After Effects CC2020 17.6 we have been experiencing MAJOR crashes. During rendering and sometimes scrubbing, AE just closes and goes to the desktop. It is a crash and then I have to send a bug report. I am attaching the crash logs to help you determine the issue.

We are on a Mac Pro with Big Sur 11.2 and we even tried removing ALL plugins and reinstalling all adobe software including reinstalling Big Sur, this issue is still persistent.

In the mean time we are dual booting into Catalina 10.15.7 to continue working and this is unprecedented. Please please please fix this issue, we want to use the latest macOS with your software but it's not possible.

When attempting to add a sourceRectAtTime() expression to a Mask Path property that references a text layer, After Effects will immediately crash upon evaluation.

Reproduction steps:
1. Create a new project
2. Create a new composition (tested with HDTV 1080 29.97 preset for repro purposes)
3. Add a text layer
4. Create a comp-size solid
5. Add a comp-size mask to the solid by double clicking the mask button
6. On the "Mask Path" property of the mask created in step 5, add the expression: `thisComp.layer(<name_of_text_layer>).sourceRectAtTime()

After clicking out of the expression editor and allowing AE to evaluate, After Effects crashes.

OS: Windows 10 Pro
OS Build: 19041.572
AE Version: 18.0.1 (Build 1)

If I'm running AE on Windows and the OS lanugage is Japanese, it is not possible to read the currently pressed keyname. It doesn't matter whether I use the ScriptUI.environment.keyboardState.keyName variable or whether I try to read it via a keydown eventListener, it always fails. It seems to affect all Adobe applications, see here:
https://community.adobe.com/t5/indesign-discussions/scriptui-environment-keyboardstate-keyname-is-returning-undefined-in-windows/m-p/11274854

If I switch my OS language to US or similar, it all works perfectly. If I switch it to Japanese again, reading the variable fails.

It would be really good if this could be fixed, as this is quite an important variable to read and it affects a lot of users.