Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
chrisbrearley
Engaged
chrisbrearley
Engaged
Activity
‎Sep 16, 2021
12:09 PM
24x24 pixel solid in AE 17.6. Layer bounds match the edges of the solid.
... View more
‎Sep 16, 2021
12:08 PM
Try it yourself. Make a comp, add a solid, draw a mask. Zoom in to 1600% and see if you can get your mask to match the edge.
... View more
‎Sep 16, 2021
12:07 PM
Here is the same thing in AE 17.6 - no offset. To any AE dev reading this, whatever has been done to break this, please unbreak it.
... View more
‎Sep 16, 2021
10:13 AM
Here's another example. This is a 24x24 pixel solid. No masks. Why is it offset from its layer bounds?
... View more
‎Sep 16, 2021
10:07 AM
Something is broken. Here is a 1x1 black solid. It has no position or anchor point offset. It should be fully opaque and the anchor point should be in the middle.
... View more
‎Sep 15, 2021
07:11 AM
Now only works when timelime is window is selected, not in any other window ie Comp. This is a huge bug. Correct asap please. Win 10 AE 18.4.1 *edit. A simple restart seems to have fixed it. Will keep an eye on it to see if it happens again.
... View more
‎Jul 20, 2021
02:49 AM
Anyone? This would be especially useful for painting mattes so you can actually see the bit you are wanting to mask reveal as opposed to painting on a blak and white footage window praying you've hit the right spot.
... View more
‎Jun 17, 2021
07:52 AM
Win 10, AE 17.2, AMD Ryzen Threadripper 3960X 24-Core, 128GB Ram, 2x 3080, 2TB SSD for AE Cache. My ARRI files are in the newer MXF wrappers at 4448x3096. Caching obviously helps but i can't help but wonder why they are so much slower than other RAW files. R3D are much quicker to decode for example. I'm not expecting realtime here but 2 seconds per frame on my system is painful. I've got numberous10 second sequences that are taking 8 minutes to cache each. I think I'm actaully going to render out EXRs from Resolve as it's that painful to watch it chug through. I noticed that Resolve has two options to decode ARRI RAW - Resolve's own and ARRI's. Resolve's is much quicker so I'm guessing AE uses the slower ARRI version. I think this is where the problem lies.
... View more
‎Jun 17, 2021
06:32 AM
Why is AE so painfully slow at reading ARRI RAW files? I can get realtime playback in Resolve but AE takes about 2 seconds to read one frame.. I'm not expecting Resolve type performance but this seems ridiuclous. They are impossible to work with.
... View more
‎Apr 30, 2021
05:30 AM
Interesting. I've always considered straight alphas to be far superior to premult due to less colour polution in semi-transparent pixels and there's no risk of it being matted with the wrong colour. Premult is pretty terrible when the BG is not a solid colour as well but I suppose this happens less often when coming from a CG render. It surprises me that staright is not written into the spec as an optiona at least rather than the default.
... View more
‎Apr 29, 2021
09:19 AM
Just came to find out the same thing. Why has this not been addressed yet? Seems like a simple fix. There is a caveat to the script file as well - Although the alpha is correctly being exported straight, the flag inside the file is still set to premult so any other software and indeed After Effects will interpret it incorrectly as premult when imported and needs to be manually changed.
... View more
‎Feb 25, 2021
01:56 PM
Fixed in v18 https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/42234835-dnx-export-data-flagging-bug-introduced-in-17-5-1?tracking_code=3cc02988ea9c1106c801f836d979c8c7
... View more
‎Feb 16, 2021
04:17 AM
While I'm at it, scrubbing the timeline over a clip with a speed change on it doesn't show the speed changes but instead the clip running at 100% - what's that all about?
... View more
‎Feb 16, 2021
03:40 AM
When swapping out a clip with a speed change on using alt+shft and dragging from a bin with a clip with the same duration and timecode results in the new clip being dropped in with the wrong in-out points. I often get given clean and GFX versions of an ad to cut down. I cut with the GFX version and occasionally have to do some clip speed changes to eek out a few more frames as I'm going from 23.98 to 25fps. Once I've cut the ad then I need to swap out some clips for the clean version to put my own supers on. When I do this the in-out points are wrong - the clip speed changes do not get respected.
... View more
‎Feb 03, 2021
02:56 AM
This should open up a new compostion window and lock the old one. Having done this succesfully for many years, it now doesn't. Instead in makes AE crash. Before it does the pointer changes to a camera icon. Not sure what that's all about.
... View more
‎Dec 17, 2020
03:44 AM
I have disovered the bug has appeared in 17.5.1. If you have rendered out of AE with DNx HQX or less and have not manaully changed clip attribures in Resolve to Video then what you are seeing in Resolve will be incorrect. If you used DNx 444 then you will be ok.
... View more
‎Dec 17, 2020
03:31 AM
So I've done some more investigating, importing files rendered throughout the year to find out when the issue started. It's a very recent thing and seem to have happened in the November After Effects 17.5.1 update. Looking at the update release notes they were playing about with DNx codecs Fixed an issue that caused QuickTime DNxHR files generated via Avid Media Composer's Universal Media Engine to import as audio-only. Fixed an issue that caused all-black frames when exporting a comp to QuickTime with the Avid DNxHR 444 codec with an alpha channel. Fixed an issue that caused import to fail for Quick Time ProRes files. Fixed an issue that caused garbage pixels when exporting a comp to QuickTime DNxHR 444 with uncompressed alpha. During these 'fixes' this bug has been introduced.
... View more
‎Dec 17, 2020
03:27 AM
Again. Not a colour management issue.
... View more
‎Dec 16, 2020
01:34 PM
Spot the odd one out
... View more
‎Dec 16, 2020
01:25 PM
Seriously, guys. I appreciate your input but I have been using this workflow for over 5 years. Something is wrong. Here is my Resolve window. I have rendered out a black solid from AE as DNxHR HQX 10-bit and dropped it into the timeline and moved it to the right. As you can see, what should be black is actaully grey. Data levels are set to Auto.
... View more
‎Dec 16, 2020
01:11 PM
No but even with RCM turned on the problem still persists. This is not an RCM issue, when Resolve Data levels are set to Auto it is incorrectly choosing DATA. Manually changing it to VIDEO sorts it but I shouldn't have to do this. If you are using a current version of AE to export your files I would double-check this.
... View more
‎Dec 16, 2020
11:11 AM
Further to this, MXFs created in Premiere are interprted correctly.
... View more
‎Dec 16, 2020
11:06 AM
Not quite sure when this happened but I know things used to be correct. Resolve is wrongly interpreting any DNxHD or DNxHR HQX, HQ, SQ & LB files as FULL when they should be VIDEO, resulting in washed out files. This has not always been the case. I have pulled in a DNxHD HQX created in After Effects last year and Resolve interprets this correctly as VIDEO. DNx 444 are correctly interpreted as FULL. This has probably caused us to send out potentially hundreds of TVCs with the wrong colour. Colours are correct when these files are brought back in to After Effects so the issue seems to be with how After Effects has started to flag data levels which Resolve is not picking up correctly. The fact that an older file from After Effects seems ok leads me to the believe the bug has surfaced in After Effects rather than Resolve.
... View more
‎Dec 15, 2020
06:02 AM
1 Upvote
Just got myself a new machine. New GPUs, upgraded blackmagic card. Same problem. This is clearly a software bug that effects all systems. Why is there no fix yet?
... View more
‎Oct 05, 2020
08:06 AM
I'm noticing this as well. Never used to be a problem. Scrubbing through any time re-mapped clip on the timeline shows the wrong frame. Needs a fix asap.
... View more
‎May 29, 2020
07:21 AM
Is it possible? It keeps saying my system does not support hardware acceleration for these settings. I can only get a progressive encode to work. This is slightly annoying if it can't. Some of us still work in TV and need to render versions with fields...
... View more
‎Aug 15, 2019
08:58 AM
We are seeing this in Prem 2019 outputting a stereo track to a DNxHD MOV as a stereo channel. Audio is 3db quieter. This is a massive issue. How do we get around it?
... View more
‎Jul 03, 2019
04:21 AM
Another version (16.1.2) of AE comes around and still no fix. This happens on different machines and on both Mac & Windows. PLEASE CAN WE GET A FIX ALREADY?
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices