After Effects (Beta)

Greetings! After Effects is a BIG application. Here on the After Effects development team, we know that when we introduce a new feature it can sometimes become lost, like trying to find a newly sprouted tree in the forest. We do our best to announce new features via Adobe.com and our social media accounts, but the best way would be for After Effects itself to tell you what's new and changed. Starting today in After Effects Beta, version 22.3 build 72, you will see new notifications when you click on certain parts of the UI. We call these coach marks, as they can help point you towards new features, introduce you to changed functionality, or even help you improve your workflow.  Right now in After Effects Beta, you'll see just a few coach marks sprinkled around After Effects that point you towards some of the newer changes to rendering performance and 3D workflows. What we'd like to know from you is:Do you like having these little pop-ups tell you about what's n

This happened to me when I imported an mp4 file (don't know the codec exactly, but it's a very compressed one for sure) When I set the blending mode to Add it got a couple of glitches where it jumps to another frame for a couple of frames. I applied time remapping and it fixed the issue. here's a video demonstrating the glitch

As announced back in May, we’ve added Keyframe Color Labels to After Effects. Right-click on any keyframe(s), select ‘Label’, and choose the color you want assigned. Choose ‘Edit Label Colors…’ at the bottom of the Label list if you want to change those default colors. Use ‘Select Keyframe Label Group’, to have that color label be the basis for a selection (also available via scripting hooks).   From the feedback we have gotten so far, we’ve been adding updates and fixes along the way. Now we want to know from you, our beta members, whether you think Keyframe Color Labels are ready for primetime.   In your AE Beta build, click on the flask with the blue dot in the upper right:   In the What’s New in Beta panel that comes up, select ‘Rate features’ on the left. This gives you an option to say whether you think Keyframe Color Labels are either ‘Not ready yet’, or ‘Ready for release’. There is also space to leave any comments you may want to add:   As always, thank

Hi everyone,I'm going crazy about this and I hope someone could help me.As in the title,  I'm using a Macbook pro 16 gb M1 and my after effects is letteraly unusable. Now I'm on a project that uses Animation Composer preset and I can't see the preview at all. I tryed to open the same project on another Macbook pro (2019) and everything goes easy. I comparated the render, memory, cache storage, preview settings, on both computers and everything seems to me ok and the same, but I can't see if there's someting I'm missimg or what. I only notinced that in my new computer when I press the spacebar for preview the cache blue/green bar becames uncolored, and restart the green from the start point. Then green go slow slow slow and stop. I'm not super expert on setting, so something maybe make no sense, but perhaps it could be helpful to understand what's wrong.I have also read that many people are having issues with the native Mac M1, so at least I would like to understand if it

Like the new feature you added with moving between keyframes only on selected layers. I noticed a slight bug that it only works if you are on the AE default keyboard shortcuts and disappears if you have custom ones. I have some pics to show what I mean. Any idea around this?

I am a multibyte language(Japanese) user and change the language settings to English by using ae_force_english.txt.In the latest version, a dialog appears at start-up and AE doesn't launch.(Windows 10, version 22.6x9) 

Good afternoon!   As of After Effects 22.6 Beta (build 11), we have fixed a situation where starting a preview could cause After Effects to purge previously rendered and cached frames in front of the CTI, creating a need to re-render them during playback. The issue presented as slow playback even though green cache markings were present as the green cache markings do not update fast enough to reveal the purging. This would have been most noticeable in cases where memory usage was maxed out.   You should see improved Preview performance with less re-rendering during playback as After Effects should now purge the frames least likely to be played during that Preview if necessary. If you do see re-rendering of frames about to be played during Preview, either via the info panel or disappearing cache markings bar in front of your CTI, please reach out to us with your system specs and any project you see this behavior in.

The good news is that After Effects Beta 22.3 no longer crashes when using Apple SF Pro version 17.1d1e1. This font is available from Apple here https://developer.apple.com/fonts/ The repro was simple - select some text in a Text Layer, apply any SF Pro Regular font style, other than Regular itself,  boom. The reason for this, though there really is no good reason for After Effects to crash, is that there is a problem with the construction of the particular font version which confused our code and in that confusion it did something bad and triggered the crash. That vulnerability in our code has now been fixed, but an underlying problem with the font remains and that is the bad news that I will cover next. The issue our code has with the font is that we are unable at times to properly distinguish between the Regular instance of the front from the Italics instance of the font. This only happens, so far as we have seen, when applying a Regular font style othe

