Questions

Dans les options de rendu CINEMA 4D avec une qualité à 67 :"For highly reflective or layered opacity scene, as needed"est traduit par :"Pour les scénes d'opacité en couche ou très réfléchissantes, suivant les besoin" Il y aurait pas une meilleur traduction ?layered opacity ... opacité en couche !En tout cas c'est drôle 🙂

Hand tool keyboard shortcut works but V won't swtich to arrow from hand tool, and you cannot interract with any of the interface while the hand tool is activated.

When I try to play back or look at my project through the preview window, one random frame from the project is there and it's covering everything up. I check if I made a mistake and if there was a layer taht I'm missing, but no.

I just ran into a tiny little bug. I don't know if it's known. It concerns text layers with an effect on an area using mask and the Compositing Options. You have to look for it, it wasn't easy to find.Create a Text or Shape layer, apply an effect, apply a mask on a part of the text, activate the effect inside the mask with the Compositing Options, create a progressive outline with the Mask Feather Tool. Here we are: if you activate the 3D of the layer the progressive contour is not taken into account. With an ordinary Mask Feather property it's works.Funnier, if we do this on an Illustrator layer with Continuously Rasterize on, the option deactivates itself.

Having a 3D layer, activating the rotation tool and moving the cursor above a single axis should enable the user to rotate the layer around that axis. In the beta, currently the cursor will change to the axis below, but will translate (move) the layer, instead of rotating it. Same behaviour when having the rotation tool selected or doing a rotation override via keydown-hold W while being on another tool.→ atm, it's not possible to rotate a 3D layer in the composition around a single axis via the cursor, only the multi axis rotation works[Windows 10]

Version 451.67 the Nvida Geforce video driver Release date 07/09/2020 is incompatible with After Effects Beta. This is the latest release of the Gforce driver. I am using a 1080 founder's edition Graphics card from Asus. After Effects still run's and I have not had any problem with the beta yet. I only get a warning when I first start After Effects Beta.

When starting AE beta v 17.1.4.13 (2020-08-11) it says that my graphics card driver (NVIDIA GeForce GTX 980 Ti) is unsupported. I have installed the newest driver from Nvidia. Is this GPU no longer supported? It's from 2015, but still is good.System info    Application: After Effects (Beta) v17.1.4.13    OS: Windows v10.0.19041, RAM: 62.57 GB, CPUs (logical): 8

Trying to create timeline markers or navigate with hotkeys Not respond and nothing happens Also cant import xml System info    Application: After Effects (Beta) v17.1.4.13    OS: macOS v10.15.5, RAM: 64.00 GB, CPUs (logical): 16

So I'm trying the rotobrush 2 and I had selected my subject's hair. As the tool propagated forwards, the line I  drew over his hair started to snake along and "slide" down over the (camera) right side of his head (see video).Overall the tool seems to have improved quite a bit! Tho I do find that it struggles to catch his ears. I have tried with several clips and even tho I made an effort to be precise with the initial frame, it ignores the ears as soon as it gets the chance. Hopefully you can work on these issues to make it even more amazing. 

Adobe After Effects disables GPU acceleration and shows me the composition on a white screen. I have a Nvidia 1060 video card

Nvidia RTX 2070 Super with the latest driver (451.67) AE Beta 17.4.1.9 says it's unsupported.Edit: Attached compatability report.  Error comes up every time I launch AE beta.

Steps to reproduce:    1. Double-click on a keyframe on any property Result:  error: internal verification failure, sorry! {unexpected match name search for in group} (29::0)Expected: pop up window that shows the property field inputs (Edit Value..) System info    Application: After Effects (Beta) v17.1.4.7    OS: macOS v10.15.5, RAM: 16.00 GB, CPUs (logical): 8

If you build extensions or plugins for Premiere Pro or After Effects, please be sure to try out the latest beta build, as the CEP team is looking for feedback on CEP 10. Please comment on it in this thread so feedback can be given back to the CEP team.Here are the release notes regarding this update: CEP 10 includes a major update to CEF(Chromium Embedded Framework) from v61 to v74. More details are available at https://medium.com/adobetech/summer-cep-update-cep-10-is-coming-in-august-bcc30d22c38f   Of note for CEP 10 Issues seen on NWJS version 0.38 will also be applicable in CEP 10 For example: There are errors noticed when node module "winston" is used with any other node module which uses duplex. Workaround: In case you are using the node module "winston" please add this below script to the extension. var {Duplex} = require('stream') var {Writable} = require('stream') {   // Allow the keys array to be GC'ed.   const keys = Object.keys(Writable.prototype);   fo

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.