Re: reverse engineering pwcx

[Vojtech Pavlik]

On Sat, Aug 28, 2004 at 01:14:16PM +1000, 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.
> 
> It would appear I have found an answer to my question.  The reason 
> Philips made Nemosoft sign an NDA was not to hide proprietory 
> information from their competitors.  It was to hide the fact that they 
> were misrepresenting the resolution of their cameras to their 
> customers.  No wonder Nemosoft did not feel right about opening this 
> module even after the NDA expired, he would be telling the world their 
> dirty little secret.  Of course I'm sure this was common knowledge to 
> all those people who work in robotics and always demand an uncompressed 
> stream from the camera.

Well, it's definitely no surprise, you simply can't push the
uncompressed stream through USB1.1.

Us in robotics, we use the iBot2 from Orange Micro, which is an USB2.0
webcam working nicely with Linux at 30fps, 640x480, truecolor,
uncompressed.

So I don't think that Philips would really be able to "hide" this fact
by putting the decompressors into a binary only module - everybody knows
the compression must be lossy to allow for this high a compression
ratio.

Also, it's quite obvious that there is a big tradeoff between image
quality and algorithm complexity - it might be possible do do JPEG
compression in the webcam at full framerate and a reasonably low price,
but simpler algorithms with worse image quality still be well usable and
make the price even lower.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/