From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] PNG and APE (cntd)
Date: Fri, 28 Apr 2006 06:02:21 +1000 [thread overview]
Message-ID: <775b8d190604271302y2d7262bdo233acc444c0f75dd@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620604271226o17e6cccdm63a0794e550a39b4@mail.gmail.com>
Yes, 12 bit was added to postscript for x-rays.
brucee
On 4/28/06, Jack Johnson <knapjack@gmail.com> wrote:
> On 4/27/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> > > And, BTW, PNG allows 16-bit per colour, a 48-bit depth per pixel.
> > > Thanks to libpng, my "npng" can render these as 24-bit images.
> >
> > ``the human ear can't hear as high as that / still, it ought to please any passing bat''
>
> I used to do some image fiddling a long time ago (image prep -> TGA
> for television), and came across some info regarding medical x-ray
> photographs being stored in a 12-bit grayscale format. It's likely
> that so fine a variation is either above or right on the edge of human
> perception (given current working environments), but one
> counterargument is that maybe it's not a human looking at the data.
>
> Plus, I think 12 bits per color would be right around the limit of
> film, something like a 4000:1 contrast ratio, so depending on the
> scanner you'd likely be pushing the limits of the original medium
> anyway, "lossless" transfer from analog to digital, whether or not
> you're in a good position to make use of the data.
>
> Archaeologists have the same problem all the time, looking at data
> gathered by previous scientists and realizing the original gatherers
> didn't save enough information for the current questions, so now they
> tend to swing the opposite direction and record all the minutiae so
> that years later someone can glean new information from an old dig.
>
> One day, you may be a bat.
>
> -Jack
>
next prev parent reply other threads:[~2006-04-27 20:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 4:47 lucio
2006-04-27 6:23 ` Lluís Batlle i Rossell
2006-04-27 17:51 ` lucio
2006-04-27 18:24 ` Lluís Batlle i Rossell
2006-04-27 18:28 ` Charles Forsyth
2006-04-27 19:26 ` Jack Johnson
2006-04-27 19:58 ` Steve Simon
2006-04-27 21:13 ` Lluís Batlle i Rossell
2006-04-27 22:05 ` Charles Forsyth
2006-04-28 5:00 ` lucio
2006-04-28 18:31 ` jmk
2006-04-27 20:02 ` Bruce Ellis [this message]
2006-04-27 19:59 ` lucio
2006-04-27 6:36 ` andrey mirtchovski
2006-04-27 6:39 ` andrey mirtchovski
2006-04-27 11:43 ` Lluís Batlle
2006-04-27 11:53 ` Harri Haataja
2006-04-27 12:25 ` Russ Cox
2006-04-27 18:18 ` lucio
2006-04-27 18:27 ` andrey mirtchovski
2006-04-27 19:56 ` lucio
2006-04-27 12:25 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=775b8d190604271302y2d7262bdo233acc444c0f75dd@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).