ðòïåëôù 


  áòèé÷ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 

  óôáôøé 


  ðåòóïîáìøîïå 


  ðòïçòáííù 



ðéûéôå
ðéóøíá












     áòèé÷ :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[filmscanners] Re: 8 bit versus 16



Austin Franklin wrote:
>>Its well documented in the 3D community that having
>>24 bit colour internally in 3D processing engines
>>can result in banding in certain scenes, and thats
>>why Nvidia and ATI have developed 32 bit engines,
>>and more.
>
> That's an entirely different issue.

I don't think so. This is exactly the same problem.

When editing an image colorwise, then depending on the algoriths used,
an 8bit value per channel can easily lead to banding on some operations.
It will show up pretty clear in histograms, but might not be visible to
the viewer, depending on where it happens and the visual sensibility of
the viewer (and the monitor or whatever the outout device is).

If there is more room to work in, this banding does not happen or is
less visible. That is the advantage of working with 16bits.
Just plain old math. If you work in a small integer space some
operations will produce losses. The bigger the space the less loss you have.

If the effects of working in the wider space affect your images visibly
is something that only can be judged by looking at them and comparing
the results of working in both ranges. For some it does so drastically
for others not.

cheers
afx

--
Andreas Siegert
afx@muc.de


----------------------------------------------------------------------------------------
Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe 
filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or 
body



 




Copyright © Lexa Software, 1996-2009.