From: "Steve Simon" <plan9fans@ntlworld.nospam.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] nice hardware for a cpu server (wavelets)
Date: Sat, 7 Feb 2004 12:15:03 +0000 [thread overview]
Message-ID: <006101c3ed74$042af820$85cf6051@stevesimon> (raw)
In-Reply-To: <89850e23e6bc5a40e7960d1a8b06999e@vitanuova.com>
Mmm, difficult to explain without a piece of paper.
jpag takes DCTs of the image, quantizes the coefficenst and encodes these as
the jpeg image (roughly).
Wavelet compression (now in Jpeg2000 standard) uses an arbitary waveform
(arbitary but fixed and well known) to peform the transform the image.
The idea is that the distribution of visually important coefficents is
easier to qualify in wavelat space rather than in DCT (which is near 2D
frequency) space.
Wavelets have many interesting properties
image compression is just one application of course.
Loads more info at http://www.wavelet.org
though you may be amused to know that this points to the same machine as....
plan9.bell-labs.com; they are clever people there.
-Steve
----- Original Message -----
From: <rog@vitanuova.com>
To: <9fans@cse.psu.edu>
Sent: Friday, February 06, 2004 9:08 PM
Subject: Re: [9fans] nice hardware for a cpu server
> > DjVu on the other hand was a very nice wavelet based image system...
>
> what are wavelets?
>
>
next prev parent reply other threads:[~2004-02-07 12:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 2:20 [9fans] nice hardware for a cpu server YAMANASHI Takeshi
2004-02-03 1:46 ` andrey mirtchovski
2004-02-03 11:09 ` Charles Forsyth
2004-02-03 3:16 ` ron minnich
2004-02-03 4:18 ` Martin C.Atkins
2004-02-03 4:34 ` ron minnich
2004-02-03 4:57 ` Martin C.Atkins
2004-02-03 5:06 ` ron minnich
2004-02-03 6:35 ` Taj Khattra
2004-02-03 5:45 ` andrey mirtchovski
2004-02-03 9:45 ` Bruce Ellis
2004-02-03 15:38 ` C H Forsyth
2004-02-03 15:51 ` C H Forsyth
2004-02-04 3:53 ` Jack Johnson
2004-02-04 20:48 ` Bruce Ellis
2004-02-05 0:29 ` Charles Forsyth
2004-02-05 7:21 ` Jack Johnson
2004-02-06 1:08 ` Bruce Ellis
2004-02-06 1:23 ` Charles Forsyth
2004-02-06 2:33 ` boyd, rounin
2004-02-06 9:55 ` Jeff Sickel
2004-02-06 21:08 ` rog
2004-02-07 12:15 ` Steve Simon [this message]
2004-02-09 10:20 ` Jeff Sickel
2004-02-06 4:40 ` vdharani
2004-02-06 2:57 ` Bruce Ellis
2004-02-06 14:31 ` a
2004-02-06 20:26 ` boyd, rounin
2004-02-06 9:55 ` Caerwyn Jones
2004-02-06 13:31 ` Bruce Ellis
2004-02-06 14:57 ` a
2004-02-03 16:00 ` ron minnich
2004-02-03 3:49 ` Jack Johnson
2004-02-03 4:29 ` ron minnich
2004-02-03 4:45 ` boyd, rounin
2004-02-03 6:21 ` vdharani
2004-02-03 6:47 ` vdharani
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='006101c3ed74$042af820$85cf6051@stevesimon' \
--to=plan9fans@ntlworld.nospam.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).