Questions

I saw awhile back one of the update notes said:"Fixed an issue that caused a delay for the render job to start. (v18.2.0.9)"However it seems like I still have a long delay between hitting Render and the render actually starting, giving me the blue stripey-string -- and it does it between each composition in the queue. Was that note referring to something else, or is something still broken here? It actually seems to have gotten worse as of the latest beta from yesterday; now when I hit render, I get absolutely nothing for many seconds before I even get the blue stripey-string, which I then have to wait after.This is on Windows 10 Pro 20H2, 6-core Xeon, GTX 1070

  Steps to reproduce:    1. ...Create a new comp (32bpc)Created a SolidTurned solid into 3d layerTurned on Draft 3dTurned on 3d Ground PlaneTried to navigate the viewport Result: Lower half of the comp view turned black.Expected:   System info    Application: After Effects (Beta) v22.0.0.32    OS: Windows v10.0.19042, RAM: 15.90 GB, CPUs (logical): 12

An old nghtmare comming back !!! The top  panel size of the window are not saved. Each time I open AE the pmanel size is set to a default minimum value.In AE V18 I found a workaroud : not setting AE in full screen !!! then the panel size are saved correctly. This woraround worked also in beta.But since last beta version (22.0.0 build 30)  it does not work any more. The top panels of the window are allways openned at default minimum size !!!! Is it possible to solved definitively this problem  ?Thanks for your helpJean

From After Effects 2020(17.0), the displayName that can be obtained by the script is garbled in Japanese.In addition, there are other issuesJapanese cannot be specified by app.findCommandId.The characters are garbled in aerender.Please fix it. 

More of a non-issue but still something that leaves a sour aftertaste right now. The Beta, for the last few incremental versions, is throwing me a debugger related notice when exiting.I just tried cleaning out the prefs (everything except for workspaces and keybindings) and the issues still persists. Message is attached  

Whenever I hit Space or the play icon in the preview pane, nothing happens. The playhead does not move 

Using latest After Effects beta. Bar above timeline indicating what's been cached seems to change once you actually hit play, sometimes doesn't represent what's actually there, sometimes doesn't show that something is being cached while it is, and sometimes hitting spacebar requires a second press to actually start caching. I've included a video demonstrating the problem.

Three new, highly requested APIs have been added to the Scripting DOM:Layer.id,Project.layerByID,Property.essentialPropertySource,All available in AE Beta versions 22x25 or newer. Here's An In-Depth Look At Each API:Layer.idapp.project.item(index).layer(index).id DescriptionInstance property on Layer which returns a unique and persistent identification number used internally to identify a Layer between sessions. The value of the ID remains the same when the project is saved to a file and later reloaded. However, when you import this project into another project, new IDs are assigned to all Layers in the imported project. The ID is not displayed anywhere in the user interface. TypeInteger; read-only. Project.layerByIDapp.project.layerByID(id) DescriptionInstance method on Project which, when given a valid ID value, returns the Layer object on the Project with that given ID. Parametersname descriptionidA non-negative integer representing the ID of the Layer

Steps to reproduce:1. I set AE to use 52Gb of my 64Gb ram in AE prefs (shared among pool of Adobe apps)2. The "Show Memory Usage Details" in prefs claims that only 42Gb is in use, while my Activity Monitor, the Top process in terminal and iStatMonitor all claim that AE is using 62,63Gb ram, causing Macos to start swapping Result: AE is using more ram than set in prefsExpected: use as much as set in prefs System info    Application: After Effects (Beta) v22.0.0.21    OS: macOS v10.15.7, RAM: 64.00 GB, CPUs (logical): 16

with the latest update, impossible to add a comp to render queue not working (nb : i have a regular version of AE that runs at the same time, and a regular version of AME, but before with the same configuration, it worked perfectly)

This issue is taking very long for you guys to fix it and it's a real pain. Sorry for the constant complain but imagine my clients face when I have to ask for a mouse because my wacom is no working any more. It's constant. After several minutes working in after effects, the wacom driver kind of brakes. Actually, when I pass a wacom diagnostic tool, the software tells me that the driver is damaged. this happens always. I'm absolutely up tu date with everything. Mac M1, latest wacom driver and latest AE version.

I tried to edit an Output Module preset, but it does not stick.Tried to create a fresh one. Same problem.Editing it in the Queue doesn't stick either... 

EXR-Sequence is causing artifacts (see attached file) when an VR Chromatics Abberation Effect is applied. The error disappears, when „Falloff Invert“ is unchecked in the effect’s options.It is most noticable when the image is stacked multiple times, otherwise it is barely visible. It persists in Preview and rendered/exported. Disabling GPU-Acceleration in the Project Settings solves the problem – but makes the effect unusable.System info    Application: After Effects v18.2.1 and After Effects (Beta) v22.0.0.13     OS: macOS v11.4.0, RAM: 8.00 GB, CPUs (logical): 8, Apple M1

