Questions

I think we've reached the same state as it was in CS6.Multiframe rendering for final render - GOODMultiframe for previewing during work - BAD.It seems that every time AE starts multiframe rendering it starts with launching background processes that are going to do the rendering, which is understandable, except AE does absolutely no rendering untill these bg processes start. And since it takes around 15seconds!!! to start the processes, we 're stuck waiting 15seconds every time we hit the spacebar - how do you expect people to work like that?Seriously, on many comps, 15 seconds is enough to render a good couple of frames and decide, that fixes need to be made. I remember MFR in CS6 - I often turned it off during work and turned it back on for final rendering for this very reason.It's obvious to me that the MFR should only be an addition to normal single process rendering - I need to see rendering happening whenever I press space, if that means that the bg processes will be starting for

the multi-threading behavior is great, but when I hit spacebar to start playback, the beta takes a very very long time to start doing anything compared to release version AE. Like, over 40 seconds it just sits there and doesn't start at all, even when there's a long chunk of cached green in front of the playhead. Meanwhile release version does it "now-ish".

When hitting space bar to preview it's about 50/50 wether or not it'll play the audio with the video. It always seems to play the video, but sometimes (about half the time) does not play the audio with it. 

When I import an image sequence with several non-sequential missing frames, the frame count only reflects the number of frames visible in the alert dialog, not the total number of frames missing.  In the attached, 25-27 frames are reported missing out of 30 frames truly missing. If the number displayed includes a sequential segment (i.e. 1, 3-5, 7, 9...) the resulting count is inclusive, but still not accurate (see last attachment; 30 frames were truly missing, only 29 reported.) Super minor, but just something I noticed. Same results for both Windows release and beta versions:After Effects - Version 18.4.1 (build 4) - WindowsAfter Effects (Beta) - Version 22.0.0 (build 56) - Windows

The keyboard shortcut Control Shift Y does not work when you select a solid in a composit and then try to change its properties.

I'm not sure why this isn't working in AE Beta, it's working fine for me in AE 2021, but after creating a layer, if I go to open layer settings it's grayed out. It isn't specific to any project file or anything, just in general. 

As part of AE Beta 22.0x46 and above, there are changes to the set of Output Module templates that are created and changes to the Output Module Template Defaults.   When After Effects is installed for the first time, or if you clear your preferences, the following changes will be made:   New Templates Added Two new templates have been added, High Quality and High Quality with Alpha. High Quality is based on QuickTime ProRes 422, while High Quality with Alpha is based on QuickTime ProRes 4444.    Older Templates Removed The QuickTime and AVI NTSC and PAL DV templates have been removed. The Save Current Preview template has also been removed.   New Defaults The Movie and Save Current Preview Defaults will use the new High Quality output module template. The Pre-Render and Movie Proxy Defaults will use the new High Quality with Alpha output module template.     When upgrading to a new version of After Effects with existing Output Module templ

When I press the spacebar, it takes too much time to start playing the preview, even with some frames rendered. Also, by the speed it plays, it feels like it is rendering all over again. If I turn off "Enable Multi-Fram Rendering", everything is back to normal. Version: 22.0.0.44MacOS: Big Sur 11.5

Steps to reproduce:    1. Add any footage and try and use Rotobrush. As soon as you propagate AE crashes.  Result: CrashExpected: Should work. System info    Application: After Effects (Beta) v22.0.0.35, also all builds of AE 18 and AE 17..4    OS: macOS v11.5.0, RAM: 8.00 GB, CPUs (logical): 8   I am almost certain this bug was caused by the recent OSX 11.4 to 11.5 update. I did not have any Rotobrush crash problems before I updated my OS.

After short brake on project which uses fonts Druk Web Super Italic and Druk Web Heavy Italic current Beta version reports Super font is missing and regular AE 2021 reports Heavy Italic font missing. I use both fonts (and it's in CI of my client) and about 10 days ago both versions of font were visible by both versions of AE (2021 and Beta).  As a substitution is visible [Druk] (not Web) in font combo box.  If there is a need for both problematic fonts, I can upload them, but not public visible as they are copyrighted. I reinstalled fonts, uninstalled and installed again. Tried install for my user account and for all users on computer (Win10) and it didn't helped at all. Both fonts are visible for Font Viewer and other applications.  Please help as I'm on hurry with current project time schedule and there is a lot of animations using font, not vector and any changes braks it.  Regards,Radek Sliwinski / MAD multimedia  

Hi, previewing a composition takes a long time to initiate (like 20 seconds), and even after it starts it gets stuck at the first or second frame for like another 15 seconds (showing fps:00.27/29.97 or 00.119/29.97 not real-time in the info panel) and it's not smooth at all even when scrubbing through the timeline.

There is a consistent 10 second delay between hitting play regardless of how that is done, space bar or manually with the preview panel, and even when everything is 100% RAM previewed. It also happens no matter what is it in the comp, it could even be a single solid and there will be a 10 second delay between play and actual playback.

I can't seem to copy and paste things into after effects like text etc.  I can do the opposite copy from AE into another program but not vise versa. it's a really strange issue. 

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...