Hello! Since upgrading my Adobe suite to the latest 2022 versions I haven't been able to export my files from After Effects to the Media Encoder. When I'm ready to render I'll go to "File > Export > Add to Adobe Media Encoder Queue..." as usual, but nothing actually shows up in Media Encoder's Queue. I've sat and waited long enough, staring at Media Encoder, mentally willing the file to go through the dynamic link that my boss started poking at me with a sharp stick to see if I was still alive... I've had a similar lack of luck exporting from AE to ME in different ways.

I've removed all the third party plugins I could identify and find, but that didn't help either. I've restarted the software probably nineteen times, and have rebooted my iMac several times as well, but alas and alackaday, the problem persists. I've fiddled with various settings in AE and ME, but...

If anyone has a solution to this I'd be very grateful! (At the moment I'm using the "export via AE as a .MOV, import the .MOV to ME, export as H.264" workaround, but that's adding several steps to my workflow.)

I'm working on a Late 2015 27" iMac with Big Sur (v. 11.6), 32 GB RAM.

Error 83::2 - String Memory Leak
I get this error message every time I log out of AE 2019 whilst using one particular project that involves a lot of imports. Will not open the files again later. I can work around it by importing the file into a new project, but once I save the NEW project, under a different name and go to quit the program, I get the same error message and rinse and repeat. I don't know which, if any, files are corrupt and the program otherwise acts normally until I try and close out the program.It doesn't generate an error report or anything, so I can't access that. When I try to reopen, whatever the error is causes the files to open part way, and then the application stops responding. Any thoughts? I've lost HOURS of work on this project every time.

I recently upgraded to a 4K monitor. Now RAM previews consistently do not play back real-time. Changing the resolution of the monitor to 1080p OR resizing the entire After Effects application window to a quarter screen results perfect playback. I've tested this on several other workstations that either have 1080p or 4K monitors and have been able to reproduce this. They all have different graphic cards and plenty of RAM. I've played around changing the MST settings on the display without any changes.

Tested on several versions of:
Windows 10 Pro
nVidia 1070's / 1080's
32 GB Ram

Latest nVidia drivers plus several previous versions tested.

Latest After Effects: 15.1.2 (Build 69)

Access text properties (kerning, font size, leading, etc) via scripting
We need more access to text properties via scripting. It will be helpful to change, for example, the font size of a text layer via scripting, that way the textbox stay the same size becouse right now I can only change the scale of the layer and it changes all proportions of the layer (height and with in pixels, size of the textbox).
If we can access to that properties via scripting we can let all LayerObject attributes the same (textboxes, width, height, scale) and only change font size, leading, kerning, tracking, text stroke width, color, etc).

Thanks for your time and sorry for my english.

Currently the biggest bottleneck or noticeable speed degredation for me after getting a CPU with more cores and a lower clockspeed has been shape layers and vectors. If I have a comp with lets say 100 small shape circles, the FPS in After Effects drops to such a low level it is hard to even work. Since things are being optimized in After Effects and tasks are being moved to the GPU, this is one area of the program I would really like to be improved. Shapes and vector layers are very commonly used, so it shouldn't be such a huge bottleneck with modern hardware.

In both AE 17.0.0 and 17.0.2, I did not test it in 17.0.1. Using Win10 with a Ryzen 3700x and a GTX 1060 6gb

When editing or writing expressions while in the graph view mode, it is hit or miss whether or not the new code will be commited.

It was suggested by another user to use the 'enter' key on the numpad to commit changes, but this didn't work every time either, so it doesn't solve the problem.

When editing expressions in the normal layer view everything works and saves/updates as it should. You just type out the code and then click off and it commits those changes. It should work the same in the graph view but it doesn't seem to.

I've attached a screen capture to show what is happening.