- Banned
- #141
konrad grant
Banned
- Joined
- Jul 24, 2016
- Messages
- 64
- Reaction score
- 0
- Points
- 0
If you want proper linear output to do these kinds of comparisons, export an EXR. The integer linear output is very conservative in how it tries to avoid producing clipped data.
Graeme
Graeme , my understanding is EXR supports 32bit integer , and 16bit half float types .. it doesn't clip..its floating point(ish)
so there is no linear "integer" output . ..and 16bit half float is very lossy ..clipped or unclipped.
i know this, because
a) ive written integer -> half float functions
b) if I convert r3d output from integers -> half floats , my inhouse compression systems ,that are already capable of producing lossless files half the size of j2k on a good day.. start doing it much more regular ..and significantly beats openEXR PIZ compression .. due to the highly wasteful/ lossy nature of the integer -> 16bit half float transformation . YUK!! .. of course , for the purpose you mention ie, testing linear output etc it may suffice ..
of course , if red ever decided to finally explain to us when our cameras are, or are not recording 12bit and 16bit raw data,..as ive politely asked for ..years.. i might consider openEXR for 12bit dervived source footage .. but alas ..
so since half floats are not suitable for 16bit integer sources IMO (unless you throw half your data away and can live with it..).. surely its better just to stay in the integer domain and clip when necessary later down the pipe for real post situations?
half float may handle the clipping better (it can after all produce files above and below traditional clip lines, so it doesn't clip ..) .. but it is not without cost .. as half floats can handle about 8192 shades at best (if normalized between -1 an 1..) .. 16bit integer is 65535 shades (just don't clip, and you're golden .. no wasteful sign bits and mantissa)
ps, redcine used to have linear as an option , but I haven't seen it there for years ? is it still there ? where did it go ?
Last edited: