After Effects (Beta)

We have improved our display pipeline to provide smoother playback and to reduce screen tearing artifacts. The change is effective in the latest public betas of Premiere Pro and After Effects.The changes we've made slightly increase memory usage, so the improvements are available on computers with a GPU that have 2 GB or more of VRAM.If you have been affected by screen tearing, we'd love to get your feedback on this change.

After a very loooong journey I have finally merged a very significant revision with ae23.5_13 to the code in After Effects which manages Fonts.   Some example immediate benefits to this code revision:   • Apple’s SF Pro and New York, and other Open Type Variable fonts will start working properly.• Duplicate fonts, by PostScript name, will show properly in the UI and also stop crashing After Effects.• Copying and pasting text from Illustrator with a Open Type Variable font using custom design axes will come through correctly - After Effects UI still lags what AI offers but it is better than the useless “0 0 0” we used to show.• The Char Panel UI is going to behave a little less wonky than before - it still has some flaws (ex: sample drawing, mixed selections) - but it is quicker and less sloppy at points.• Substitute fonts, that is fonts which a Project asked for on open but did not exist, now show the PostScript name and font technology we know about. They sort at the bo

Text Animation by Character and Word has been Left to Right (Roman)-centric since the beginning and consequently in the case of Right to Left languages such as Hebrew and Arabic it was 100% wrong (unless your content was a single character or single word!) Essentially the code assumed that the order the glyphs appear on the screen is the same as the character order but that is only true for Left to Right. For a line of Hebrew text, for example, the glyph on the left is actually the last character and the glyph on the right is the first character. Consider with the following Text Animation settings: With Roman text it looks correct as we scrub about half way - first character in the Story is the "R": But not so good with Hebrew text where the first character in the Story is on the far right. See how the left glyphs have been exposed before the right most ones? Bad. With Beta build 22.3.0 (89) this has now been addressed and After Effects is properly iterating th

The Solids folder names itself to"Farbflächen" even if in the Prefs it is set to be auto-named to Solids

We have a mix of windows and MacOS machines, with a mix of AE versions. when creating a project on Windows, AE 23.0.0, using the 'Poppins' typeface from Adobe Fonts, it creates a version seemingly incompatible with AE latest Beta (23.5x26) on MacOS, showing as [Poppins-Light/Type1].When opening the project in AE 23.3 on MacOS, it shows (renders and in the character dropdown) fine, but the render times are >100x slower (123ms vs 1ms). I can resolve this by switching the font from 'Light' to 'Standard' and back again.  If the resolved project is then opened again on Windows, AE 23.0, the issue returns, and the typeface gets replaced with the windows specific version. Seemingly, the improvements to the font system are now exposing that something incorrect is happening in the background.I've included 2 project files, 1 that includes the windows typeface, and shows slow render times on MacOS 23.3, and incompatible Typeface on AE 23.5. The other file has the issue resolved

Please help me, I am no expert, still learning. Why is make comp size greyed out??? is there an issue with my file? I have mercury software only enabled, followed various tutorials.. what am I doing wrong??? thank you

Latest beta (23.5x12) won't lunch for me. It gets through Initializing MediaCore, then just vanishes shorly after that. When I try to relaunch, it offers to let me launch in safe mode, which desn't help. I've done a couple of rounds of uninstall and reinstall, but no luck. I've retreated to 23.4x48, which seems to work fine.

Hey beta users!    Starting today (August 1), the After Effects beta will save in project version 23.0. This means that projects saved in the 23.0 beta will not be able to be opened in other versions of After Effects (including the 22.5 public release) without file conversion.    If you need compatibility with 22.x or before, please follow the instructions below:  Moving from v22.x to v23.0 - On opening a project in the 23.0 beta, you will be presented with a message that the project needs to be converted. Simply click “Ok”, and the project will be updated automatically. If you would like to preserve your 22.x version of the project, please be sure to “Save as” the 23.0 project so that you don't need to convert again in the future.  Moving from v23.0 to earlier versions of After Effects (I.e. 22.x or below) - Please use the option Save As > Save a copy as v22/v18 to create a project that is compatible with older AE versions.  We apologize fo

Hi, I'm setting lots of expressions to comps & layers via a jsx file.In current versions I have no problems, but the Beta app (23.4.0) gives me errors, while there are none... What the issue probably is, is that I'm setting e.g._ references to effects (and ffx files) which are not applied yet_ linking to layer names in compositions which are renamed afterwards in the jsx file etc... So it seems that the Beta version is evaluating expression on the fly, while current AE versions check the expressions afterwards.I tried to fix some issues with "autoFixExpressions", but that doesn't work in this case... Is there anything to worry about when the new release comes out, or will this behaviour of "evaluating expressions" change?The reason I ask, is because it's a bit clumsy to go through "expression errors" only to click them away and be totally fine at the end. Anyhow, hope to hear from you, Jochem

Hi All,   We've made some changes to the Default Workspace in Beta, and we'd like to hear your thoughts!   These changes will not impact any custom workspace settings you have. To see the new Default Workspace, click the hamburger menu next to "Default" in the workspace toolbar, then select "Reset to Saved Layout". Please note that if you have previously changed and saved over the Default Workspace, you will have to reset your preferences to see the new Default Workspace.     In the new Default Workspace, the Libraries Panel is nested horizontally with the Project Panel on the left-hand side of the workspace. The Info Panel is stacked on top of the right-hand side, with Preview, Align, and Audio Panels nested horizontally. The Properties Panel is stacked directly below the Info Panel, with the Effects and Presets Panel nested horizontally.   Tell us what you think! Do you like the new Default Workspace? Do you hate it? Other thoughts? Your feedback is critica

