In message ,
wrote:

Kibo informs me that stated that:

In message ,
wrote:

What format are you using to store your artificial data?

A binary file of 2-byte unsigned integers from 0 to 65535, loaded as
.raw.

Got any data on that format? You've gotten me interested enough in this
question to want to try a few experiments myself. ;)

I just wrote an applet in C that stripped the RAW data out of
uncompressed .dng files and multiplied them by 16 so that there wouldn't
be any quantization (the .dng files use the numbers 0 to 4095 in 16-bit
space) . I modified it slightly to create a string of 65536 2-byte
integers, 0 to 65535, and loaded it into PS as a 256*256 16-bit
greyscale bitmap. I placed the "Info" cursor over it, and got those
values.
--


John P Sheehy

In message ,
(Mitch Alsup) wrote:

This looks like somebody is applying the gamma correction to the RAW data
ouptut = input**2.2 / some-fixed-scaling

No; it's totally linear. 6 sequential 16-bit values become one "PS
16-bit" value (except for the highest and lowest values, which are 3 to
1).

I think its time for Adobe to realize that people have fast machines,
and that they need to stop cutting corners on quality for speed.
--


John P Sheehy

In message ,
(Mitch Alsup) wrote:

This looks like somebody is applying the gamma correction to the RAW data
ouptut = input**2.2 / some-fixed-scaling

No; it's totally linear. 6 sequential 16-bit values become one "PS
16-bit" value (except for the highest and lowest values, which are 3 to
1).

I think its time for Adobe to realize that people have fast machines,
and that they need to stop cutting corners on quality for speed.
--


John P Sheehy

what the hell are you talking about?!!! :(

what the hell are you talking about?!!! :(

"Mike Engles" wrote in message
...
SNIP
There was a discussion about this kind of thing on the scanner
group,
comp.periphs.scanner. Post your observation there. You might get a
explanation.

You probably are referring to these:
1. Chris Cox's 'explanation' of the internal format of 15bits+1:
http://groups.google.nl/groups?selm=...25ccox%40minds
pring.com&output=gplain
2. The way Photoshop converts (16-bits to 8-bits)
http://groups.google.com/groups?selm...%25ccox%40mind
spring.com&output=gplain

Bart

"Mike Engles" wrote in message
...
SNIP
There was a discussion about this kind of thing on the scanner
group,
comp.periphs.scanner. Post your observation there. You might get a
explanation.

You probably are referring to these:
1. Chris Cox's 'explanation' of the internal format of 15bits+1:
http://groups.google.nl/groups?selm=...25ccox%40minds
pring.com&output=gplain
2. The way Photoshop converts (16-bits to 8-bits)
http://groups.google.com/groups?selm...%25ccox%40mind
spring.com&output=gplain

Bart