Questions

I can no longer import .mp4 files or use previous projects from Version 17 that use .mp4 files. The preview only shows solid green.

808r7d6

I have an issue with opening Joysticks and sliders script, it says that : Type error Null is not an object. Can't load the script....

I haven't changed the hotkeys CTRL+G is by default had to group shapes when you select one of at least one of the paths or fills or else in the "add" of the shape layer. And since a week or two this hot key doesn't work, though it is set in the keyboard manager

Hello, It would be very helpfull to have in effects list an icone for "Multi Frames Support"  (as GPU or number of bits)Many thanks, Jean

After effects beta 18.1.0.30The warning messsage in effects window is not correct for "Hue/Saturation" efffect This effect is 32bits I got a warning message about 8 bits !! (see joined screen copy)Thanks, Jean-----------------------------------------------------Nom du système d’exploitation Microsoft Windows 10 ProfessionnelVersion 10.0.19042 Build 19042Type PC à base de x64Référence (SKU) du système ASUS_MB_CNLProcesseur Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 MHz, 8 cœur(s), 16 processeur(s) logique(s)Version du BIOS/Date American Megatrends Inc. 1105, 06/06/2019Version SMBIOS 3.2Version du contrôleur embarqué 255.255Mode BIOS UEFIFabricant de la carte de base ASUSTeK COMPUTER INC.Produit de la carte de base ROG STRIX Z390-F GAMINGVersion de la carte de base Rev 1.xxRépertoire Windows C:\WINDOWSRépertoire système C:\WINDOWS\system32Périphérique de démarrage \Device\HarddiskVolume11Option régionale FranceCouche d’abstraction matérielle Version = "10.0.19041.844"Utilis

Hello! I noticed, that when i'm importing these types of filesmov ProRes 4444 10bitmov ProRes 4444 XQ 10bitmp4 HEVC 444 10bit/16bitAdobe After Effects interprets them as 8bit and shows Millions of colors instead of Trillions and unwanted banding appears.  There is no way to change import settings, but i'm definitely sure, that these files have more bit depth (checked using Nuke, ffprobe, PotPlayer).  When i'm trying to use ProRes/HEVC with 422/420 chroma subsampling - AE imports them correctly.I've attached project files and sample videos. ProRes files rendered inside After Effects (Beta) 17.1.2  10/16bit mp4 h265 with 444 chroma transcoded using ffmpeg. mp4 HEVC 422 10bit  "ffmpeg.exe" -n -i "D:\Prores\Gradient_ProRes4444.mov" -c:v libx265 -preset slow -pix_fmt yuv422p10le -q 0.18 "D:\Prores\Gradient_h265_10bit_422.mp4" mp4 HEVC 444 16bit "ffmpeg.exe" -i "D:\Prores\Gradient_ProRes4444.mov" -c:v hevc_n

I'm getting this every time I launch today's beta build and I have to press Return multiple times to make it go away. I'm not sure what script I have that is causing it. 

I get this error every time when opening a specific project. I tried creating a new project and importing the old project into it and it has the same error. The project appears to still work after hitting ok.

I am experiencing much improved render times with the beta version of multi frame rendering. Approximately 25 seconds for one of my personal projects I was testing it on, for a comp that would have taken 40-50 seconds on previous versions. However on a particular composition I'm experiencing a significant delay after clicking 'Render' in the render queue, where the render queue is frozen before the render commences. The actual render starts approx 1 min 20 secs after I click the 'render' button. Please note I'm not experiencing this same delay if I try to render the AE pulse benchmark project, which commences fairly quickly after clicking render. Further details about the comp in my personal project: It's a large project file with a lot of external media. The media was loading in from a Samsung T3 SSD.I achieved better results (i.e reduced the time it was hanging) when I 'reduced project' to just the composition in question.Another thing worth noting is that the com

Am having an error when undoing while trying to use the roto brush, when I under I often get this error, and sometimes the undo doesn't work. This is on Beta 18.1, and the same error is not occuring on the same project file in 18.0.

