After Effects (Beta)

With the release of the Beta v23.x there is the ability to pickwhip track mattes now (which is awesome)However, when I copy pasted a selection of layers into a new comp with all sorts of track mattes, all of the layers came over in the correct order and were parented correctly (as expected), however nothing was linked anymore with track mattes.What's weird is when re-linking the track mattes, it did retain if it was an alpha or luma matte and if it was inverted or not.. so some of the information is retained while the physical link is broken.

Hi, i am using the beta specifically for a project taking advantage of the new Track Matte feature as i have a ton of layers.Unfortunately, i just tried to parent 4-5 layers Track Matte to another layer with the pick whip for the track mattes but it only link the first selected layer. as opposed to normal parenting, which lets you parent all selected layers in one drag of the pick whip. This is a must as after pick whipping all my layers one by one, i realized i track matted it to the wrong layer, and had to do them all again, one - by - one.This would be a nice fix to have soon, Thanks! 🙂

It's a tiny thing, but I pretty much laid it out in my Subject line.   Amazing work.  I LOVE IT  Keep up the amazing work.  Thank you.

Ctrl + Alt + Home is not working for the Center Anchor Point in Layer Content.I've tried changing out the shortcut to different keybinds but nothing seems to be working besides manually eyeballing it. Shapes seem to be the only thing that work with the shortcut but when it comes to masks, it no longer works. I've tested on solids, adjustment layers, footage, as well as nested compositions.

There is a bug happening on shutdown in AE 23.0 beta builds that might cause AE to crash on startup the next time you run AE. If that happens, please delete your beta preferences. You can do that by:   Windows: Navigate to C:\Users\{username}\AppData\Roaming\Adobe\After Effects (Beta) and deleting the 23.0 folder.  MacOS: Navigate to \Users\{username}\Library\Preferences\Adobe\After Effects (Beta) and deleting the 23.0 folder.    The preferences will be recreated on the next start up of After Effects. Please post back if you continue to have issues with AE startup after performing these steps.  

Version: 23.0.0 (Build 11) This happens

Any idea what these are meant to do?  Also, when you initially open the dialog, the first control you click makes the Quality/Resolution/Frame Rate controls re-arrange themselves into a different order (Framerate moves to the top)

In the "Based on" dropdown, I cant select the option word. I made a GIF for better undestanding

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

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) 

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

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

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 

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

During rendering animation a lot of high is missingrecording is ok, sound in AE also?

I have no idea what happened between the last and current beta, but this is unusable. Every move I make caused the screen to drop to black. I will see the screen in the preview window, but when I move the mouse or try to make changes everything in the preview goes black. WTF. Macbook Pro M1 Max fully maxed out on Monterey 12.2.1.

Anytime I try to apply a previously made text animation preset or one built in from Bridge, it gives an error: "After Effects (Beta) error: Can't import file "Text-Fade in-out.ffx": unsupported filetype or extension. ( 0:: 1) This is a deal breaker for me, I absolutely need these presets for my main client. I had just started trying beta as the current version is nearly impossible to use with shape layers causing a pinwheel every time I touch anything. Please fix ASAP.MacBook Pro (16-inch, 2021) M1 Max 64GB Ram