Bug Reports

MAC Studio, M1, Ventura 13.0.1, 64 GB My experience with After Effectssince upgrading to the Mac Studio has been horrendous. For several months I was unable to work because of the 5 frame playback glitch, countless bugs and memory errors. I was so relieved with the last update, playback seemed to be working just fine. That was until I updated the Mac OS to Ventura. I am doing some greenscreen work and had to download some mp4s for backdrops, the first and most noticable issue is that the backgrounds are seemingly jumping to random frames, constantly lagging and cutting to black. I assumed this was a codec issue with the mp4s so I converted them to MOVs. No luck, playback is just as bad and choppy. On top of the playback speed is seemlingly a fraction of what it used to be, Making it incredibly difficult to get any work done. 

I updated all my Adobe apps as I was between projects, then got a request from my client to update a project created a few months ago. After downloading the collected project from Dropbox I tried opening it in the latest 23.0.0 build of After Effects. Every single embedded .MOV file gave an error "this MooV file is damaged or unsupported." I rebooted, etc and nothing worked, having to repeatedly click OK for the dozens of footage files over and over. Tried reimporting but the same error. Strangely the same project will open fine in both the 2022 build as well as the latest Beta (23.2.0 Build 9) with no error messages for the footage. I know there are ongoing issues with Dropbox and M1 Macs, but I'm wondering why this seems to be specific to 23.0.0? MacBook Pro 16  Model Identifier: MacBookPro18,2  Chip: Apple M1 Max  Total Number of Cores: 10  Memory: 64 GB

Mocha Pro (2022.5) will no longer launch through After Effects (23.0.0) on my Mac Pro (OS X Ventura 13.0.1), it just hangs on the "Mocha Pro is starting..." screen and the app icon bounces in the app doc for about 2 minutes before stopping and staying frozen. I have tried restarting the computer multiple times, and I have uninstalled and reinstalled both After Effects and Mocha Pro, to no avail.

Been having this issue on and off for a while. Hit spacebar for ram preview, preview is shown in composition window, but playhead (blue arrow and line) stays still on timeline. It should advance and turn red, plus when I hit spacebar to stop it should stop at that point. This issue appears to happen randomly, often with projects with lots of comps, but not on overly complicated ones. The only way to get rid of it is to close AE and reoppen, then it works fine for a bit, but then the issue comes back. Also seems more common in dynamicly linked to Premiere comps (maybe)? I've tried a bunch of things, clearing various caches, purging, resetting prefs, resetting the GPU driver settings as I had tweaked the vsync for playback. I've also tried setting ae to just CPU and turning off multiframe. Using version 22.6 Windows 10 on a reasonable machine (Ryzen 9 3900, 64GB ram, RTX 2070) Any thoughts would be much appreciatred.

Hello,   As stated in the title, my problem is that by having just two pre-comps with one containing the video and the second one the audio, it is almost impossible to watch the video when I press "space". The videos themselves are a medium quality proxies that I have created in Premier.I have a very high spec machine and the problem just cant lie with the hardware since on my other computer that has a fraction of ram, cpu, gpu power the playback is smooth.System Specs:Windows 11 Home (10.0, Build 22621)12th Gen Intel i9-12900KS128GB RAMNVIDIA GeForce RTX 3090The video that I'm trying to play is:1280x720 50fps MP4Does anyone know how to fix it? I have tried purging everything, deleting cache again. I have also assigned over 100gb of RAM to AE but it still lags as hell.

The new update has completely bugged my after effects. The warning sign displays the message, 'Low memory warning. RAM use has been extended for previews. Adjust RAM setting in preferences > Memory & Preference'. Despite efforts to fix this issue, it makes the software impossible to use as the playback button will only play a second on a loop. 

Hello,  I'm using Macbook Pro 2016, and everytime I choose the cinema4D renderer in after effects, it crashes and sends a report, is there a fix for this issue?  Thnak you

Has been successfully reproduced on multiple computers.When I am in a project that I have been working on for a while，And Then I type pinyin in the text box， It will undoubtedly collapse straight away

