After effects 17.1.4 interpreting ProRes444 as millions of colours not trillions (mac)
After effects 17.1.4 interpreting ProRes444 as millions of colours not trillions (mac)
WHITE CHOCOLATE
shared this idea
13 comments
-
[Deleted User]
commented
Confirmed as a bug in cc2020 on windows as well. ProRes4444 works fine in cc2018. Hopefully this is fixed ASAP, probably one of the worst bugs in After Effects history. Though the exports appear to be fine, re-importing them limits the color and compresses it. Can also confirm that ProResHQ files are fine on re-import for whatever reason.
If anyone sees this, it also applies to the ProRes4444 XQ codec. The colors are wrong when imported, but it could be from the higher gamut being compressed into 8bit (millions of colors).
-
Morgan Beringer
commented
I am also having this concerning issue in AE 17.7 (Windows). It is a very large problem as rendering to Prores4444 is an integral art of my workflow. Please share if anyone discovers a fix or if fixed by Adobe!
-
Azariah Owens
commented
This bug is holding up our entire department from upgrading to build 17. Please provide an update as to when to expect a fix for this confirmed bug.
-
the dudes
commented
Was there anything announced by Adobe concerning this?
-
Felix Dames
commented
It's still not fixed in AE 17.5.1 and AE Beta 17.6.0 (Build 25) on Windows 10 v.2004 64 bit.
I can't say anything about the Mac version because I don't have one and I can't test it.
After extensive tests by looking at the actual RGB color values and not only judging by eye if there is banding or not I have to disagree with Ярослав Семенов.
This is NOT only a GUI bug at least not on windows!There is definitely a loss of color depth information!
This is a footage interpretation bug and not only a GUI bug.
There is also another footage interpretation bug for Prores4444 files when Alpha Channel is Premultiplied. After unpremultiplication (interpret footage) the unpremultiplied RGB values are wrong.
-
Ярослав Семенов
commented
Tested today 17.5.1 on Mac*.
Gradient rendered in Trillions - appearing as Millions in Project panel, but it has no banding (compared with file rendered in Millions).
So it's seems to be just GUI bug.
* Tested on Windows too, but without comparing files.
-
Gerry Rufman
commented
on project window
on the new AE 17.5
MacOS -
Andy Kidd
commented
Still happening in 17.5.0
This is NOT the case:
"- Rendering with "Millions of Colors (8bit)" Data Rate and file size is higher then with "Trillions of Colors (16bit)"! Should be the opposite!!!"What's happening is the Millions setting applies 8-bit dithering, which in turn makes the compression less efficient, and so the file size is larger.
Actually, the Trillions exports work. They look good in other applications. It's just AE that reads them in as 8-bit.
Nils.
-
John Myers commented
Confirmed on Catalina as well, latest AE.
-
I can also confirm this issue on Mac, latest AE.
-
Felix Dames
commented
I confirm this bug!
Bug exists on Wondows too!
AE 17.1.4 (Build37)ProRes 4444 has many more bugs and it's totally broken in AE 17.1.4:
- Rendering with RGB+Alpha with "Alpha Premultiplied" results in wrong Alpha Channel
- Rendering with "Millions of Colors (8bit)" Data Rate and file size is higher then with "Trillions of Colors (16bit)"! Should be the opposite!!!Adobe fix this **** I need to work!
-
Felix Dames
commented
I like to confirm this bug.
The bug exist on windows 10 64 bit too! -
Andy Kidd
commented
All imported Prores 4444 files are interpreted as 8-bit (Millions).
A gradient ramp, exported as Prores 4444, rendered at Trillions, will read correctly in Premiere, Flame, Nuke etc. But the same file in After Effects is shown as "Millions of Colors" and shows banding.
ProreHQ files do not have this issue.
After Effects 17.1.4 (build 37)
macOS Mojave 10.14.6
iMac 2017 i7