As the title mentions - if the properties pannel is active (even while being collapsed) - moving a shapre is extremely slow.Is there any temp fix for that?

When AE performs an auto-save, no matter what window is in foreground gets replace with AE, I mean when browsing the web for example and AE is running in the BG it automatically switches to the foreground when and auto-save occurs, this is slightly more annoying since I have to decrease the auto-save time interval because unexpected crashes of Betas. I wish I could provide more info.

H/ware: MacBook Pro / M1Max / using internal laptop screen (doesn't seem to matter which colour preset is active) or internal + external screensOS: macOS 12.3.1AE: shiny fresh install of the latest AE (22.5.0.35), default prefs, no 3rd party plugins Steps to reproduce:New ProjectNew CompProject Settings > Color: set depth to 32 bit; set Working Space to sRGBClick the viewer or timeline to make sure the comp has focusView > Simulate Output > Rec.709 (or any of them for that matter) This hangs (beachball or watch) or crashes AE here; you may need to Force Quit it (Cmd-Opt-Esc). If anyone can confirm this happens (or not) on their machine that'd help me figure a way forward. Could be M1 based, or it could be something display related, but I've no way to narrow it down. Thanks : )

Steps to reproduce:1. Import an .mp4 Result: No video is being shownExpected: Video to be displayed System info    Application: After Effects (Beta) v22.5.0.32    OS: macOS v12.3.1, RAM: 64.00 GB GB, CPUs (logical): 10 Quicktime info

This is a bit nuts so if anyone has a second to either confirm it's a bug or point out my idiocy it'd be much appreciated; there's a minimal project file attached. I tend to work with a linearised sRGB working space, and when rendering to an sRGB output file, AE correctly applies gamma correction to de-linearise the image. Except it's not doing it on my M1 machine; it outputs a linear space file. The same project opened on Intel vs ARM64 machines show the problem: To reproduce:open the attached project. It contains an empty comp and a single render item.look at the File > Project Settings... > Color dialog. It should show the project is using a linearised sRGB working space:  go to the Render Queue, click on the Output Module (ProRes), and go to the Color Management tab. On my Intel Mac Pro, I see this: Note the middle paragraph - though I'm outputting to the same colour space as the project, AE knows it has to apply gamma. On my M1 MacBook Pro, I see thi

Steps to reproduce:    1. Quit After EffectsResult: After Effects (Beta) error: crash occurred while invoking plug-in "Scripting".Expected: Quit System info    Application: After Effects (Beta) v22.5.0.29    OS: macOS v12.3.1, RAM: 64.00 GB GB, CPUs (logical): 10

There is isssue whene I copy autosave aep from its folder and return to main folder to paste it AE crashes this isssu in version AE 2022 and 2022.4.0

I continuously get "Cached Preview needs 2 or more frames to playback in AE Beta 22.4.0 (Build 10)" when I add a new layer or adjust a layer in my setup. Simple 3D camera setup with a slow camera push in z-space. 5 layers in total, no effects. Continuous rasterization thru to a live text layer with no effects. Background/base layer is built off a quicktime MPEG-4 movie - 2.3 MB. If I restart AE beta, it works fine for a little while until it pops up again. Roughly 80% CPU idle. Hardware Overview:   Model Name: MacBook Pro  Model Identifier: MacBookPro18,2  Chip: Apple M1 Max  Total Number of Cores: 10 (8 performance and 2 efficiency)  Memory: 64 GB  System Firmware Version: 7429.61.2  OS Loader Version: 7429.61.2

As promised, we have some new functionality being added to the Keyframe Color Labels feature today in After Effects Beta, 22.5 build 25.   Select Keyframe Label Groups  More options are now available to give you more control when you want to select all the keyframes that have been labeled by a specific color. Right-click on a keyframe and notice the new ‘Select Keyframe Label Groups’ option. You can now choose your selection to include keyframes of the same label group: On Selected Layers On All Layers Visible Keyframes on Selected Layers Visible Keyframes on All Layers  Visible keyframes means that the property for that layer has been twirled open in the Timeline panel. It does not relate to the zoom or scroll of the Timeline panel.  For the first two options, keyframes that aren’t visible will be selected and their properties will be twirled open.  KNOWN ISSUE: These commands do not work if more than one

When quitting the AE Beta app it hangs the app and I need to restart the computer.

Steps to reproduce:Put 'Properties' panel in a stacked panel group, and select a different panel in the group (so that Properties is contracted, or 'closed').Select a shape layer.Click on the Properties panel to expand it (make it active). Result: The Properties panel doesn't show any information or properties – the Panel title reads "Properties: No Selection". If you click on the shape layer with the Properties panel expanded, it then populates. Alternatively, if you expand and contract the Properties panel a couple of times, it populates.Expected: Properties panel should populate with information on the selected layer even if the panel is contracted. System info:Application: After Effects (Beta) v22.5.0.14OS: macOS v12.1.0, RAM: 64.00 GB GB, CPUs (logical): 10

Steps to reproduce:1. create a new comp (command+n)2. create a solid (command+y)3. undo/redo 2xResult: Solid takes .5, 1, then more than 15 seconds to appear in the new comp. System info    Application: After Effects (Beta) v22.4.0.32    OS: macOS v12.2.1, RAM: 64.00 GB GB, CPUs (logical): 10 Here's a video. You can jump about halfway through to see the 15 second delay. I wiggle the cursor around while waiting more than 15 seconds for the solid to show up. Solid Creation Delay  Anyone else getting this? Please let me know if there is any way I can help. Also check my profile for other AE Beta bug reports. Thanks! Benjamin

Hi all!I'm always on the newest Beta, but never can start it. I sendet die report, no response.I deinstalled it, but it does not matter. alwys that Debut Event, then the Bug report window 

When I render DNxHD in any Apple Silicon version of After Effects (Beta 22.5 and the current release v22.3), the file is unreadable when imported in to Avid. Avid can read DNxHD files redered out of 22.2.1 using the exact same output module no problem.

Hello everyone! I'm back to announce a new feature, available today in After Effects Beta 22.4x1!   Separated Dimensions Preference:  You can now set AE to default to separated X, Y dimensions (for 2D layers) or separated X, Y, Z dimensions (for 3D layers) on position properties by enabling the new Separated Dimensions options in Preferences > General.     What We Want to KnowDoes this feature improve your workflow? What would you change?   Thank you! We’re looking forward to your feedback

Text Animation of Character Offset with Range Type Preserve Case & Digits has been enhanced in After Effects Beta 22.5 (19) to include the Hebrew character set. You can read more about this particular character set here: https://www.unicode.org/charts/PDF/U0590.pdf  Just to review, the Range Type Preserve Case & Digits defines a set of Unicode range groups whereby when After Effects adds a positive or negative offset to the base character it is animating the resulting Unicode character is wrapped around so it stays within the same Unicode range group as the base character.  For example, consider the upper case Latin letter "Z" which is part of a Unicode range group for upper case Latin letters that spans from "A" to "Z". When we add one with the Character Offset we generate an upper case Latin "A" instead of getting the next Unicode character after "Z" which is the Left Square Bracket "[". Neat, eh? With Character Offset Range Type Full Unicode the

Been struggling with a strange issue lately but I've narrowed things down, so I here's what I've found in case it helps others with the same problem. I don't think AE is the cause, but since AE is where you're likely to experience the problem, I wanted to document it somewhere. Symptom: a project containing certain ProRes assets renders fine on Intel Macs, loads and displays correctly on ARM macs but when you try to render them, AE hangs at the start of the render. The cause seems to be some ProRes files that have been created using ffmpeg. Not all files created with ffmpeg exhibit the problem. The ProRes files in question may not cause problems in any other software packages, but something about the way ffmpeg compresses them can cause issues with the M1 chips' hardware decoding, I'm guessing. We've been using ffmpeg to compress image sequences into ProRes files for years now without any problems, so this has been tricky to track down; it really does only seem to affect AE o