I have created a simple AE project in AE 2022.6 and 2023 on a Mac M1 running Monterey.  The project contains a 54 minute .mp3 audio file (69 MB), a sequence containing the audio file and a text field, and a .json file (1.3 MB) -- the AE project is 89 KB - this project opens fine.   If I drag the .json file into the seqence, it takes several minutes and when I save the AE project is 283.1 MB.  At this point I can't re-open the AE project without AE hanging.  Is this expected?  Is there a limit on the size of the .json file that AE can manage in a sequence?  Why does the program balloon so big if the .json file is only 1.3 MB?  I am attaching the project that opens (without the .json in the sequence) and can supply the .json file if needed.

I have this folder with multiple image sequences. When I select one frame of each, After Effects Compes up with the check box 'Multiple Sequences'. Wheb checked, the import results in 1 image sequence, and the other selected frames are just imported as single frames, not the complete sequences.

Hello all, AE 23 (build 59) won't open past projects (17.5.1) on my 2020 Mac. Alert message,"Last log message was: <940310><BEE_WorkQueue> <5>BEE_WorkQueue_PreCloseProject end"Already tried:Trashing preferencesOpening from AutosavesImporting old project into new projectSent logs HELP PLEASE!Thanks!

I am doing some clean-up on TIF sequences, and am finding that the software very quickly runs into issues. It particularly hates when I reference other layers, and gets gradually slower and slower as I work through the sequence until it hangs and I'm forced to restart. The only workaround I have found is to export as a new TIF sequence and keep working into it. But that is obviously not a viable solution, and I hope to God it's a temporary workaround. I am using a 16 inch 2021 16-core M1 Max MacBook Pro with 64GB RAM, and the way things are at the moment, it's giving my 2015 iMac with 16GB RAM and a Fusion Drive a run for its money. It is unusable and unacceptable that it's performing this badly and I cannot workout what to do. OS Monterey, version is V23 (up-to-date as of this post). You can reproduce this issue by adding enough paint layers to large TIF sequences, and should find the only way out of it eventually is to restart AE.

We get green flashes when rendering VR Chromatic Aberrations with interlacing.  Below is a side-by-side comparison. The problem does NOT occur when rendering progressive (29.97p) OR when rendering at 59.94.   (our workaround to date has been to render full frames at 59.94 and then bring that render back in and re-export in a 29.97 comp with interlacing.) It doesn't matter if the effect is applied directly or as an adjustment layer, we get the same green flashes. Anyone else experience this and have a solution that doesn't require pre-rendering comps that use this plugin?  The problem happens on both Windows and Mac computers and it's been around for many versions of After Effects, up to and including v22.6.0. Thanks, Marc 

