From: Vojtech Pavlik <vojtech@suse.cz>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Craig Milo Rogers <rogers@isi.edu>, QuantumG <qg@biodome.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: reverse engineering pwcx
Date: Sat, 28 Aug 2004 14:23:33 +0200 [thread overview]
Message-ID: <20040828122333.GC1841@ucw.cz> (raw)
In-Reply-To: <1093664940.8611.8.camel@krustophenia.net>
On Fri, Aug 27, 2004 at 11:49:00PM -0400, Lee Revell wrote:
> On Fri, 2004-08-27 at 23:35, Craig Milo Rogers wrote:
> > On 04.08.28, QuantumG wrote:
> > > Craig Milo Rogers wrote:
> > >
> > > > Hmmm... a poster on Slashdot claims that entropy measurements
> > > >imply that the pwcx code is interpolating rather that truly
> > > >decompressing. Again, that's integer math and table lookups.
> > > >
> > > >
> > >
> > > http://www.amazon.com/exec/obidos/tg/detail/-/B00005R098/102-7619892-0201738?v=glance
> > >
> > > claims that the Logitech Quickcam Pro 3000 is a "True 640 x 480
> > > resolution video capture" which is now clearly false.
> >
> > If the "now clearly false" is meant to be a consequence of the
> > entropy measurements poster I referred to, I wouldn't jump the gun.
> > On reflection, it's entirely natural for a decompressed stream to
> > examine less entropy than the corresponding compressed stream!
> >
>
> Please see this slashdot thread:
>
> http://linux.slashdot.org/comments.pl?sid=119578&threshold=3&mode=flat&commentsort=0&op=Change
>
> The LavaRnd guys examined the pixels on the actual CCD chip. It's
> 160x120. The 'decompression' is just interpolation.
It's hard to believe this. I'd believe it if there was supposed to be a
320x240 chip (or even more probably 384x288 (QCIF)), as those are rather
common and with proper scaling up from the Bayer RGB pattern you can do
a rather good interpolation to 640x480 or 768x576.
But 160x120 sounds pretty ridiculous. It still would be possible to
scale that to 640x480 smoothly, but the image would be obviously blurry
and just awful even with avanced Bayer-based scaling techniques.
If Philips really does that, and succeeds, then I see the reason to
protect those methods, as it would allow the competition with better
sensors to scale to even higher resolutions (heh, my iBot2 webcam would
then be a 2560x1920 camera - that's 5 megapixels!).
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-08-28 12:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 0:52 reverse engineering pwcx QuantumG
[not found] ` <20040828012055.GL24018@isi.edu>
[not found] ` <20040828014931.GM24018@isi.edu>
2004-08-28 3:14 ` QuantumG
2004-08-28 3:35 ` Craig Milo Rogers
2004-08-28 3:49 ` Lee Revell
2004-08-28 12:23 ` Vojtech Pavlik [this message]
2004-08-28 19:20 ` Chris Meadors
2004-08-28 3:57 ` QuantumG
2004-08-28 12:07 ` Vojtech Pavlik
2004-08-28 6:47 ` Clem Taylor
2004-08-28 12:23 ` Wouter Van Hemel
-- strict thread matches above, loose matches on Subject: below --
2004-08-28 16:17 Albert Cahalan
2004-08-28 16:25 ` Lee Revell
2004-08-28 16:56 ` Albert Cahalan
2004-08-28 17:11 ` Lee Revell
2004-08-28 18:05 ` Vojtech Pavlik
2004-08-28 17:53 ` Joel Jaeggli
2004-08-28 18:04 ` Lee Revell
2004-08-28 18:08 ` Lee Revell
2004-08-29 21:04 ` Helge Hafting
2004-08-30 7:42 ` Paul Jakma
2004-08-30 12:52 ` Albert Cahalan
2004-08-30 20:23 ` dulle
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=20040828122333.GC1841@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=qg@biodome.org \
--cc=rlrevell@joe-job.com \
--cc=rogers@isi.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