After Effects (Beta)

Today I got an AE message that I’ve never seen before. Is this related to the “Collapse Transformations” switch? What exactly does it mean and do? thank you.

Steps to reproduce:    1. Try and rotobrush any footage Result: Immediate crashWorkaround: Click once on the footage in the layer panel with the Rotobrush tool. Press Caps Lock. Switch from Version 2.0 to version 1.0 in the Rotobrush Effects Control Panel. Release Caps Lock. Continue with Rotobrush and everything works fine. System info    Application: After Effects (Beta) v22.1.0.36    OS: macOS v11.6.0, RAM: 8.00 GB GB, CPUs (logical): 8

shapes in preview

Being a GFX artist my compositions usually take hours to render, so definitely excited about the multi-frame rendering, however I gave it a test drive today and the Beta version only rendered a few seconds faster than the single frame rendering, hoping when they launch it, it will be faster than it currently is. One amazing thing is being able to get notifications once your queue is finished! BIG UPS ON THAT!! No more constantly going back to the computer to check your queue, one question on my mind is, will it let you now if the queue fails to render?

Cant change quality and zoom options in after effects beta for m1 mac

In the latest Beta when you convert a parametric shape into a bezier path it will create a copy of the path but also keep the parametric path and you can't delete it because it will remove both paths. Hope this make sense 

Steps to reproduce:When having a basic shapelayer and adding a modifier, like a repeater, a new stroke etc. and trying to modify any of it's properties, I get this alert and I am not able to do changes:After Effects (Beta) error: internal verification failure, sorry! {asked for invalid component of property path} System info    Application: After Effects (Beta) v22.1.0.6    OS: Windows v10.0.19043, RAM: 63,95 GB GB, CPUs (logical): 24 

The paths of the effect points in the layer window no longer show the keyframes. You can see the paths but not the little squares of the keyframes with their tangents.1-double-click on a solid to open its layer window2-Add an effect with a position point (e.g Write-on)3-create animation keyframes for the position result: no keyframes path(It's not related to the beta, it's the same thing on 18.2.0.) 

Keyframing with added properties (e.g. trim paths, repeater,...) leads to this window: "After Effects (beta) error: internal verification failure, sorry! {asked for invalid component of property path}. After hitting a few times the ESC-button I can continiue, but have to erase the property to not have a black screen.

Am I missing something in the settings to enable OpenType font support? I remember seeing IN DEVELOPMENT tag a couple of weeks ago, and assumed it was implemented already, since that tag is not there anymore. I'm really looking forward to for this feature. Just love to use different alternate styles, and it adds value to my work.

Testing out the latest AE Beta v22.1.0.3 on Windows and found that any export of ProRes 4444 (including XQ) has a color shift and small additional amount of grain. I've tried CUDA vs. Software Only, 32 vs 16 bpc project, Millions vs Trillions of Colors, MFR vs No MFR - all exhibit the same issue. Note: AE 2021 on the same system renders the ProRes 4444 correctly. To test the actual shift, I created a 50% gray solid composition in 32bit and rendered it out in multiple different formats:ProRes 422, ProRes 4444, ProRes 4444 XQ, (and Tiff Sequence as a control) When re-importing the renders, the 4444 and 4444 XQ renders exhibit the shift, as seen in the RGB values, for example:Original grey solid:ProRes 4444 Render:Here's the ProRes 4444 on top of the original 50% gray with a Difference blending mode (comp viewer exposure is bumped up about +12). Played back, the grain pattern moves uniformly across the screen. I've included all of the renders of the 50% gray and a vide

I've just been trying out multi-frame rendering with a small sequence that has a single instance of Keylight 1.2 on some video footage.I initially tried it just RAM previewing and found that the time to render was the same for single and multi-frame rendering. I could see that multi-frame was working and CPU utilisation was much more. Info said that at some points, 8 frames were rendering, So then I tried a proper output from the AE render queue. I tried both single and multi-frame. The single took 31s and then the multi-frame took 54s! I had purged memory and disk cache between each attempt. I was saving as ProRes 422 in Qucktime wrapper. Specs - Windows 10 Pro 10.0.19043Intel i7-7700K 4.2GHz 4 coreASUS Maximus IX hero64GB RAMNVME system and data drivesAE 22.1.0 (build 1) Happy to share project comps if needed. Paul.

Hey Y'allCan't export motion graphic template from AE Beta (22.1.0)The export UI pop's up, but I get and error message saying: After Effects (Beta) warning: Unable to load operating system font "Adobe Clean UX""Bold" I ok to dismiss the error message. It pop's up persistantly.I hold down esc. It flashes dismissing hundreds of times. Eventually the esc works and quits the export dialog.There is no crash, just go back to main UI, but can't get to through the export diaglog. Keep up the good work! Peace. Windows 10, AMD Ryzen 9 Mobile - 8 Cores16GB DDR4RTX3070m 

