Quote:
Originally Posted by ajp_anton
Yes, sorry, looks like I got the 0 and 1 wrong there.
How is 8(or higher)bit to float handled? Shouldn't it also be
0 -> .0
128 -> .5
255 -> 1.0 ?
Using "averageluma", 128 is converted to 0.501961 (128/255).
Using "yplanemax"/"-min", 128 is converted to 32896 (is this a bug? should be a float number, not a 16bit int)
Also, y=128 in 8bit -> float is different from 8bit -> 16bit -> float.
|
yes, I think there are bugs in Runtime Functions, AverageChromaU and AverageChromaV in float too