In the last week orso my AfterEffects is completely broken to the point of being unusable (even though I'm still paying a full subscription every month!)Preview breaks as soon as I make any changes on the timeline. I open a project, the preview window works fine. I can drag along the timeline and the preview updates.But as soon as I do anything in the timeline, e.g. move a layer, switch a layer's visibility, literally ANYTHING, the preview doesn't update anymore. So basically it's now an expensive previewing software and I can't make any changes whatsoever. No system incompatibility issues.Switched off ALL GPU acceleration.Cleared caches, moved them to different harddisks.Purged everything multiple times.Added more memory allocation.Restarted rebooted, even reinstalled AE.Start new project.  The problem persists. And I really need to use this software for its intended purposes soon!

New for v23!Slight annoyance waiting 2 Seconds for CtrlA to actually select laters in Timeline.(Asus Wrx80 Sage / TRPro3955WX /128GB RAM / GeForce 1070Ti / Samsung980Pro OS/Cache/Files)

I don't know if this happens to you. var num=parseInt(effect("Angle Control")("Angle"));num.toLocaleString("en-GB");I tried these expressions in an old version AE 2020 it worked fine. But when I tried it in AE 2023 it is spitting out } this curly brace instead of comma. 

Even if you unassign Numpad 0 from preview shortcut (which is default) it is still working as a preview shortcut. It wouldn't bother me, but whenever you try to type in text with using "ALT CODE" for example ALT+0176 = degree symbol, you are unable to do it cause instead of typing, after effects starts to preview LOL.2023 and 2022 have to issues, not sure about other versions

My team *loves the possibility of MOGRT files, however, we've run into issues that severely limit its application. Please fix these bugs so we can have a seamless transition from After Effects and Premiere.  -Mode settings do not takeWe have made a lower third and open with the "multiply" mode setting attached to create a specific transparent look. Whenever the mogrt graphic is uploaded to premiere, it loses its transparency altogether. - 3D effects not supportedWe use 3D on many graphics, however, we get an error message when exporting the file as a mogrt Additional info:Our team's workflow is simple. Our photographers will edit a video together in Premiere using their collected assets. During that time, our graphics team will make the Open/Close/Lower/Graphic in After Effects. With the application of MOGRT files, our Photographer team never has to leave premiere, and our graphics team isn't bogged down making copies of the same lower with different text.At this ti

I haven't used this feature in a while, but I remember that it was possible to simply click on it to activate and deactivate it. This was very practical for work. I'm sure it worked, and I still see it in tutorials and courses. Now, to deactivate it, you have to go to the display configuration and remove it from the bar, otherwise it is always on. Every time you use it and stop using it, you have to go to the display configuration. Why did they change that? Or is this a bug? One of the reasons, I think, for the tool was the practicality of programming animations quickly, for any transformation... changing the mode with just one click. As it was once possible to turn it on and off with just one click, it seems to me more like an unresolved malfunction, rather than a purposeful change. Is there anything to do? ThanksAfter Effects 22.06.0 (Build 64) Win 11

When using iphone footage (both hdr or non-hdr clips) i cant interpret footage - just get this error mesage: "Profile rec.709 gamma 2.2 is missing or damaged or doesnt have privileges" and fails to open the intepret footage dialogue Have uninstalled, reinstalled etc. Works fine in v 22.2.1 so i have rolled back to that for now. Am on Apple M1 Max, Monteray 12.5.1.  This needs to be fixed. As of now, i cant properly use my iphone footage in any of the latest versions. I need to intperet the frame rate from 60 down to 30 fps. Yes i can work aorund this one way or another, but there's clearly a larger bug going on if the profile is not readable/accessible and im not risking further unexpected problems popping up, by going ahead in versions with this bug.  thanks.   

Advanced user who needs to tweak render presets per project reports a persistent (22.3 through 23.0) but intermittent (random intervals) error "After Effects warning:  Could not rename the file xxxx to xxxx."  The folder is in the AppData\Roaming tree, redirected by Group Policy on our Windows domain. I can recreate a similar problem by rapidly scripting file creation, renaming, deletion loops with no delay in the same folder.  Running such loops for about 2hrs this morning, I generated a small number of "Cannot create" responses to the Powershell Rename-Item command. My end user just wants the software not to dump his presets.  It appears that the result of this failed copy is loss of both the temporary file ('...output.nnnn.nnnn.txt') and the default settings file ('...output.txt'), with a stock edition replacing them.  End user says, "If there were just a 'Retry' button on the dialogue..." It seems the code here does not do a safe rename opera

In Preferences, with Default Position Properties to Separated Dimension checked. Sometimes it separates dimensions when typing "P" on the selected layer. Sometimes not. Is there a method to produce consistant results? MacOS 12.6Premiere Pro 23.0.0 Build 59

Hi currently when you have 2 layers, - 1 layer with Sepperate position dimentions - 1 layer without Sepperate position dimentions Now select both layers & drag the position (with the numbers). It doesnt update both of them if you select the one with sepperate dimentions. The other way around works. See video for a detailed example. Much love, Dierenwinkel

Has anyone else dealt with or fixed this issue? Drop-down menus with a lot of items in them like Essential Graphics ALWAYS open off-screen so you can't scroll all the way to the top or bottom (depending on where the panel is that you're opening from. It's been this way for several versions and I don't know why it isn't fixed. It should just be a small dropdown that opens BELOW the drop-DOWN menu and has a scroll bar to go through all the options, not this weird long list that opens off screen everytime. 

AE Version: 17.6.0 (Build 46)Reproduction Steps:- Create a New Project- Add a new layer- Animate the position property with keyframes- Apply the following expression to position:posterizeTime(6); transform.positionExpected Behavior:Position animation is posterized.Actual Behavior:Position animation is not posterized.Additional Notes:The failure to posterize only occurs in cases where the expression returns a property directly. For instance, the following expression...posterizeTime(6); transform.position + [0, 0]... does correctly posterize the position animation, despite the fact that it should be returning an identical result. This can be seen in my first example AEP file.The property being returned does not have to be itself. For instance, if the expression returns the position value from another layer, or if it returns the value of a Point Expression Control, it'll again fail to posterize. This happens even if the layer is 3D and pointing to a 2D vector property. The second example