Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

After Effects CS4 color dept 8, 16 or 32 bit?

A

Alex De Vivo

Well-known member
Joined
Jul 19, 2009
Messages
59
Reaction score
0
Points
0
Someone can tell me wich setting I should use in After Effects and whhy? Thx!
 
Well, that depends. One factor to consider is whether the effects you'll be using are supported in 32bit or not. Some are not.
 
HOW to check the effects really apply to R3D in 32 bit project?
I have a R3D footages which contain some overbright highlight. I apply the exposure effects, lower the exposure value, the highlight looks "grey", looks like in 8bit mode.
While I use other HDR footages to do the same test, the result is different.

R3D RAW doesn't mean it's HDR footages? Maybe I have misunderstanding?
 
overbrights...

overbrights...

chunchun said:
HOW to check the effects really apply to R3D in 32 bit project?
Click to expand...

hmm... well, only 32bit float supports overbright values. Try this. Add levels, limit input interval to say 0 to 50% from original 0 to 100. Then add another levels effect, this time enter *output* range 0 to 50%.

You should get picture identical to original, when effects are ON - check by turning on/off. That means after 1st effect there appear many overbrights out of range, which are moved back by the 2nd effect. In integer mode, everything out of interval crops to saturation, which can't be fixed by the 2nd effect. In float, however, that shall not be the case.

Then Your effects may be badly coded causing some cropping, too, clipping overbrights. Ensure btw they support float 32bit, no yellow warning sign shown in effects panel where the effect's controls are.
 
hdr..

hdr..

chunchun said:
R3D RAW doesn't mean it's HDR footages? Maybe I have misunderstanding?
Click to expand...
what HDR is.. actually a file with high bit depth storing many f-stops at once (eg OpenEXR I guess). RED certainly isn't HDR camera, can store say 9-10fstops, the same as any DSLR camera and my canon certainly isn't said to be HDR. Typical HDR footage stores more f-stops than that I guess.

On the other hand, R3D has 12bit precision, which certainly isn't bad, better than jpeg and most other formats. So we may probably say r3d isn't HDR, but it also isn't standard dynamic range. You need more bits to store these very bright areas without clipping, that's why 12bit is better than most usual 8bit.

RAW means something completely else, it doesn't store data in RGB format, rather direct chip readout. Read elsewhere on this, Bayer pattern CMOS in wikipedia etc.
 
Thanks Stepan Kment.
How about cineon / dpx ? So we can't call it HDR too ?
 
Why wouldn't you always want to use 32 bit depth, since it allows smoothest color gradient?

Also, if R3D is by nature 12 bit depth, then does it matter go to from 16bit to 32bit?
 
8, 16, 32 bit ...
?? don't you need to export/render to a 16 bit codec to really get the 16bits ?
from my experience with AE = very few (QT codec's are above 8bit )...
so far microcosm is 16bit per channel and does work in AE as 16bits ..however when microcosm is used in most other apps you end up with a 8bit file ...
sheer codec has some 10bit but doesn't mean AE can render out to 10bit .. i've tried rendering out to Sheer 10bit RGB QT and it ends up 8bit .. i can render out to sheer YUV 10bit 4444 QT ... cannot render out to any of blackMagic 10bit QT codec's ...
now i assume when you use 32bit float it processes all the data in 32bit and then fits all the data back into the 8 or 10 bit codec's range ?
 
You must log in or register to reply here.
Back
Top