After Effects (Beta)

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

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)

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 

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.

The historgam of the Levels effect is barely visible with the latest Beta; see screenshots attached.System info    Application: After Effects (Beta) v24.2.0.50    OS: macOS v14.1.1, RAM: 64,00 GB GB, CPUs (logical): 10

When I zoom in or zoom out the screen or move the guide line my compositon panel got freeze. I already contact to customer support they also did not resolve my problem.

Trying to start aerender from the console gives: dyld[90248]: Library not loaded: @rpath/libtbb.dylib Referenced from: <B396A383-BFC0-3E47-948C-185ADC2FAF73> /Applications/Adobe After Effects (Beta)/aerender Reason: tried: '/Applications/Adobe After Effects (Beta)/libtbb.dylib' (no such file), '/Applications/Adobe After Effects (Beta)/libtbb.dylib' (no such file), '/Applications/Frameworks/libtbb.dylib' (no such file), '/Applications/Adobe After Effects (Beta)/Frameworks/libtbb.dylib' (no such file), '/Applications/Adobe After Effects (Beta)/libtbb.dylib' (no such file), '/Applications/Adobe After Effects (Beta)/libtbb.dylib' (no such file), '/Applications/Frameworks/libtbb.dylib' (no such file), '/Applications/Adobe After Effects (Beta)/Frameworks/libtbb.dylib' (no such file) zsh: abort ./aerender The needed file is under /Applications/Adobe After Effects (Beta)/Adobe After Effects (Beta).app/Contents/Frameworks/libtbb.dylibbut this directory is not in th

After today's Beta update there's a pop up window upon the application launch (see the image attached).There's no way to close the window and proceed to start using AfterEffects.In results the app has to be forced shut down from the Windows Task Manager.  

I have been using the beta and there is problem , most  of the time my both preferences got reset and lost my recent project in recent files ,thats annnoying  for the work and you to relocate the project every project again, it happens with beta and also the prefrences got reset in the main version of after effects 

Steps to reproduce:If I click on different layers in various comps, the ECP often fails to update; it might still show the effects controls for a layer I selected some time ago. I've never seen this issue before, and it doesn't happen (on the same project) in the release version (24.3.0 Build 50). Also, sometimes if I enter a value on a layer's effects (eg. the amount of Gaussian Blur) when I press Enter to exit the number box, AE opens that layer. UPDATE: Yes, this DOES happen with the same project in the release version! Very weird. I would be happy to send the project (not publicly) to Adobe for analysis.System info    Application: After Effects (Beta) v24.5.0 Build 8    OS: Windows v10.0.19044, RAM: 127.92 GB GB, CPUs (logical): 32

Friends, colleauges: Of the many documented properties+methods available in ScriptUI to position and resize dockable ScriptUI palettes in After Effects, most of us have tinkered with: win.bounds = { Bounds object } win.windowBounds = { Bounds object } win.frameSize = [ width , height ] win.size = [ width , height ] win.location = [ x , y ] win.frameLocation = [ x , y ] ..but these don't appear to work anymore. Or, maybe they've gone read-only? Is there a new, preferred way to script (set, rather than get) the position + location of ScriptUI palettes, or has this functionality been deprecated? Just curious, no pressure. Below is tests.jsx which creates a dockable window, then alerts the user to different attempts at resizing or repositioning it, using the methods listed above. When tests.jsx is placed inside AE's ScriptUI Panels folder, the methods don't work. When tests.jsx is launched from VS Code, the window resizes+relocates as expected.&nbsp

Colorspace workflows not functioning in latest AE beta, works fine in standard AE. Using the OCIO colorspace transform plugin to change footage colorspaces has no effect. Same for any adjustments in the color management area of the project settings.

If a text layer contains multiple justifications on different layers, editing text using character range can cause justification to incorrectly change. Steps to reproduce:1. Open justifyText.aep and have Comp 1 open and active.2. File > Run Script....run justifyText script. Script output:"top line justify = 7413 next line was = 7414changing text to = *1234*top line justify now = 7414 next line now = 7414"While the (0,5) character range covers a single justification setting across the top line of text,changing the text (still 4 characters plus return) causes it to adopt the justification of the next line.3. Undo the text change or Revert Project, comment out line 10 of script and try again with lines 11 then 12Script output:"top line justify = 7413 next line was = 7414changing text to = *234*top line justify now = 7413 next line now = 7413"Result: This time, the change seems to cause the second line to adopt the first line's justification. Expected Result: Justificatio

Either I'm missing something or Kerning doesn't appear to work properly with character range queries. It mostly seems to return undefined, even for a character range of a single character. It's potentially important to check if kerning has been manually altered to be able to take steps to preserve that kerning during a scripted edit. autoKernType seems to work as expected, only returning undefined on mixed autoKernTypes in a single text layer, it's just kerning that does. Makes it impossible to query in any useful way. 1. Create a comp, a text layer with some text, set to Metrics. Run attached kerntest script and you get:autoKern all = Metrics first char = Metricskerning all = undefined first char = undefined Kerning should be returning 0 in both cases (the scripting docs say so too) 2. Use Character panel to set Kerning to 0. Run script:autoKern all = None first char = Nonekerning all = undefined first char = undefined Kerning should be returning 0 in both cas