After Effects (Beta)

Steps to reproduce:    1. Import movie .mp4 for rotoscoping Result: movie is recognized as .AVI and is interpolated in rotobrush - produces green frames. (does not seem to be due to RotoBrush 2).  Expected: ... Green frames do not appear in previous versions of Ae  previous versions of Ae have different frame rate interpreted.         System info    Application: After Effects (Beta) v17.1.4.2    OS: macOS v10.13.6, RAM: 128.00 GB, CPUs (logical): 36

Working with 2 Composition Viewers isn't possible.I work on interlaced footage, so I've to pre comps the rotobrush layer in a 50 FPS comp,while maintaining my footage for final render in a 25 FPS comp.My general workflow is LOCKING the 25FPS Composition window on one screen, while the work itself is done on another screen with another Composition Viewer. so I can use it to monitor the final outcome of the rotobrush.this doesn't seem possible, the Rotobrush just freezes& the progression bar just keeps on looping,once i unlock the Composition Viewer of 25FPS and all Composition Viewer are on the working timeline everything is back and working. on a side note 🙂it's an AMAZING tool!it does MAGIC.

In the past, Markers could be accessed simply by their name. This stopped working in the Beta unfortunately.This previously worked: var sTime = marker.key("Start").time; Now I have to call the Marker by it's index: var sTime = marker.key(1).time; Is this a temporary Beta hiccup, or is this actually a new bahaviour? Thanks. System info    Application: After Effects (Beta) v17.1.2.2    OS: Windows v10.0.18363, RAM: 31.95 GB, CPUs (logical): 12

This worked in an earlier beta version but doesn't now.

I have noticed that with the latest Beta v17.1.3.18 Expression Errors are popping up randomly as I scrub through the timeline. The Expressions work in older AE versions as well as when I switch the Expression Engine to ExtendScript.AE v17.1.3.18 I can not attach an .aep because: "The attachment's ae_beta_expressionbug.aep content type (application/octet-stream) does not match its file extension and has been removed." and no .zip because the file format is forbidden.

Steps to reproduce:    1. Check out my sample project and screen recording here: https://www.dropbox.com/s/w3t4zq8jvua0nlw/Bug%20on%20After%20Effects%20Beta%2017.1.3%20%28Build%2018%29.zip?dl=0Result: When I open the sample project in latest Beta I see an expression errorSometimes turning on and off a layer or moving playhead fixes the errorWhen changing the controls on "Controller" layer all sorts of weird errors happen which were not happening in previous versionsExpected:No expression errorThese expression errors were not happening on previous versions of After Effects 2018-2020 The expression errors do not make sense - for examle "Couldn't turn into numeric value" when dividing a number property by 2. System info    Application: After Effects (Beta) v17.1.3.18    OS: macOS v10.15.5, RAM: 32.00 GB, CPUs (logical): 12 Let me know if there is anything more I can provide.  Cheers

Hi, An expression that usually worked, does not anymore Syntax Error :thisComp.layer("Dad's Birthday/Dad's Birthday.chproj").transform.zPosition - 1 => TypeError Cannot read property zPosition of undefined  If I take out the "- 1", it's accepted ?! Thank you 

Does not work with interlaced footage- QT DNX 50i.on the 25 FPS comp the brush as no problems and works great as far as i tested.but once I go to the 50 FPS comp [so I can actually render truly interlaced]the roto brush doesn't stop calculating.

The Adobe video and audio applications are updating to the CUDA 10.1 SDK on Windows. Our products currently ship with CUDA 9.2 runtime on Windows. For plugin developers, the CUDA 10.1 SDK offers overall stability improvements and enhanced support for newer CUDA cards. Users should notice no changes, but as always, we strongly recommend keeping your CUDA drivers up to date. The latest Beta builds of the Adobe video and audio applications already include the CUDA 10.1 SDK.       Note to 3rd Party plugin developers: -  As CUDA SDK 10.1 is backward compatible with 9.2 we do not expect any impact on the output frames.     However, as it is an SDK change, we recommend that you to verify your plugins with the latest runtim

Dans l'animation des calques de texte. Quand on choisit d'ajouter la propriété Inclinaison, elle s'appelle Oblique dans le montage. (Skew en anglais dans les deux cas). Dans les préférences on pointe Importer et ça devient Importation dans le panneau. (Import en anglais dans les deux cas). Dans les calques de forme quand on ajoute des tirets les premiers s'appellent Tiret et Espace puis ça devient Pointillé et Intervalle. C'est toujours Dash et Gap en anglais. Dans le menu Animation on pointe Interpolation d'images clés et la fenêtre qui s'ouvre a pour titre Interpolation d'une image clé. (Keyframe Interpolation dans les deux cas en anglais).

The current beta I have for After Effects seems to ask me to save the Untitled project even if I didn't do anything. This behavior happens when I opening a recent project. It didn't do this in the past and I'm wondering why it does it now

playback of preview freezes. The only way I have found to unfreeze it is by switching the audio hardware settings.  Something someone posted as a solution several versions ago.

