Sorry, but I can't resist. I just read something which is rather ironicly pertinent.
I really will drop this subject in this thread after this. Your video, "Ibuki" is great!
Microsoft, it's
reported, is proud of a new image compression technology which they hope will supplant JPEG. While a couple of the aspects actually seem interesting, one which really caught my eye was that they will be able, with their new technological wonder, to, well:
[ QUOTE ]
The compression technology is also "smart"--it is possible to ... [do] such things as rotating the image without the need to decode it and subsequently encode it again
[/ QUOTE ]
Every time one "works with" a JPEG image in many ways the image is decoded, modified, then re-encoded and this causes a loss in clarity/quality. However, let me share a couple of lines from the formatted "man page" for a utility I happen to have (note the date at the bottom!):
<font class="small">Code:</font><hr /><pre>NAME
jpegtran - lossless transformation of JPEG files
SYNOPSIS
jpegtran [ options ] [ filename ]
DESCRIPTION
jpegtran performs various useful transformations of JPEG
files. It can translate the coded representation from one
variant of JPEG to another, for example from baseline JPEG
to progressive JPEG or vice versa. It can also perform
some rearrangements of the image data, for example turning
an image from landscape to portrait format by rotation.
jpegtran works by rearranging the compressed data (DCT
coefficients), without ever fully decoding the image.
Therefore, its transformations are lossless: there is no
image degradation at all, which would not be true if you
used djpeg followed by cjpeg to accomplish the same con-
version. But by the same token, jpegtran cannot perform
lossy operations such as changing the image quality.
... [skip about 180 lines of text] ...
AUTHOR
Independent JPEG Group
BUGS
Arithmetic coding is not supported for legal reasons.
The transform options can't transform odd-size images per-
fectly. Use -trim if you don't like the results without
it.
The entire image is read into memory and then written out
again, even in cases where this isn't really necessary.
Expect swapping on large images, especially when using the
more complex transform options.
3 August 1997 JPEGTRAN(1)</pre><hr />
Currently, computer time is kept track of by incrementing a 32 bit number once every second. The first second was "Thu Jan 1, 1970 00:00:01 UTC" (the "birth" of UNIX). The number will reach maximum capacity at "Tue Jan 19, 2038 03:14:07 UTC" (this will be the
real Y2K-like problem if we aren't all off of 32- bit machines by then, but we're already starting to use 64-bit computers and a 64 bit integer for counting seconds will not fill up until well after the expected lifetime of the universe; but I digress). There's a point to that bit of "trivia".
With the new MS "Vista" due out "real soon now" (a phrase repeated for, I think, about 7 years now

they will have finally incorporated some of the security features which UNIX-like systems have had for literally decades. They will also be including "user experiences" along the lines of (no doubt inspired by) those already available for unixes and Mac OS X.
You'll likely need to upgrade your hardware to use it, and the interface has changed a fair amount. Certainly the ways of doing things with the new security model will require training time.
Might I suggest you all fetch a bootable CD-ROM of Knoppix or Ubuntu
now and save yourselves a bunch of time,
money, and some effort?