After Effects (Beta)

app.project.usedFonts doesn't work Properly, If we duplicate a text layer and change the font of either one of the layers, It won't detect the old font used in the original layer. Even if we remove the layer which have the new font. It always shows us the removed font (second font). Not the font that remain in the project.

Version 24.5x4 of After Effects Beta introduces support for two new 3D features in the Advanced 3D renderer: shadow catchers and shadow colors.   Shadow catchers are 3D layers that “catch” shadows cast by 3D models but are otherwise transparent. They’re a great way to make a 3D model look like it’s part of a 2D video or image.   Beta users can also customize a shadow’s color tint and opacity for a more realistic composite. Color can be set per-layer rather than per-light, which makes it possible to do things like cast pink-toned shadows on a model while the model casts blue shadows onto the ground. Shadow Color also works with shadow catchers.      Getting Started Shadow catchers and shadow colors work with any 3D layer that can accept shadows using the Advanced 3D renderer. The Accepts Shadows and Shadow Color properties can be found under Compositing Options for 3D model layers and Material Options for native AE 3D layers (3D text, shapes, solids).   To

Starting with Beta build, AE 23.0x11, H.264 is now available as an option in the Output Module Settings dialog allowing you to encode to H.264 directly from the AE Render Queue.     This integration utilizes the Adobe Media Encoder (AME) UI along with AME’s backend encoding system all without leaving After Effects. We have also included 3 H.264 presets to get you started.   If you need more control, you can customize the H.264 settings by clicking on a Format Options button in the Output Module Settings dialog. Not every option that is available in AME is exposed inside AE, and some settings such as resolution, frame rate, color management, are still set from AE’s Render Settings or Output Module Settings, but there should be enough to tweak for most users.   H.264 export also supports both Hardware and Software Encoding modes. The same accelerated export you have in AME and Premiere Pro is now available for H.264 export in AE.   If you need more control or sp

in camera no depth of field

Lumetri Scopes Panel shows nothing sinse the Spectrum UI updates 

Feature request:Right now we only can see how many Comps there is in one particular selected Folder.Can we please have this improved and be able to see how many Comps there is while selecting more than one Folder? Also while selecting only Comps.

after selecting project. close automatically after effects.

1. Adobe After Effects (Beta 24.5.0 (Build 46))2. MacOS, Sonoma 14.4.1 BASIC STEPS TO REPRODUCE CHALLENGEI continue to get an error about the Cap Locks needing to be disabled, even though it is. To replicate: 1) Shuttle to a different location in the timeline. - Error: Refersh Disabled (Release Caps Lock to refresh view) Or 1) Select the Roto Brush Tool 2) Click on the layer to apply the Roto Brush Tool- Error: After Effects (Beta) warning: Roto Brush strokes cannot be added while Caps Lock is engaged.  To temporarily resolve both errors, type any key on the keyboard. Afterward, replicating Step 1 in either scenario above creates the same error.  To resolve, I quit and reopened After Effects, same issue. I tried using After Effects 2024 and the same issue occurred. I replaced keyboards, same error occurred.  EXPECTED RESULTSWhen Cap Locks is off, these error messages should not happen.

tengo 128 Gb de ram,  y aun asi a veces colpsa y se traba

Hola! Tengo un PC Windows 11 con una tarjeta NVIDIA T400 de 4GB y he actualizado las versiones BETA de After Effects y Media Encoder. Sin embargo, no puedo exportar una composición de After Effects a Media Encoder.  Sale un mensaje diciendo: "Error de Dynamic Link" - El origen está vacío.  ¿Cuál es la solución? Gracias

Steps to reproduce:    1. Run "Scale Composition" script Result: Dialog opens but impossible to read input over almost black background.Expected: Contrasting colours for legibility Medium-dark is better but not great. Light looks fine but my eyeballs are aching. Thanks,Laurence System info    Application: After Effects (Beta) v24.6.0.13    OS: macOS v14.2.1, RAM: 128.00 GB GB, CPUs (logical): 16 PS. I fully expect After Effects to complain when I pull the trigger on resising this comp which is already enormous.

Sometimes, when i want to render a 3D Object, the model itself disappear and in the video you can see the blue 3D-Box. This happens randomly, with .gltf and .obj files and it appears sometimes only at one frame in the rendered video. 😞 How it should look like.       What actually is shown.    

The reference frames created in the Content Aware Fill window have mismatched colours.  In the attached picture you can clearly see the hard line between the footage and the reference frame.  This is the same on my Windows machine and every mac we have in the office. 

