After Effects

Acabo de comprarme una Mac Studio M3 Ultra, luego instale After Effects 2026 y estuve trabajando con inteligencia artificial tratando de resolver el problema de la previsualización y no logré nada. Cuando muevo una imagen en el pre Visual izado de After Effects se comporta como si estuviera trabajando en cuatro o tres cuadros por segundo y a veces más. Cuando comienzo una previsualización tarda entre uno y dos segundos en arrancar el previo. Es imposible trabajar así. No tengo ningún otro Soft instalado en la Mac.

After updating to 22.2.1 build 3 I've got strange problem with "All Caps" feature in Character control.Some letters are "caps" and some are not, some letters can be made bold after that and some not. No issues like that were present in previous version.See attached file. If font is anything else that "Regular" "All caps" is tottaly crazy.

If you're experiencing a problem with After Effects, we want to hear from you! We'd also like to know if you've found errors or omissions in our documentation. The most critical information in a problem report is how to reproduce the issue. It is challenging for us to address a problem we cannot replicate. Please provide detailed steps for us to follow to observe the problem you're encountering. Use the template below to provide us with information: Issue - A short description of the problem.  Steps to reproduce - A numbered list of the exact steps needed to reproduce the problem.  Expected result - What should happen after completing the last step. Actual result -  What actually occurred after the previous step Screen recording – If you think it might be helpful, include a recording of your screen, showing the issue.    Adobe After Effects version - FAQ: How to find the exact version of After Effects you're using? Operating system - Specify Windows or macOS, along with the version GPU

Issue - When working in a composition larger than 10,000px horizontal, guides can no longer be placed at positions further than 10,000 pixels when using the “Edit Guide...” dialog. The dialog accepts values larger than 10,000 in the text box, but will always snap back to 10,000 after clicking “ok”.Steps to Reproduce:Create a comp with a horizontal resolution larger than 10,000 pixels (for example, 11,000) This step doesn’t seem to be 100% necessary, the issue occurs when placing a guide further than 10,000px even with a comp size smaller than 10,000px wide. Turn on rulers and drag a vertical guide out from the ruler. Right click the guide and click “Edit Guide...” to open the dialog box. Edit the “position” value to be a number larger than 10,000 pixels. Click “OK” Observe the guide snapping to the 10,000px position, right click the guide again to see that it is at 10,000px instead of the position entered.Expected Result - Guide should be placed at the position value entered in the “E

I’m a Creative Cloud subscriber. I use After Effects 24 because it runs much better than other versions with the Insta360 footage I work with. However, I haven't been able to open it for the past two days. I really need to get version 24 running again. It simply closes while still on the splash screen and fails to launch. I’ve already tried everything I could find on forums.Intel 13th Gen i7-1370064GB RAM2TB NVMe SSD

I’m experiencing a severe performance issue with After Effects 2025 on Windows:as soon as I open the program, RAM and Disk usage instantly jump to 100%, even with an empty project.This happens with:No project loadedA blank projectOnly one empty compositionClean installation of AENo plugins installed (fresh install)The program becomes unusable and the entire system slows down heavily.1. Main symptoms RAM → 95–100% usage immediatelyAfter Effects alone consumes nearly all of my 32 GB RAMEven without any project, layers, effects, or mediaWindows becomes slow after opening AE Disk → 80–100% usageDisk usage spikes to the maximumStops only after killing Adobe background processes, but RAM remains maxed outAfter Effects sometimes locks the NVMe at constant high read/write usage (70–100 MB/s)2. Adobe background processes involvedThese processes reopen automatically even after being closed:Adobe Dynamic Link Manager 2025Adobe TeamProjectsLocalHub 2025Creative Cloud Interprocess Service (32-bit)H

in After Effects 26.5 custom controls feel a lot slower than the same controls in AE 25.In After Effects 26.5, PF_Event_DRAW for an effect's custom UI in the Effect Controls panel is delivered at about 10fps for as long as the mouse is captured in a send_drag drag. The same plugin build on AE 25 receives 40fps under identical conditions. Hovering is unaffected — 26.5 delivers 90–130 there, which is faster than AE 25.You can reproduce the issue with any plugin shipped with AE that features custom parameters, for example “Curves”. I tried to fiddle around with update flags and working around the drag system but was not able to find a solution or any significant improvement.This is what I’m working with:Windows 11 Pro 26200, NVIDIA GPU. Effect uses PF_OutFlag_CUSTOM_UI, PF_OutFlag_SEND_UPDATE_PARAMS_UI, PF_OutFlag2_SUPPORTS_SMART_RENDER, PF_OutFlag2_SUPPORTS_THREADED_RENDERING. Custom UI drawn via PF_GetDrawingReference + the Drawbot suites, on an arbitrary-data parameter.Here’s a video s

