public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kaiser <v4l@kaiser-linux.li>
To: leandro Costantino <lcostantino@gmail.com>
Cc: "Németh Márton" <nm127@freemail.hu>,
	"Jean-Francois Moine" <moinejf@free.fr>,
	"V4L Mailing List" <linux-media@vger.kernel.org>,
	"Hans de Goede" <hdegoede@redhat.com>
Subject: Re: image quality of Labtec Webcam 2200
Date: Sun, 13 Sep 2009 17:59:47 +0200	[thread overview]
Message-ID: <4AAD16F3.7050805@kaiser-linux.li> (raw)
In-Reply-To: <c2fe070d0909130742u2b471f7do7ff7bc8a3b6cd688@mail.gmail.com>

On 09/13/2009 04:42 PM, leandro Costantino wrote:
> Actually it based on pac7302. Pac7311/02 also has support ( since gspca1 ).
> 
> I checked some old logs of the pac, and the driver init for 7302 seems ok.
> 
> The "ff ff ff" sequence, seems to been taken in account on conversion.
> (libv4lconvert)
> 
> /* Special Pixart versions of the *_nbits functions, these remove the special
>    ff ff ff xx sequences pixart cams insert from the bitstream */
> #define pixart_fill_nbits(reservoir,nbits_in_reservoir,stream,nbits_wanted) \
> 
> This is really a tricky cam. I be back on windows to do further test.

Hey All

I thought Hans will come in, in this discussion.......

Anyway, I introduced support for the PAC7311 in gspcaV1 in 2006 [1]

Pixart is using a proprietary JEPG Format to code the image. It took me 
(and help from Jörg Schummer) more than a year to find out the basics 
to decode a frame.

They have this 0xffffffxx markers in the stream, I don't know for what 
this is good, just skip it. And they have a "MCU marker" for each MCU. 
As we know so far, this MCU marker tells what Quantization table should 
be used for decoding the MCU.

Hans did implement my findings into lib4vl and improved it :-)

So, when you get this errors, this is due to a unknown format Pixart is 
using.

I guess we should know what marker you get and how the image should look 
like.

Don't forget, this is all re-engineered -> guess work!

Thomas


[1] http://www.kaiser-linux.li/index.php?title=PAC7311

  reply	other threads:[~2009-09-13 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11  7:09 image quality of Labtec Webcam 2200 Németh Márton
2009-09-11 18:17 ` Németh Márton
2009-09-12  0:43   ` leandro Costantino
2009-09-12  1:21   ` leandro Costantino
     [not found]   ` <c2fe070d0909111741l21120025v3f45eb8566d27c7a@mail.gmail.com>
     [not found]     ` <4AAB3CB5.7090106@freemail.hu>
2009-09-12 14:51       ` leandro Costantino
2009-09-12 18:26         ` Németh Márton
2009-09-13  7:20 ` Jean-Francois Moine
2009-09-13 11:00   ` Németh Márton
2009-09-13 14:42     ` leandro Costantino
2009-09-13 15:59       ` Thomas Kaiser [this message]
2009-09-13 18:50         ` Hans de Goede
2009-09-13 18:48   ` Hans de Goede

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=4AAD16F3.7050805@kaiser-linux.li \
    --to=v4l@kaiser-linux.li \
    --cc=hdegoede@redhat.com \
    --cc=lcostantino@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    --cc=nm127@freemail.hu \
    /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