After Effects

I am building a mogrt. I use a dropdown menu to choose between 20 preset color combinations. To make the ux a bit more comprehesive I want to use separator-lines between diffrent groups. The way to do that is to name items "(-". The problem is I can only make 1 separator line. If I try to edit more than on item the change just gets ignored. When I edit, write "(-", press enter it goes back to be named "Item 5". Is this a bug or can you realy only use one separator line? I am using AE 23.2Mac OS 13.2 (22D49)MacBook Pro M1 Max

When rendering out videos, with many layers, png sequences and imported photos/videos as a .mov with alpha channel, flickering lines of pixels would appear and disappear throughout the final output. I am using an older version of After Effects: 17.1.0,  on a Mac (High Sierra, 10.13.6).It seemed to be inconsistent when these glitches would appear. I rendered out several of these sequences with no issue, until a certain moment when it was appearing on every subsequent render. The solution seemed to be to clear my cache before peforming each render. I used Edit > Purge > All Memory and Disc Cache. A couple times this didn't work, but restarting my computer, clearing the cache again, then rendering seemed to solve it. Hope this can help someone else in the future!

I updated to AE 23.2.0 (Build 65) this afternoon.Some existing projects will not open. An "unexpected data type" error occurs, and the project terminates.There are some 3rd party plugins that are missing (Light Factory & Optical Flares), but previous versions of AE were able to open these projects and allow me to edit them.I've reverted to AE 23.1.0 (Build 83), and the projects open successfully.Thanks for your time.

Hi! I've just installed and launched After Effects for the first time. After opening this error pops up, after that it can be closed only from windows task manager. I've tried to reinstall it - it didn't help. After Effects error: Crash in progress. Last logged message was: <14568> <Scripting> <5> Executing startup/shutdown script at C:\Program Files\Adobe\Adobe After Effects 2021\Support Files\Scripts\Startup|commandLineRenderer.jsxPlease help me, I badly need this soft for my classes... This is specifications of my laptop:Asus ROG Zephyrus G14OS - Windows 11 (x64) RAM: 16 GbGPU: Amd Radeon RX 6700sCPU: Amd Ryzen 9 6900HSSSD 1 Tb 

Time remap has a bug after update to 23.3 Cant enter specific frame values anymore when using image seq Anyone else facing the same issue ?

I have installed Creative Cloud and the latest version of After Effects, but every time I try to start it from CC it won't open, it won't even sleep the software. However, if I open it by going to the installation folder and starting from "AfterFX.exe", the startup screen appears but after a couple of minutes it just shows:"After Effects Warning: Unknown Exception". I have tried uninstalling After Effects and Creative Cloud, deleting all folder files, including temporary and data files, and nothing works. Please, I need urgent help for my work.  If you need any log file or something, please let me now.After Effects 23.2Windows 10 x64

I am working on an After Effects project, and often when I open or close it the project has reduced itself. This means that all the imported files I have not used get automatically removed. It happens without me going onto File > Dependencies > Reduce Project. It is quite annoying as I need those other files I improted and have to do it twice. Sometimes it happens even WHILE I am working!! Anyone knows about this issue?

I have the latest iMac27 and I still get the low memory messages - and I am on 23.1! here are my specs: macOS Monterey Version 12.6.1 iMac (Retina 5K, 27-inch, 2020)Processor 3.6 GHz 10-Core Intel Core i9Memory 128 GB 2667 MHz DDR4

Audio during preview in a particular project stutters a bit, and then completely stops. This issue has happened before for me, and restarting seems to fix it, but then I find myself having to do it over and over.I have read a number of posts on this topic, but none of the advice I have seen applies or helps.  Audio works fine elsewhere on my machine. I have adjusted cache and preview settings as well as cleared cache. I have reloaded the audio track. My Windows machine has sufficient power and RAM to handle this as well as SSDs.Not sure what else to do. It's severely affecting my workflow. 

Dear all, I am using the Rotoscoping tool in one of my projects.Unfortunately it only works on the first frame! If I want to select the object a few seconds later it creates a pink frame around the whole shot!  And also if I choose the object on the first frame and hit space bar so that the propagation starts I cannot adjust anything anymore becuase it ignores the tool after the first frame! Anyone an idea what I am doing wrong? 

Hi Team,I'm getting this dialogue from Yesterday. Can you please check and help me?Please find the attachment with this message for more details.  

Windows 11 Running After effects 2023 & Premiere 2023 where both issues exist. When I use a white solid or a shape layer as a background, I get a weird border artifact that appears only at certain times in the program, but always in the renders.  In the attached image "Boarder issue 2" and "Boarder issue 3" you can see the lines appearing at different viewport zoom levels (12.5% and 25%) they disappear at 50% and at 100%, but regardless of what the viewport is, they will appear in the final render. If I add a white rectangle/solid behind the video like in  "Boarder issue 4" the outline disappears (in this case I put the solid behind half of the video) but it will still appear in the render.  Trying to export from premiere leads to a similar result, in "border issue" you can see scaling down the video (or up to try and crop the border)  still results in a new border being created. I have rendered in H.264, MOV. Transparency videos. none s

Hi, I am trying to use Warp Stabilizer a clip shot on a DJI Air 2S in After Effects 23.1. It freezes constantly and will not complete the analysis. I tried transcoding the clip to ProRes 422, which hasn't fixed it. It's odd, as the clip stabilizes just fine in a Premiere project of the same spec. Is this a known issue? Thanks, Enzo