Issue #1:I used to change the state of the On/Off icon for an effect with no restrictions. The state would change as fast as I could click the button. Now, I must move the cursor off the eye icon and back on to change the state. Steps to Reproduce:Add any effect to a layer. Click the eye icon next to the effect name in the Effects Control panel more than once per second. The state (on/off) of the effect does not change. The faster the eye is clicked the less likely it is to change states.It seems like moving the cursor off of the eye icon then back on resets the eye icon’s ability to be changed.  Moderator: Unrelated bug report moved to separate post:. 

Eyedropper next to color properties in Effect Controls panel does notapply the sampled color (26.5, macOS) — regression vs 25.6.6Environment- After Effects 26.5.0 (also installed: 25.6.6, Beta 27.0)- macOS 26.2 (25C56), Apple silicon MacBook Pro- Two displays (scaled external + built-in); reproduces on bothSteps to reproduce1. New comp, add a solid with a saturated color.2. Add an adjustment layer, apply the Tint effect.3. In Effect Controls, click the eyedropper next to "Map White To" and drag   onto the colored solid in the Composition panel.ExpectedThe swatch takes the sampled color.ActualNothing is applied — the swatch stays unchanged. During the drag, the colorfield in the Info panel switches from the correct color to black, while thenumeric RGB readout in the Info panel remains correct.Scope- The eyedropper INSIDE the Adobe Color Picker dialog (click the swatch,  then use the dialog's eyedropper) works perfectly in 26.5.- The same steps work perfectly in After Effects 25.6.6 on t

I have to move from Win to Mac systems but stumbled upon a glaring issue in AE. Using a Wacom Pen set to either Pan/Scroll or Pan/Scroll (Legacy) causes AE to turn the cursor into the Hand Tool to move the comp canvas around rather than perform a scrolling operation.  This is messed up because I want to use scrolling to Smooth Zoom rather than pan around.I don't want to use keyboard shortcuts because that can only be in steps. I also don’t want to hold the zoom tool because it often sticks or is unresponsive. I'm not sure what AE is doing communicating with the Wacom/driver but only AE has this issue. On Windows it's totally fine. I'm on Tahoe using the latest Wacom Drivers and a Intuos Pro CTH-660 tablet.

I have project made in AE26.3 where I am using varible OpenSans font to achieve decided effects. After I updated to AE26.5 it is not working and OpenSans variable is not installed / seen by AE. Other variable fonts are, but not OpenSans. Only fixed weight variant is available.It also show missing OpenSans Roman variable - I do not know why roman, but I believe that should be the problem - wrong indentification. But until it will be fixed I have to use older version, sadly.. 

Issue Built-in Unmult leaves residual alpha instead of producing fully transparent pixels. Steps to reproduce Create a composition. Import footage with a black background. Apply the built-in Unmult effect. Inspect the alpha channel. Expected result The alpha value should become 0 in transparent areas. Actual result A residual alpha value remains (equivalent to 1 in 8-bit). The issue also occurs in 16 bpc projects. Environment After Effects 26.0 Windows 11 Additional information This issue does not occur with third-party Unmult plugins such as Knoll Unmult or Red Giant Unmult.

Used Materials are still listed in the Project Panel when only ‘Unused’ assets should be listed.Type “Unused” in the Project Panel It still comes up even though it’s “Used 2 times”This bug exists in the latest update as well as the Beta

I have some mess after timeline scrubber move sometimes after update to 26.5  

Title: Context menus do not stay open inside modal dialogs (macOS)SummaryOn macOS, right-clicking inside any modal dialog in After Effects causes the context menu to appear and dismiss immediately, before an item can be selected. Context menus function normally everywhere else in the application — Timeline, Project panel, Composition panel, Effect Controls, docked and floating panels. The failure is specific to modal dialogs.System- Mac mini M4 - macOS 26.6.2 (25G83)- After Effects 26.5.0 (Build 89)- Also reproduces in the current After Effects BetaSteps to reproduce1. Open any composition.2. Composition > Composition Settings.3. Left-click the Preset field4. The context menu flashes on screen and dismisses before an item can be chosen.Same result in other modal dialogs, including Output Module Settings and Render Settings.Expected resultThe context menu opens and remains open until an item is selected or the menu is dismissed.Actual resultThe menu renders and disappears on the same

A longstanding After Effects bug that has become incredibly frustrating and feels unacceptable in a professional workflow.The issue affects EXR image sequences from 3D renders.When I use Freeze Frame, or enable Time Remapping and set a Hold keyframe, After Effects shows the frame as frozen in the time-code for the footage. The Time Remap value stays constant and the hold keyframe is present, but the footage in the Composition viewer continues playing through the EXR sequence normally.If I precompose the exact same EXR sequence and apply the freeze or time remapping to the precomp, it works correctly. So the issue appears to be with After Effects evaluating the EXR sequence directly.This has been happening for a long time across multiple projects. Having to precompose every image sequence just to hold a frame is not a reasonable workaround.EXR sequences are standard in professional 3D workflows, and Freeze Frame and Time Remapping are basic After Effects functions. They should work toge

simple 3D scene, 2 lights, background plane, text with extrusion and bevel. Preview is good, render with any Adobe engine is bad. Can see colour banding and random colour block artifacts in the output. Lighting is completely different on the render, illumination in a different spot entirely. Switching to C4D render looks as expected (sooooo slow)Won’t render cleanly with any of the adobe renderers. Render with Adobe advancedPreview and C4D version 

I know this falls into the "this can't possibly be true" category, but please don't dismiss it outright. I have gut-checked this a few different ways over several months, and currently have custom OCIO view transforms to counter it in production.On a Mac, After Effects sends the Composition viewer to the screen without converting it to the display's color profile whenever the project uses the OCIO color engine or has color management off. Every other app on the Mac converts, including Preview and QuickTime Player, so you see After Effects' own render. So the same frame looks more saturated inside After Effects than anywhere else.Every Mac made in the last decade has a Display P3 screen, and with SDR views in Adobe's bundled ACES configs, targeting sRGB or Rec.709, this affects every OCIO user on a Mac.The Adobe color engine converts correctly when a working space is set, so the code path exists. It is just not applied to OCIO output.To be extra clear: on Windows the After Effects viewp

The 26.5 version seems to be really problematic. It crashes a lot when I am rendering project with timeremaped video and I have no autosaves to save my previous work because it just does nothing before render, even when I have Autosave before render ON in preferences.. Sadly need to downgrade also on other machine too..

I can not access the textures for after effects. I was able to last week.  

I consistently experience a problem when trying to select a font for a Text Layer using the Properties Panel or Character Panel. Typing anything in the font combobox to search for a font produces the following error:After Effects warning: Unknown BIB Error. bad INDEX offset array, CT, 0 (83::3)Dismissing the error by clicking OK, the error immediate pops up again, rendering After Effects unusable from this point forward. Additionally, if the project is not saved and an initial save prompt is displayed in the middle of the infinite loop of the above errors, saving or dismissing the Save As dialog will cause After Effects to then crash. Steps to reproduce:1. Create a text layer.2. Open the Properties Panel or Character Panel3. With the text layer selected in the timeline, focus the font combobox in the Properties Panel or Character Panel and begin typing. The "INDEX" in all caps makes me wonder if it's a property of a particular font that is trying to be read during enumer

Hello Adobe team,I am experiencing a startup crash with Adobe After Effects 2025 version 25.1.0.68 on Windows.After Effects crashes during startup, and Windows Event Viewer reports that the faulting module is: Faulting application name: AfterFX.exeFaulting application version: 25.1.0.68Faulting module name: microsoft.ai.machinelearning.dllFaulting module version: 1.24.4.0Exception code: 0xc0000409Faulting module path:C:\Program Files\Common Files\Adobe\Plug-Ins\CC\File Formats\microsoft.ai.machinelearning.dll The corresponding onnxruntime.dll in the same Adobe folder is also version 1.24.4.What I foundI confirmed that the problem appears to be related to the 1.24.4 AI/ML runtime.With the original files:microsoft.ai.machinelearning.dll  1.24.4.0onnxruntime.dll                    1.24.4  After Effects 25.1 crashes on startup.However, I backed up the original 1.24.4 files and replaced both DLLs with the following matching 1.17 build: microsoft.ai.machinelearning.dllVersion: 1.17.20240223.

Hi, I’ve been running into this bug for a while now. I’ve been running into a lot of issues with reconforming audio that come from linked After Effects files. I know it’s not the best workflow to have audio coming from my AE files, but in my use case, I need these sounds to always be perfectly synced with the AE comps, that are also shared with team members.But these are the issues i’m getting:-when using Premiere with Dynamic Linked AE files I have to typically have to wait for audio to conform on my AE files everytime I open a file, even if it’s been untouched.-It also happens if I make a change in a AE comp (not to the audio), even a comp that’s not being used by Premiere, it will still think it needs to reconform the audio that IS being used in Premiere.-Occaisionally, it will randomly unconform without reason.-Lastly, If I have my After Effects closed, it will sometime not conform that audio until I re-open that After Effects project.One thing to note, is that our setup is using L

Maybe it is normal behavior, but I never met it yet.. When I am precomping layers and want to make the new composition as long as selected layers, I am epxecting one layer on the place I had old layers, not trimmed, not offseted.. In 26.3 it does the same as I now checked.When I try to precomp layers and choose adjust precomp lenght... it behaves strange. The precomp is trimmed and offseted. Maybe because the comp time does not start at 0:00:00..I paste two images.. before and after precomping of selected layers..  

DO NOT use identical filenames even in Different folders for linked assets in Adobe. Apparently Adobe is so broken it caches the filenames and can/does accidentally randomly replace them in wrong places during the render (happened with mp3 VO files with identical filenames).