Bug Reports

the  scene edit detection dont work good. it does not find all the cuts 😞the same shot in 23 is working great - scene edit detection work fineHappened several times in different shots 

While we apply the presets in after effects 2024, there's an issue with time.  The keyframes are not placing in the current time, but in different places forward in the timeline. Depending on the preset they are some seconds ahead or even minutes.Before, this version, keyframes where placed in the current time.After Effects 24.0.1macOS Sonoma 14.1 

Trying the convert, let's say, the character 𝟬 from a text layer to a shape layer results in After Effects crashing with the error "Could not convert unicode character (23 :: 46)". This seems to work with all character from the Unicode Mathematical Alphanumeric Symbols block, although it should be noted that not many fonts support this block. I had to use the STIXGeneral font. I am using an Apple Silicon Macbook with macOS Sonoma 14.0.

Is there a reason why when I do Create Camera from 3D View the keyframes from the original camera are moved to the new one and removed from there and the stopwatches next to the properties disappear? It doesn't really make sense. It seems to be a bug I am on After Effects 24. I haven't tried on older versions yet.  

Bonjour, je travaille sous windows 10 pro avec After effects 2023-33.3.0 build 55 et j'utilise mediaencoder 2023 23.6 buil 62.Quand je l'export de mon fichier after effects j'obtiens un résultat faisant apparaitre dans la fenêtre de codage dont une partie gauche de l'image se retrouve à droite!!!( voir captures d'écran ci dessous).Merci de me donner une explication et un moyen de résoudre le problème qui ne se produisait pas auparavant. Je ne peux pas passer aux versions récentes étant dans un lourd projet et risquant sinon de ne pas pouvoir faire des corrections ou d'avoir des incompatibilités entre versions du projet.D'avance merciClaude 

After updating AE to Version 24.01, Mocha won't apply/paste keyframe data in Team Projects. After you apply data from Mocha nothing appears on the layer. It appears to work normally in regular projects. 

Estoy trabajando en una capa, y la selecciono para hacer un keyframe de cualquier cosa (posición, escala, opacidad, etc.) y al hacerlo con el método abreviado del teclado (shortcut) la capa se deselecciona, por lo que debo tomar nuevamente el mouse y volver a seleccionar la capa para seguir trabajando. Esto no pasa cuando hago el keyframe con el mouse sobre el cronómetro. Esto comenzó a pasar al actualizar a la versión 24.0. Antes no ocurría, por lo que varias veces he hecho el segundo keyframe sin percatarme de que la capa no está seleccionada, y se aplica a todas las capas de la línea de tiempo... peor aún, cuando hago esto, no puedo ir atrás con "Command+Z", así que debo eliminar uno a uno los keyframes de todas las capas. Por favor, ¿cómo puedo hacer para que la capa no se deseleccione al aplicar el keyframe con los comandos del teclado? ¡Muchas gracias a todos!

Issue: When you accidentally add keyframes to selected multiple layers and you want to undo this, you need to hit ctr-z as many times as the amount of the selected layers. This is time consuming and not practical at all.As far as I know, undo function used to take a step back from adding the keyframes from multiple layers with just one ctr-z hit. Please fix it.After Effects 24.0.0 (Build 55), Windows 10

When I start to write in some fonts, AE automatically goes to another font after a few letters. When I try and change it back, it only changes some letters. 2017 iMac, 12.6.1. 

I'm running AE 23.5.0. When having motion blur turned off for an entire comp, I'll turn on motion blur for a single layer and this will toggle motion blur on for the whole comp. It should remain off, and in previous versions at least up to 2018 and perhaps more. I've provided a video of what I'm talking about. When checking the motion blur for a sinlge layer this should not turn motion blur on globally for the whole comp. I'm assuming this is a bug, otherwise this would be the most annoying implmentation I've ever seen. Having to constantly go back and turn off motion blur for ram previews, what a drag.

I have created a series of mogrts for use in premiere pro. They have source text that contains "Poppins" extra bold font. Both of my colleagues that need to use the mogrts reported back to me that the fonts are (without a warning) substituting for a default font. When my colleague opens the mogrt in AE, the font issue seems to resolve. But still nothing works to fix it in premiere. I seem to be able to use the mogrts on the pc I created them on in premiere without issue. I have version 23.6 AE. When I was exporting the font I did receive a warning that said:  Problems is - the font family is installed both from adobe fonts and directly onto the computers.

IssueWhen exporting MP4 with audio from AE (H264 output module, with video stream or without), AAC audio priming information is not contained in the MP4 container in the expected format (expected formats are either ISO standard [elst + sbgp + sgpd] or iTunSMPB). Consequence is that (as far as I know) no app other than AE itself reads that MP4 correctly - to everyone else audio has ~20ms silence in the begining and lasts longer than expected. If video exists, audio and video are offset by that amount (as audio has extra silence at the beginning). The most important app that reads MP4 incorectly is ffmpeg, as it is used pretty much everywhere. On top of the everything, even the AE itself provides invalid information on the duration of the audio it rendered itself - it states 10.06933333 for 10.0333333 duration audio (priming samples seems to be a part of that duration [remainder ones as well, but that is expected]).AE 2023 and AE 2024 beta are both importing mp4 with correct audio primin

AE 22.6.0 (Build 64) keeps throwing error: attempt to remove an item from a position outside of list length (27 :: 9). The error happens any time you undo something, or move a layer or keyframe in the timeline. Working inside a TEAM PROJECT, which I assume is part of the issue. AE is almost unusable as the error throws constantly.

I made a file that causes my installation to seemingly melt down. these are the steps i took:Open a new projectCreate a new Comp (4k/60, 10 seconds long)Created new Shape Layer with a single path. (no fill, 400px stroke.)Added a twist to the layerAdded a Wiggle Paths This is where it all stops working.  I no longer get a preview. AE freezes when i attempt to quit. and when I open back up it asked to start in safe mode.  I have uninstalled AE multiple times, tired several version all with the same results. I am also attaching the AE file I made with the steps outlined above.  More info After Effects versions I tried:23.623.523.3OS and Computer:MacOS 12.6.9 (i updated my os as one attempt to solve) What the hell is going on?

Video shows everything. When trying to adjust RED raw metadata settings I'm able to type in my changes no issue on other common settings, but for whatever reason I can't do so on tint. On tint I can only get it to save if I drag the slider. I tried all of the reload and save preset etc. options on the top right, none of those solve the issue of not being able to adjust tint. Only solution is dragging the slider. Pretty random and funny bug but figured I'd report it as some people may not figure out that they need to use the slider. Video: https://drive.google.com/file/d/15GmPKnS2Nb7Kx_4nzf9_5-ClWueECviI/view?usp=sharing

This looks bad. Premiere pro does the same thing too.How to fix this?PS: Photoshop respects OS color scheme properly.  

So this has been driving me nuts since version 22 came out. Working with ProRes 4444 files, color management turned off.  While playing back a clip the color will subtly shift for a few frames and then go back.  It will happen numerous times and seems farily random. I have posted two screenshot with the scopes turned on so you can see the difference.  It's so subtle it hard to catch (especially if you are working on LOG footage), but it's there and happens every project. The only way to get it to behave normal is if I turn color management on.  This is a no-go for our workflow though as we've been roundtripping files in and out of AE for years and color management always leads to inconsistencies when bringing into other applications (in other words, please do not suggest we change our workflow in order to accomodate an obvious bug). We've tried all the usual suspects...restart, clear memory and cache, turn GPU acceleration off, etc. Sort of surpr

Hi,I have a 2D hand rig (parented PSD layers with some basic scripts for IK and pointing, DuIK and custom) which worked fine in 20018-2019 versions (older PC).Now, in 2022 and 2023 same project (newer PC) throws curveballs at me - even I get smooth animation with scrubbing, the objects (rig controls, layers) start to jump and jerk around as soon as I try to preview them. Also, there I see some inconsistencies between rendered pixels and layers wireframes even after I do cache+mem purging.Even changing some layer visibility impacts the inconsistencies, just at different frames, worst thing to nest 12.5fps animation com to 25fps main comp (or setting all to 25fps and adding PosterizeTime effect).The worst part is, I have a copy of this very comp with expressions links to the rig controls, so its animation automatically updates in both comps. When I compose those two one over another, the output in both differs.Disabled multi-frame rendering, latest Nvidia Studio drivers, disabled ha

I've been running into an issue with Essential Properties and media replacement.Ater I add my "template" comp to a main composition, I twirl down the Essential Properies in the timeline OR use the properies panel but my Media Replacement line disappears. I have essential properies above and below my media replacement and they display just fine.Right now, my only fix is to "pull down" from the original master property - this SOMETIMES seems to load the full property stack, including my Media Replacement layer.Another bug I have encountered is my essential properities "dissapear" but I can tell that something is still there in the layer stack. If I blindly click on the blank area in the layer stack, the essential property displays. If I scroll up or down, they all disappear again. Clicking around for the master property "pull down" seeems to temporaily fix it.Has anyone else encountered this type of bug? I know I've experienced it for the last two years of After Effects updates.

Yikes! Mac M1 UltramacOS Monterey 12.6AE V23.0.0 Color settings:32-bit ACES working space (Title edited by moderator.) Has anybody noticed a green flickering hue with Prores 4444 material?Preview and rendering have random flickering frames.I noticed this in my latest project. Did not happen before with other Prores material. Tested both with the client's original and re-encoded versions. Colour management or anything does not seem to affect it, but...Turning off the hardware decoding option in Settings seems to help: Settings - Import - Video Footage - deselect hardware accelerated decoding box. Just lost two days' worth of hours.

Hello,Would love help with this Adobe AE 2023 bug! Problem:I'm attempting to use Adobe's code here (under "Custom layout-manager example").This code builds a window with a button that has a custom location in the UI.Example here:But when I run Adobe's code example in After Effects 2023, it crashes.  Parts of code that crashes:// of "container" in a stair-step fashion. function StairStepButtonLayout( container ) { this.initSelf( container ); }win.buttons.layout = new StairStepButtonLayout( win.buttons );  Question:How could I solve this crashing issue? Thank you very much!

Windows 11Pro 10.0.22000 Build 22000AE 2023.5 I'm experiencing very long-duration pausing/freezing when I use the EG panel.Cause: I add a parameter to the panel. Then change anything and try to select another item in the panel. AE becomes unresponsive (as seen in task manager) for between 15 seconds and 3 minutes. I observed that sometimes if I click in the comp and then back to the EG panel it won't freeze, but this is not consistent. As my project has grown the delays have increased. Unfortunately, I'm accessing much of the same source materials and even precomps across mogrts. I wonder if this is related to the menu issue. I am creating a package of mogrts and I figure this is costing me about 120 minutes a day. 

Issue - I'm converting an existing project I was working on using ACES with the OCIO plugin to the new native AE implementation, but despite the footage color spaces being set correctly (exr 2065-1 sequences), AE doesn't map correctly to sRGB, space that I have selected from the dropdown "Display color space" of the composition. However, if I create a new project from scratch, with the same footage, and do the same settings, in a new composition, this time it behaves as I would expect. Another piece of information that can be useful: in the footage viewer it looks correctly mapped, this problem occurs only in compositions.Adobe After Effects version number: 23.4 (Build 53)Operating system: Windows 11Steps to reproduce - 1. Open an old project that uses the OCIO plugin to do color management with ACES / 2. Remove all instances of the OCIO plugin and delete any related adjustment layers. / 3. Configure the project to use the native implementation of OCIO-ACES / 4. Interpre

After Effect is crashing after using rotobrush, and I can't use AE at all.I did update my brand new computer MacbookPro M2 Max OS Ventura,It didn't change anything. I even format my computer, de-installed and re-installed the last version of AE. After calling several time to Adobe for a week, this is the worst customer service I ever experience. Nobody was able to tell me what was the problem. I need to talk to a real expert who will solve my problem (and not randomly tell me to install and reinstall my app or update my computer). I'm thinking Adobe have real issues of compatibility with Mac OS Ventura.Is anybody else experience those issues?