Hi @Christine Goldby, thanks for all of your work here on the support community site. I've been testing the new After Effects 3d features this week for use on our web-video project. The project requires 3d artwork to be rendered out in .webm format with transparency support.   It seems the only way to get .webm output out of Adobe products is using an external plugin from www.fnordware.com This enables the Media Encoder (Beta) to output in .webm format w/ transparency, but I have run into some issues with ME rendering Adobe After Effects (Beta) files that include 3d objects. - Compositions including an .obj file are able to be rendered out, but the renderer ignores the 3d layers in the composition.- Compositions including a .glb file are not even recognised by the Media Encoder, you receive a "Could not locate file" error. Both of these errors occur while using the Mercury rendering engine.   For now I've found a workaround by outputting a Quicktime .MOV from A

Hello everyone,I am currently working on a project with After effects Beta (23.5), in my project I use 3D elements in .glb format.The problem is that it is impossible to export it to mp4 format because every time there is this error that appears.I wanted to know if any of you have managed to export projects correctly from after effects Beta and if so how did you do it?Thanks 

 Select a text layer.Choose Animation > Browse Presets…In Adobe Bridge, choose a text effect to apply. Result: ...Error: Can't import file "[name-of-effect.ffx": unsupported filetype or extension. (0::1)Expected: Animation Preset should be applied. This works as expected (no error) in AE 22 (non beta). System info    Application: After Effects (Beta) v22.2.0.59    M1 Mac mini, OS: macOS v11.6.2, RAM: 16.00 GB, CPUs (logical): 8

Can't assign F10 Key in keyboard editor or in custom .keys file. Why.    Steps:  Try to assign f10 "That key may not be reassigned." Try to edit keyboard shortcut file so I can use F10 for my Designated purpose....keyboard file reverts to earlier state. 

No matter what my permissions settings on the folders, I constantly get this "An error occurred migrating the settings files. Check the permissions of the After Effects preferences folder." I have checked them OVER and OVER. What is going on?

When I updated to the latest update to After Effects Beta, I opened the project, but this thing appears to me, and when I click on OK, the program exits

Interpret Footage --> Main --> Seperate Fields --> "Upper Field First" and "Lower Filed First" shows identical field.This also appears in non beta versions.  

when i  try to paint strokes with rotobrush it doesnt work, it just leaves a purple outline around the video and says "after effects warning: roto brush strokes cannot be added until the current frame has finished rendering

Hello, I made a very simple video using Mercury 3D , but when I render it using After Effects itself, it says an error with code 1, and when I use Media Encoder (beta), the video is rendered like this, what is the solution? I even deleted the plugins that I put in the video, but it also gave me the same result

Hello! I inserted an Adjustment Layer with Tint to change the color of the iMac (3d object). When using this adjustment, the 3d depth field is lost, and the layer hierarchy is assumed. Look at the attached prints. 

Updated to 23.4 yesterday.  After several uninstall -reinstalls these past 2 days, had to revert back to 23.3 as program wouldn't launch in 24.4 and kept notifying me upon launch that the beta program file was corrupted. 

AE beta v23.4.028Windows 10 22H2 19045.2728 DWAA/DWAB EXR, 2 puzzlematte layers rendered via Redshift in C4D 2023.1. Expected result: applying eXtractor should allow me to view the puzzlemattes as single colour layers. Actual behaviour: eXtractor does nothing when applied to EXR layers. Vanilla AE playback is fine.  

I've just sent 3 items to render, and got this weird message about the name of the output module. Whaaaat?? Who cares if the output module's name is already in use - I'm not changing the output module settings - I just selected one of the presets (H.264 - Match Render Settings - 40 Mbps...but it doesn't matter which one I choose...it could be ProRes444....anything), hit Render, and got the error. Exporting things one at a time fixes the problem.I'm on AE Beta 23.4.0x28, Windows 10 Oh yes - and I still often get the "The directory originally specified in the selected output module no longer exists." error, so I have to click on the output filename to choose the exact file location that AE has already set.  

Is it possible to focus the lumteri scopes to just a selected area of the frame?Ie. I just want to see the scopes for an actor's face - I don't want the rest of the scene visible in the scopes.If there is no such feature - can we make Lumetric Scopes work with Region of Interest?It's the first thing I tried, I was surprised it didn't work. I think selecting a part of the frame with RoI should be reflected in the scopes.

Hey, the new AE beta introduced a progress bar that is displayed while a script is being executed. Now I get why this might be useful in certain circumstances. However, I have my own progress bars included within my scripts and it's kind of annoying to suddenly have two progress bars popping up at the same time, especially since AE's progress bar does not display specific information regarding the progress in question compared to the custom progress bars within my scripts. I looked into the user preferences, however, there was no option to turn off the progress bar as there is for example for the warning message when executing files. Now, maybe there is an option to do that already that I'm not aware of. If it doesn't exist, would be possible to add a checkbox like this in the preferences for (de)activating the progress bar?  Best wishes,Constantin