Please help 😞I updated to Ventura yesterday and since then AE keeps crashing after a few minutes, saying "create recovery project - auto-save processing 0%". There it freezes. In another project it crashes when trying to save. That even caused a total system crash one time.I already uninstalled AE and reinstalled. I emtyed all caches. I checked login items and read-write permission I treied disabeling auto-save and multiframe render. Nothing helps and I'm in great despair, as I have a deadline today 😞 I hope you can help... Thanks in advance!Working on MacOSX Ventura 13.2, with AE 23.1.MacBook Pro 16" 20192,6 GHz 6-Core Intel Core i716 GB 2667 MHz DDR4Intel UHD Graphics 630 1536 MBCrash-log in attachment.

So when I preview my project it plays perfectly fine until it reaches a specific clip on in the comp and audio cuts off. Whenever I delete the clip and preview again the audio just cuts out at another clip later on. Also whenever I preview starting at a clip where the audio cuts out it takes forever to load the preview, then the clip plays fine but the same issue occurs and audio cuts on another different clip. I have tried purging Memory & Disk Cache many times, I even converted the audio files because they were .WAV and I thought that was the issue. Restarting and Reinstalling haven't worked either, and it isn't a high framerate issue I believe. When I delete all .MP3 files from the comp the preview plays flawlessly with no freezing or slowing down.  Using a Desktop w/ Windows 10, 32GB of RAMAE 2021 (Version 18.4.4)  Any suggestions?

For about a week now I've had ongoing issues with AE. The intial issue was AE running VERY slow on my Mac. Eventually I went backwards, uninstalled AE 23.1 and installed AE 23. That fixed the slow issue but now I'm having a new issue where AE crashes whenever I try to open the settings menu. I've tried deleting the preferences upon startup. I've deleted the preferences from the Finder. I've deleted prefs and then migrated them from a pre 23 version but none of this has fixed the issue. I'm desperate for a solution to this issue. I'm on an Apple M1 Ultra on macOS 13.1

Bonjourà tous,je n'arrive pas à ouvrir After effects, toutes les autres appli Adobe fonctionnent.Plantage et message d'erreurs à l'ouverture :Dernier message du journal : <519748> <AppDirs> <5> Required Dir = /Applications/Adobe After Effects 2023/Adobe After Effects 2023.app/Contents/Required . Génération du journal des pannes en cours. Cette opération peut prendre quelques minutes.Et ensuite il plante.MacBook Pro3,1 GHz Intel Core i5 double cœurntel Iris Plus Graphics 650 1536 MoMacOs13.1 (22C65) Merci d'avance pour vos réponsesJ'ai déja essayer de désinstaller et réinstaller plusieurs fois sans résultatsRapport çi-joint

 Adding to render queue has a loong pause now.Hitting render has long pause also.feels like I am using RendergardenAssume it is a MFR thingSort yer kernals out!23.1, Windows10, Intel i77820, geforce1080 32GB RAMps(character limit on subject needs to go now please it isn't the 90s)

Hi, I am experiencing an problem with aerender.exe in 23.1.0Looks like this is an similiar problem here: https://community.adobe.com/t5/after-effects-discussions/aerender-exe-fails-with-quot-the-procedure-entry-point-getsystemdpiforprocess-could-not-be-located/td-p/12791074but I am not using Azure VMs but local Renderblade servers from Dell with Win10The latest and legacy Redists are installed. I have the feeling that aerender wants a physical GPU since the new versions. Could that be possible? I mean, it would suck, but it would be at least a explaination.If so, maybe a command flag like -nogpu could help to tell aerender.exe not to search for GPU related stuff at startup.I would be very happy if some would consider it somehow important. The current workaround is to use an earlier version of afx, but that cannot last forever.Many thanksAndreas

Issue - Opening an Ae file from Windows explorer by double clock or by pressing keyboard enter "sometimes" returns error:After Effects Warning: project file "file path and name" doesn't existAdobe After Effects version number V23.1.0 (Build 83)Operating system Windows 10Actual file path on hard drive:D:\Projects\GOSI 8 Motion graphic production\Vid 04\Ae\GOSI_Vid 04_12.aep

I have a client who asked for an 18.x version of the file I was working. I built the file in 23.1 so I backsaved a version for him. The problem he and I found was that weird anomolies begin showing up. Specifically, when I add a null and try to move a group of layers, they don't move with the null. You can see the outline of the shape layer in its new position, but you can't actually see the change until you close AE and open it back up again.

 When hiding keyframes with a keystroke (i.e. pressing “U” after keys have been revealed to hide them again), I was noticing a delay before layers collapsed. Since I use this keyboard shortcut often, the delay was disruptive enough that I reverted back to the previous version (where it now works properly). I’m working on Windows 10 so it may be fine on a Mac. Thanks!

Inner / Outer key crashes when used on a layer that has preserve RGB on and has a mask on it whilst working in 32 bit in an aces colorspace

Currently when you change the IN and OUT point of the responsive design - time the keyframes don't stay in place, get stretched out. When you try to move them back they behave very weirdly like it's skipping spaces in time. When you try to select them for a second time to move them they freeze can't move the keyframes.To fix I have to copy and paste the keyframes 1 at a time cuz selecting 2 doesn't work. Unless you use a tool like motion 4 to copy the keyframes.I uploaded a video with proof.Can't share the file sadly cuz nda. M1 Max, AE 23.0.0Please fix, Much love, Dierenwinkel

I am an engineer who is developing Adobe Extension using CEP. Through the Script UIWhile looking for a way to handle the layer panel's keyboard event, Adobe Application was able to verify that all external key inputs were collected.This seems to be a keylogging security issue. It looks like action is needed.