|
 |
On Mon, 12 Nov 2001 12:53:58 -0600, Bob H. wrote:
> "Rune" <run### [at] mobilixnet dk> wrote in message
> news:3beffbe3@news.povray.org...
>> "Adrien Beau" wrote:
>> > Perhaps indicate here the command line switches
>> > and ini settings that allow such formats?
>>
>> Well, this is where my knowledge doesn't suffice.
>>
>> For example, to get 16 bit grayscale png I'm not sure if one has to use
>> +fn16 or if just +fn is enough when hf_gray_16 is specified in the
>> global_settings.
Yes. (hf_gray_16 forces a PNG to 16-bpp.)
> I think the confusion is because of the 16 bit hf_gray_16 being in reality a
> 24 bit image. I never understood if the PNG output was done in a different
> way from the TGA, where it might also only use 16 bits of the whole.
It is done in a different way. PNG images can be single-channel. Here's
the output from pngcheck for a POV-generated hf_gray_16 PNG:
[ron]$ ./pngcheck sig2.png
OK: sig2.png (320x240, 16-bit grayscale, non-interlaced, 83.6%).
> When I
> check for colors used I see something like a 256 color image instead, for
> both PNG and TGA.
I think that's a limitation of whatever software you're using.
> Anyway, the usual way is to use default 24 bit output, or +fn or +ft. If it
> were +fn16 you would get a 48 bit image. Which BTW is mentioned in the Doc
> under Height Field as being a better grayscale image. I've yet to see that
> to be true.
If 16-bpp PNG as an input format were working, I could demonstrate that it
is indeed true. Since it isn't, at the moment, you'll have to take my word
for it.
--
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker
Post a reply to this message
|
|