Recently I've posted that it has been fixed but it was just a lucky day where I tested it and it opened with no misclicksbut to day it is happening again...here is the fresh screen grab of the issue:(in ae so as pr) 

Steps to reproduce:    1. apply Lumetri Color2. Twirl down curves3. add two points on any horizontal curves4. grab one of them and try sliding passing by the middle Result: ... it jumps through the invinsible teleporting portal that sends it to the backroomsExpected: ... to smoothly follow the mouse drag System info    Application: After Effects (Beta) v24.6.0.7    OS: Windows v10.0.26217, RAM: 47.86 GB GB, CPUs (logical): 16 P.S. this bug exists from the very beginning of the updated lumetri effect with horizontal curves to replace the circular ones

Importing PSD files freezes Ae and consequentially requires forced closing the software.For comparison no issues with the same PSD files in Ae 2024.Something to do with the recent importing to folders in Project Window update? 

If you call $.colorPicker and just alter the sliders it's fine. But the moment you actually use it to sample a value, it then always returns the wrong value. 1. Run attached colorpicker_bug.jsx script. The hex value is sent to $.colorPicker then updated on return.2. Click Picker and use the picker's sample tool to sample a value from anywhere. For example, the blue from the selected AE toolbar item. Note the hex and RGB values displayed.3. Close picker and hex will show different returned values. Click Picker again and you'll see how it's altered the RGB values. Actual result: The blue from selected AE toolbar item is hex 066CE7 or RGB 6/108/231 according to $.colorPicker after sampling, but it then returns b52e1 or RGB 11/82/225. Expected result: you had one job $.colorPicker!  

1. Create a shape layer2. Draw a path3. Select all the points and do a ctrl-T to make the transform controls appear4 .Scale it5. Move the anchor point of the bounding box6. Scale it again7. Notice how the scaling ALWAYS works relative to the oppsite corner, and completely ignores the position of the anchor point (I'm not talking about the LAYER'S anchor point - just the "temporary" transform box's anchoer point)

Steps to reproduce:1. Close the Properties panel2. Click the Type Tool icon, ready to add some text to a comp Result: Properties panel re-opensExpected: Properties panel to remember that I closed it. I know this panel received a lot of love from Adobe when it was introduced relatively recently and I'm sure they want to show it off to everyone, but if I close it, I want it to stay closed thankyou very much. System info    Application: After Effects (Beta) v24.5.0.46    OS: Windows v10.0.19045, RAM: 127.91 GB GB, CPUs (logical): 32

After installing the Ae Beta 24.5.0.45 They seem to appear once at every first initialization in the project so it happens either when I load a project with them already or when I add effects but only the first time as I add them so far they don't affect effects to not working

my glb animation in 2024 after effect beta not working

I have a simple model, created in Blender. I export it as an OBJ, import it into AE, and put it in a comp, add a camera, and all is good. I then update the model in Blender, re-export the OBJ, go back to AE, right-click > Reload Footage on the model (both the .obj and the .mtl), the Comp Viewer redraws, but nothing's actually changed - it's still the old model and old materials. Even if I do a Purge All, AE redraws, but it's still the old model. The only thing that forces an update of the model is to close and reopen my AE project. Here's AE showing the old model, even though I've updated and 'reloaded' it:I then save, quit and reload AE (or just close and re-open the project), and having made no changes to anything, it now shows the updated model and materials (cyan line is now blue, and there's an extra yellow line in there, which is all correct):I'm on AE 24.5.0x34, Windows 10. ~ Paul 

LUT processing in After Effects now has the option to use a more precise calculation method called Tetrahedral interpolation. The result is smoother gradients and better-looking results when applying LUTs.  The old method is called Trilinear and is still available. This option can be found in the Project Settings.   Below is an extreme example for illustrative purposes:    ORIGINAL:  Your basic ramp . . .       TRILINEAR (old method):  Notice the severe banding.  This occurs when you have smooth gradients and the LUT doesn’t have enough precision to handle the small steps.  In practical terms, outdoor shots with a blue sky are a good example of smooth gradients that you see often.       TETRAHEDRAL (new method):  Notice the smooth gradient.  Tetrahedral uses a superior method to interpolate values in between the steps, so even with a low precision LUT, you get ver

In the composition panel, in the current Beta version of After Effects, the breadcrumbs of the comps are missing the active state of the current comp. It's hard to tell which one your looking at. Before the comp you are in would have a selection on it. 

 I believe this issue occured in the past, it was reported and fixed.I might be wrong but it looks like it came back with the few recent updates.It doesn't happen every time.