Wiggle animation preset in AE BETA is "missing" it applies to the media & works but error message pops up every time. As far as i can see, all of the presets do work, but each pops the error message belowSteps to reproduce:    1. apply any of the "wiggle" FX to any object in AE Result: Doesn't work in 1 project, but works in another. Both gives the same error message as above System info    Application: After Effects (Beta) v17.1.1.9    OS: Windows v10.0.18363, RAM: 63.92 GB, CPUs (logical): 32

Create a comp, create a solid, draw a mask on the solid. you will now be in the layer panel.Click the empty space in the timeline to deselect the color solid. Move your mouse over the layer panel. the cursor will show you are going to create a new shape layer. But you are actually creating another mask layer.

Depuis quelques jours et plusieurs versions, la Beta en français ne s'ouvre plus.J'ai le message :After Effects (Beta) (avertissement) : Impossible d'accéder à la ressource'disposition_orbite_cam?ra' (type.xml) 

Est-ce que la catégorie d'effet Blur & Sharpen pourait être traduite par Flou & Netteté ?Et pas juste par Netteté. Ça doit dater de la première traduction du logiciel en 1995 😄

I updated to version 17.1.2.9 (Windows 64) and AE crashes when I import mp4 (h.264) video. It works ok with quicktime.Can someone fix this please, thanks 🙂Jaka 

Pouquoi ces changements de nom des effets Fondu et Négatif ?L'effet Fondu qui fait un fondu d'un calque vers un autre s'appelle maintenant Dégradé !?L'effet Négatif qui fait un négatif s'appelle maintenant Inverser !?Ces changements ce sont produit il y a quelques versions.J'aimerais trop savoir d'où ça vient ! 

Hello, Public Beta Users.    We recently fixed a long-standing issue in AE that would result in frames not rendering:    Switching between Composition or Footage viewers no longer requires the first viewer to finish rendering before the second starts rendering. DVAAE-4214511. The change is broad and affects all rendering and interactivity in the app. Basically any time a render took a long time, if the user switched panels (layer to comp for example), and started interacting, it would not cancel the layer panel first, resulting in no interactivity and a black frame.  The fix should reduce the illusive black frame issues we’ve seen reports of.   We’ve verified the fix in-house.  We’re now releasing the fix to Public Beta users for expanded coverage.  No need to do anything special.  Just use AE as you normally would and be on the lookout for unexpected crashes due to things that should have been rendered but were not, or panels not restarting

Hi Everyone: The following Beta applications support import of ProRes RAW footage:- After Effects (Beta) 17.1.0.33 (and later)- Media Encoder (Beta) 14.2.0.1 (and later)- Premiere Pro (Beta) 14.2.0.1 (and later)- Premiere Rush (Beta) 1.5.9.4 (and later) System Requirements for macOS:macOS Catalina 10.15 (or later)macOS Mojave 10.14.5 (or later); requires user-installation of Pro Video Formats 2.1.1 (or later) from Apple. Such Pro Video Formats are NOT licensed or supported by Adobe and are subject to Apple Terms and Conditions The Metal renderer must be selected for use in the applications (this is already the default setting):After Effects (Beta): File > Project Settings... > Video Rendering and Effects > select "Mercury GPU Acceleration (Metal)"Media Encoder (Beta): Preferences > General > Video Rendering > select Renderer: "Mercury Playback Engine GPU Acceleration (Metal) - Recommended"Premiere Pro (Beta): File < Project Settin

I have experienced many GPU driver crashes - all preceded by a black screen and followed by a loss of preview in the AE viewer - when using 3D layers (both with classic 3D and C4D renderers), AE wouldn't crash right away but if I tried saving the project or closing AE it would crash, after that a C4D graphics driver error would show up, even if I only used the classic 3D renderer. System info:Ryzen 5 2600RX 570 8gb16Gb 3000Mhz

The beta only opens in first desktop space on OS X Catelina here. When having moved the app to another space the open dialogue box opens up in desktop one and not in the space where the rest of the UI is. Solution is to go to the first desktop/space and drag it over manually. Or just use AE beta in desktop 1.  The public build respects the os settings which is nicer to work with and why I suspect that this is a bug.    

Hello, I have found a bug. Shape layers don't display on view panel, but it exists on the timeline. Also, these problems relate to solids and effects.

Hey there Adobe peeps,Alrighty my run into with ProRes RAW in AE.So in my tests, I have been mainly using ProRes RAW in Premiere. But now I am testing out a green screen shot I did with myself (gotta love Covid and no actors available, lol). And I found that when you bring in footage into AE, the RAW data doesn't stay intact. Also if I send the footage to AE via [Replace with AE Composition] it reverts to the issue. But it does keep the Lumetri information from Premiere. In Premiere, I am able to go into the lumetri color space and utilize the scopes to see that the highlights are still able to be brought back. But again, when I bring it into AE, it seems as if it was burnt into the footage. Just something to look into.I figured I would put this under BUG and PERFORMANCE for you guys review. It plays fine in After Effects. Just has this color issue. To help you guys understand what I am using, here are my specs:Camera Info : Sony FS5mkii | 12-BIT ProRes RAW rec

the application is not responding. no preview