When I set the shot to render in AME it boots AME, but does not send the file to AME for rendering. If I manually drag N drop the file, it hangs when trying to work with the CH file. If I try to render in the que, it snags , but never at the same point on the timeline. It can go from 13% upto 90%, then hangs. I have ample memory, The only other program running tends to be PR, but it still snags even when that is turned off. If I try and use AE 2021it will render most of the time, but loses all the smart replay functions that were used in CH.There is no ERROR generated, it just hangs and stops the render. I've let it sit for hours, thinking it was still working, but nothing happens.

Today we are excited to announce the availability of AME Export of AE Compositions using Multi-Frame Rendering in the After Effects beta, available in builds 18.4x37 or newer. We strongly recommend you update to the latest Adobe Media Encoder beta but it is not required for AE MFR support.   What does AME Export of AE Compositions with MFR do? Adobe Media Encoder will now render After Effects compositions using Multi-Frame Rendering, speeding up export to formats that the native AE Render Queue does not support. Download the latest build from Creative Cloud Desktop.   You can see the AME to AE Export with MFR in action in the attached video.   Please use this forum post to discuss and provide feedback.   Thanks!

The lates BETA build shows up as Version 22.0.0 (Build 5). This seems like abig jump from 18.4.3. Or is this just BETA numbering? All the best, René 

System info    Application: After Effects (Beta) v18.4.0.32    OS: macOS v11.4.0, RAM: 16.00 GB, CPUs (logical): 8 command to paste does not work. When copying any text from other software (photoshop, word, text) the command to paste the text into after effects beta is simply not enabled.

Title says it all. The 3D-Indicator will not appear if the layer is set to be a guide layer. The layer will turn 3D, though. The UI just won’t show. After Effects (Beta) v18.4.0.32macOS 10.15.7

Can't use mocha after latest update, if I try to apply it to a video sequence it, open mocha UI it gives me the following error: Bad argument provided. My video sequence is not loaded, and I can't track anything.

How to reproduce:1)get a greenscreen footage2) track a garbage mask3) apply color range effect > key the footage4) set color range's effect mask to that mask5) duplicate layer, remove all effects and masks on a duplicate6) apply on it set channels (or set matte) pointing to the second layer using effects and masks7) Switch to solo to view that the alpha is ignored

At certain point After Effect always brake the Wacom controler to the point I have to restart the computer.It always happens.

Steps to reproduce:Open this build of After Effects on an M1 Mac Result: ... Expected: No warnings, no events. I get the same message with Premiere Pro 15.4. After the warning and quitting the process AE opens just fine. I have not tested functionality beyond adding a couple of shape layers and animating scale and position.   Dynamic-link from Premiere Pro 15.3 and 15.4 also does not work.  System info    Application: After Effects (Beta) v18.4.0.30    OS: macOS v11.4.0, RAM: 8.00 GB, CPUs (logical): 8   Dynamic Link works just fine between the current release of AE and PPro. It is just the beta versions that are broken. I suspect it has something to do with Premiere Pro Beta being a universal app (M1 compatible) and After Effects being an Intel (Rosetta) app.

Debug asset failed prompts upon application load screen.

Problem Description:If I hit shift-F5 to take a snapshot (or click the snapshot icon), AE takes about 10 seconds or more to actually take the snapshot. AE remains completely responsive during that time however. I'm using 18.4.0 (Build 24) on a very fast machine. Steps to Reproduce:1. Press shift-F5 (or shift-F6, -F7, -F8)2. Nothing happens3. Continue to use AE for a few seconds4. Press F5 to display the snapshot5. AE sounds an alert to say "there's no snapshot stored"6. Wait a few seconds longer7. Camera snapshot sound plays and a snapshot is takenExpected Result:Snapshot should be taken immediatelyAny Workarounds:Nope

Steps to reproduce:    1. ...Elipse path on shape layer 2. Add repeater 3. Add stroke after repeater4. Repeat 10 circles5. Animate scale of repeater 100 to 600%Result: ...At high percentages the stroke breaks and starts to do weird things. It works ok if the stroke is applied before the repeater but that scales the stroke and thats not really the effect I'm going for.    Expected: ...Strokes to animate normally and not black out and/or stroke in weird unpredictable ways.  System info    Application: After Effects (Beta) v18.4.0.24    OS: Windows v10.0.19043, RAM: 127.87 GB, CPUs (logical): 48