Good job but i think there is still much to improve because my benchmark-scene tests are not that good:(AMD 3960X (24Cores), 64 GB RAM, RTX 3090)Multiframe: 4:30 (CPU = 100% , GPU after the first 1/3 at 0%)Singleframe: 12:00 (CPU = between 5-22%)Media Encoder: 4:15 (CPU=10-30%, GPU at the beginn 10-40% after the first 1/3 at 0%)i think if this project would be GPU optimised it would be even faster in Media Encoder?.Conclusion:Im sooo glade that you realy work on Multicore support! but at the moment i see no real benefit over rendering in Media Encoder - but that could change if you optimise the Mutiframe Rendering, implement Multiframe Preview and make all your Effects Multiframe and GPU compatible! 

Please don't forget to work on a totally new GPU based and modern real-time 3D Engine for AE!We really need support of polygon 3D object (obj. fbx. abc), point clouds (.vdb), raytracing (light,shadow, reflection, AO), PBR-materials and some simple tools for deformations and 3D camera projections directly in AE.Dont try to update the old 3D Space! Rewrite it from ground up!thx,Patrick

Es sieht so aus, als hätte der Ankerpunkt beim 3D-Entwurf nicht den gleichen Wert wie im Cinema 4D Renderer.Obwohl die Werte identisch sind, springt der Ankerpunkt (In meinem Fall ein 3D Text) wenn man zwischen den Modi hin- und herschaltet.

On the info site for Multi Frame Rendering (https://helpx.adobe.com/after-effects/user-guide.html/after-effects/using/whats-new/2021-2.ug.html#multi-frame) the link to the FAQ results in a page not found: https://helpx.adobe.com/after-effects/user-guide.html/after-effects/using/multi-frame-rendering.ug.html 

I rendered an image sequence and in 2 out of 312 images, a guide layer got rendered into the final output.My guess: AE uses the cache on render time..? 😬 ---System info    Application: After Effects (Beta) v18.1.0.15    OS: Windows v10.0.19042, RAM: 63.95 GB, CPUs (logical): 24

Keyboard Shortcut: enable expressions not working

So many crashes in this update I can barely work.

I rendered a premultiplied clip with red background.After an import to After Effects and interpretation as background color red there is no effect to show it correctly.Since CC 2019 the interpretation of the background color has no effect.

Composition view shows error when zoom is not standard (see Screenshot)

Hello everybody!  I have noticed, that in After Effects 17.2 and later, the program is very often crashing when writing an expression in the "Source Text" property. Usually, while working on it, it works fine, and nothing happens. The crashing starts when I want to re-open the project after closing it (Zanzibar-2 Error). I have tested it on many projects, 2 machines, and with all the versions of AE 17.2+. The crashing always happens. I need to open the project with AE 17.1 and untick all Source text expressions to be able to open it again in later versions. I have tested it on macOS Catalina and macOS Big Sur. I believe the problem is very critical because I am practically unable to write expressions for the Source Text. Does anybody know how to solve this issue?

The newest BETA build 18.0.0.21 does not launch on my system. It is just hanging and also creates a crash report. Please find the report attached.Sytem specs: MacBook Pro (15 Inch, 2018)2,9 GHz Intel Core i932 GB 2400 MHz DDR4Radeon Pro 560X 4096 MBIntel UHD Graphics 630 1536 MBMacOS Catalina 10.15.7

v18.0.0.29 | Windows 10:The effect shows up, starts, and the process stripes and AE freeze right away.10 minutes later, the error pops:After Effects (Beta) error: Could not launch Adobe Analysis Server. (515) ( 25 :: 101 ) In v17.7.0.45 the process stripes do stop moving as well, but the tracker does finish 2 minutes later.

HiyaWhen do you expect to see a beta version of After Effects native on Apple M1?

Trashcan Mac running 11.2.1.I've having really spotty luck with dropdown option not wanting to open when using a non-default workspace.    ie Text option, puppet pin options, etc in the toolbar but also in some scripts, Ease and Wizz, PT Auto Express, etc.  Sometimes it's works without a problem, I open the app again and it doesn't.  They seem to work correctly using a default space.