After Effects (Beta)

I'm doing very basic renders between Cinema 4D and AE. C4D lets me choose between rendering an OpenEXR file, or rendering the OpenEXR file with an accompanying aec. file that After Effects should be able to read. I'm doing a basic render (a sphere on a plane with a light) and rendering out the EXR file and the accompanying aec file. When I open After Effects - current Beta version 22.4.0, Build 41 - it can import the EXR file but the aec file is greyed out and unselectable. There's a C4Dimporter plug-in that comes with C4D and I've placed this (if it's needed) in my AE plug-ins folder. If it's meant to help the process it doesn't seem to be doing so. If this is a limitation of the current Beta, I can certainly wait, as I'm sure things will be fixed in the coming months, but I'd welcome some guidance as to whether I'm doing something wrong, if Maxon needs to fix things at their end for the Apple Silicon version of AE, or this is something that the Beta version will be able to

Steps to reproduce:    1. Create Project in Ae Beta    2. Save Project    3. Open Project in Ae 21 or 22 Result: Project wont open error  and 33 : 5(In my original project I get the above error in addition to 26 : 00)  (screenshots attached)Expected: It should open without issueSystem info    Application: After Effects (Beta) v22.4.0.32    OS: macOS v12.3.1, RAM: 32.00 GB GB, CPUs (logical): 8 This was happening on my other computer (PC), and for my client as well. I think this is a recent issue and I have previously been able to open projects in previous versions of Ae when using Beta, if I recall correctly.I have tried every method of exporting and importing that I can think of, and I haven't got anything to work. I originally thought that it was a problem with some footage I was using, but it is now happening for me with a fresh project (new project with an empty comp, attached).

Hi,  I've discovered that if I create an AE Beta document on my M1 Mac and then try to export the project for another user either on Mac or PC.... and even on M1 Mac using standard AE,  The project files is unreadable - "Chunk in File too Big"  Tried saving as AE XML still no go.  Anyone know a workaround to get the AE Beta file usable by anyone not using Beta?  Thanks.

When rendering, you can click the Info button to pop up a tiny panel with information about the current render: how long each frame is taking, how many frames are rendering concurrently. If you are using multiple monitors, the Info button only works on whichever monitor is considered the "main" monitor by your Mac (according to Sys Prefs > Displays).  To reproduce:Ensure you have more than one monitor plugged into your computerSet a render going in AE, and click the Info button.Cancel the render or let it finish.Move AE to another monitor.Set a render going, and click the Info button. Problem:The Info button will only work correctly on one of the monitors. System info    Application: After Effects (Beta) v22.4.0.28    OS: macOS v12.3.0, RAM: 64.00 GB GB, CPUs (logical): 10

Hello! Today I'd like to direct your attention to a bug fix that is available in After Effects Beta, v22.4:When you use Microsoft Remote Desktop to log in to a Windows computer, the "Hardware Accelerate Composition, Layer, and Footage" panels option in Preferences > Display is no longer automatically disabled. We know that there are a few folks out there who use Remote Desktop to access the machines where they use in After Effects, or are using virtual machines. In fact, some of our developers are among them! This bug fix addresses the problem where the Hardware Accelerate preference was automatically disabled when you launch After Effects for the first time when using Remote Desktop. It was possible, after you launch AE, to enable this preference and continue working, but once you log out and log into Remote Desktop the preference could automatically disable itself again. A few features in After Effects are dependent on this preference being enabled, like the Dr

With the release of the Mac Studio, I'm very curious what the performance differences between the two chips are. Let's just say at their base configurations for the sake of argument, how much of a difference will the Ultra make to performance? From what I know of AE performance, CPU is still very important, so I would think that it would be a big deal, but I've yet to see a single YouTube video that focuses on AE with the new systems. I know Stu Maschwitz put out the article on release day, but it wasn't so much a comparison between the two or how big of a difference it would make. I'm very much trying to inform my purchase currently. I do have an ultra on order, but if the difference is minimal, it may not be worth it. I'd love to hear more for anyone who knows!

Hi,I've recently been working on a project I started on my PC. I have moved to a mac air m1 16gb for portability . The project I'm working on gives the need more than 2 frames error in Beta. I have tried emptying the cache etc. It still won'r play back. I have treid the same project on AE runnning through rosetta and as long as I don't run anythiung else includind media encoder it works great. Rendering is fast and changes update quickly. I realise that the M1 16gb is on the edge of the RAM threshold but how come the native M1 version doesn't work at all and going through rosetta works fine?

Steps to reproduce:1. In Photoshop, create a puppet with art layers against transparancy2. Rig the puppet in Character Animator. Do not add a background3. Load the resulting puppet.chproj into an older version of AE. 22.1 for example.4. Add the puppet.chproj to a comp and add a background. Looks great!5. Open the AE created above in After Effects (Beta) v22.4.0.17Result: The alpha of the puppet.chproj has a black borderExpected: No black border. Not sure which app is changing how the alpha is handled, but this is new and unexpected... Workaround: interpret the puppet.chproj footage with premultiplied instead of straight alpha.  System info    Application: After Effects (Beta) v22.4.0.17    OS: macOS v12.2.1, RAM: 64.00 GB GB, CPUs (logical): 10

HelloWould I notice any difference in speed using the current AE released and beta version on an M1 mac?The reason I ask is: I was originally using PP & AE beta, because PP beta supported Apple Silicon. Now Premier has officially been released to support Apple Silicon and I'm wondering if I should continue using AE beta or the latest official release until an Apple Silicon AE is released. I'm mainly looking at the speed in its workflow, like 3d tracking, adding titles etc. CheersJamie

In AE 22.4 Beta updates since March 17th on my Mac M1 Macbook Pro Max, I can't pull down menus any more.  When I click a second time, the dropdown flashes on/open for half of a second and sometimes I can quickly click on something with the mouse button held down but they are not working correctly.I was lucky after a few attempts to even be able to click on the Beta Feedback button's pulldown menu 

Greetings!   We’d like to introduce you to two new features in After Effects Beta, available today in version 18.0.0.20 and later: Redesigned Composition Panel Toolbar: The row of buttons at the bottom of the Composition panel has been streamlined and re-organized to show only the most used features. 3D options are now contextual and won’t get in your way when you don’t have 3D layers in your comp. Settings that are no longer accessible via the toolbar, such as pixel aspect ratio correction, can still be controlled via the Composition window menu. 3D Ground Plane button: When Draft 3D is enabled, a new button in the toolbar at the bottom of the Composition panel allows you enable or disable a ground plane in the comp’s 3D space.   What We Want to Know We want your feedback on these features. Primarily: Does the redesigned Composition panel toolbar improve your workflow? What would you change? How does the 3D ground plane feel? Is it helpful when working in 3D comps? &nbsp

I'm trying out the new Properties Panel. Every time I select the stopwatch to set a keyframe on any of my object's attributes, I get an error message "Unknown Exception". 

I'm just curious 

Chaque clic sur le Chronomètre affiche un message d'erreur 'Unknown Exception' (version anglaise). Les KF sont bien valides et efficientes dans la timeline, les paramètres sont modifiables dans la fenêtre Propriétés, mais impossible d'activer le chrono.

Currently, clicking this icon in the Properties panel does not unlink the X and Y size values (neither the icon or the behaviour change).  

While rendering with Multi-Frame rendering on imac pro 2017, after effects crashes without saving. This happens pretty much all the time. I like the speed but I always have to keep an eye out in case after effects crashes without me knowing. Specs:2.3 GHz 18-Core Intel Xeon WMemory 128 GB 2666 MHz DDR4Graphics: Radeon Pro Vega 64X 16 GB

Pretty simple, as the title emplies. In the properties panel the link chain is blue and can't be clicked and unlinked. sometimes it does nothing sometimes an error pops up. Hoping this is an easy fix.. Good Luck 🙂

Lagging Interface in AE Beta 22.3.0 Build 62Getting stuttering / lagging from the interface itself when trying to scrub through my comps. (not an issue in other versions) As opposed to delayed previews, the actual current time indicator, and really any interface action is just lagging every few moments. I even tried an empty comp, literally nothing in it, same problem. Click on the timeline, wait a moment, app catches up. Scrubs ok for a second, then hangs up. Setting and out point, adding a shape layer, all basic functions seem to be included in the list of laggable offenses.

It wont allow me to Freeze Frame a RotoBrushed 2.0 Layer

Beta doesn't RAM preview. On the initial launch, it will preview once. After that, any changes made will not play or return an error. Purging all cache and memory won't solve this, only re-launching, and the problem repeats itself. 1TB scratch available + 48 GB RAM allocated to CC.

Thanks for adding the ability to add 1:1 shapes while holding shift.Unfortunately the behaviour seems to be more buggy in the latest beta.  After opening a new, empty comp, double clicking the rectangle tool (without holding shift) creates a shape layer with a rectangle. If I Ctrl+Z Immediately afterwards and try to create another one, the functionality breaks and no shape layer is being added.Highlighting another panel (like the viewer or the timeline) then trying again fixes the issue.This happens to me on a PC. Thank you.  

Scrolling the properties panel is significantly slower than scrolling anywhere else.The scrollbar size also seems to be different.I also find text in this panel to render slightly differently than in any other panel.People also mentioned how using it to set values is slower than in the timeline (feels stuttery) and mentioned how a dual screen setup can cause this, which I am using.I am not sure what's going on behind the scenes but just to let you know, it shows that this panel does not feel well integrated, but the biggest issue is how values are slower to update. Thank you for the hard work. 🙂

Steps to reproduce:  1.Open a new comp2. From anywhere under the timeline ruler start a selection and drag the mouse upwards. 

I'm trying to follow a tutorial from linkedin learning for drawing a circle in After Effects. I am on M1 mac running the 2022 intel version for this software. How in the world do a draw a cirle? In the tutorial they show a button in the composition window after using the ellipse tool to select "Toggle Pixel Aspect Ratio Correction" to change the ellipse to a perfect circle. Help? I don't see that icon and can't find it in any menus offhand.  

Steps to reproduce:    1. Render to 1080p Avid DnxHD LB-8bit.     2. Do the same render in AE v22.1.1 or previous AE beta v22.3.0.2#Result: The rendered movie doesn't open in Quicktime Player or Avid Media Composer. File icon is not correct, it's a generic Mov icon without the thumbnail. Compare with the same comp rendered with AE v22.1.1 (see the screenshot). System info    Application: After Effects (Beta) v22.3.0.39    OS: macOS v12.1.0, RAM: 64,00 GB GB, CPUs (logical): 10