On windows 10 with latest AE beta, when I try to go to preferences I'm met with a dialog box with, "After Effects (Beta) warning: Unable to load operating system font "Adobe Clean Ux" "Bold". Can only get out if I press down on escape for a few seconds, where dialogbox repeats itself a few times. 

Noticed something strange.  When you enable continous raster (collapse transformation) on a precomp it ignores the layer's blending mode and uses whatever blending modes are enabled on the layers within that precomp. This pass through behavior I understand and I think has been around for awhile.  When you use a track matte with that layer however it ignores those internal layer blending modes and then goes back to whatever you had set it to in the master comp. (see example below) Its just weird and inconsistent. I went back to the non-beta version at the same behavior exists that version as well.  Example: Precomp with simple circle has no internal blending mode / continous raster off / blend mode set to differnece in main comp.  Continious raster switched to on. Blending mode ignored as shown by the (-) in the blending mode drop down. Track matte enabled for layer, continous raster switched on, now using differnece mode again even

I have a Pr Project with 3 Ae parts in it. If a modification needs Ae for prewiev every thing is fine but when I close Pr, Ae crashed. I am unable to send (or not send) the crash report. I have to force Ae to stop in task manager. I joined the Ae messagePr (beta) 22.1.0 (build5)Ae (beta) 22.1.0 (build 2)Windows 10 proCPU I9 9900KMemory 64GoVideo RTX 2080 TiThanks for the help 

During export AME stoped (no error message, just stoped !!) .Since there is no link any more beetwen AE and AME.No dynamic link, No export, AME start and nothing more !!AE beta 22.0.0 build 56AME beta 22.0 build 42Thanks for the help 

I get "Warning: Invalid menu operation" when trying to access anything. I can't click on or access any of the the menue times (File, Edit, Compisition, Layer etc). So I currently can't do anything in the project I have open besides scroll the timeline.

When working on lengthy comps it gets really tedious having to trim layers into specific areas, any chance we could see some way of being able to create layers only inside of the specified work area?Maybe somewhere in the layers panel have a 'work area focus' icon?Cheers

Found a small UI bug. If a layer is a guide layer, is 3D, and is visible, the 3D switch’s icon goes away. If the layer is not visible OR is not a guide layer, the icon correctly returns. In my screen shot, you can see layer 2 is missing the 3D switch icon, but still has 3D properties (Z position, orientation, Z rotation). All 3 layers are duplicates, otherwise identical besides guide/layer visibility. System info    Application: After Effects (Beta) v22.0.0.100    OS: macOS v10.15.7, RAM: 64.00 GB GB, CPUs (logical): 16

I updated to the 9/15 update yesterday and saw that DUIK Bassel no longer work. I still have access to that script in 18.4.1 but I didn't expect that to happen. Any reason why this build did that?

When opening a composition with an .exr image sequence, after effects immediately begings loading the composition to the ram preview. (without pressing play) You can see the green ram preview growing, and there's no way to stop this. This then maxes out completely (my system has 64gb of ram) and does not clear itself.  The same issue occurs with using media encoder to render the composition, as the render progresses, the ram is slowly used up until the headless after effects.exe crashes, leaving media encoder frozen midway through the render. You have to force close the application then. On some renders it will make it all the way through without crashing.  

Amazing!

Steps to reproduce:    1. Create a solid, add Lens flare, open Layer Panel, set a keyframe for Flare Center, move down the timeline, set another keyframe, make sure Lens Flare is selected to render. Result: In previous versions of After Effects you get a nice bezier path that can be edited with the pen tool. In the latest two versions of AE (beta and release) you get a dot for every frame, no path points, no bezier handles.Expected: You should be able to see the motion path. This does not work for any effect that has the option to create a motion path like Lens Flare, CC Radial Blur, or Anchor Point path. The display is 100% broken.   The strange thing is that you can enable the pen tool, roll over the path and have the pen tool change to add point, then click and drag to curve the motion path. Everything works except the ability to see a motion path. System info    Application: After Effects (Beta) v22.0.0.81 / After Effects 18.4.1&nb

For some reason, when i try to begin playing the preview, it takes a few seconds before it starts playing, after which it plays fine. It seems to have something to do with the size of the project. I have a lot of stuff in it, however I am in an almost empty precomp (all it has is music), so there is no reason this should be happening.I tried restarting after effects, my pc, playing it on another project (where it works without problems) and removing everything from the comp, deleting disk cache, ect. Any suggestions on how to fix it?