From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Thomas Kaiser <linux-dvb@kaiser-linux.li>
Cc: video4linux-list@redhat.com,
"bertrik@sikken.nl >> Bertrik Sikken" <bertrik@sikken.nl>
Subject: Re: PATCH: gspca-pac207-fix-daylight-frame-decode-errors.patch
Date: Sat, 05 Jul 2008 21:56:57 +0200 [thread overview]
Message-ID: <486FD209.5020709@hhs.nl> (raw)
In-Reply-To: <486E0D71.9020106@kaiser-linux.li>
Thomas Kaiser wrote:
> Hans de Goede wrote:
>> The proper fix for this would be to lower the compression balance
>> setting when
>> in 352x288 mode. The problem with this is that when the compression
>> balance
>> gets lowered below 0x80, the pac207 starts using a different compression
>> algorithm for some lines, these lines get prefixed with a 0x2dd2 prefix
>> and currently we do not know how to decompress these lines, so for now
>> we use a minimum exposure value of 5
> Hello Hans
>
> Can you post some frames with a lower compression balance, please? Then
> other people can take a look at the decoding ;-)
>
Done, if you go here:
http://people.atrpms.net/~hdegoede/
You will see about 20 imgXX.raw's, which are pac207 compressed bayer images,
including lines starting with the 0x2dd2 prefix.
When decoded they should show a hand (mine) at the top of the screen holding a
lucky lucky comic in front of the cam.
Note this is not me being shy, but I needed a high contrast image which was
hard to compress to trigger the bug :)
Regards,
Hans
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2008-07-05 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 10:58 PATCH: gspca-pac207-fix-daylight-frame-decode-errors.patch Hans de Goede
2008-07-04 11:45 ` Thomas Kaiser
2008-07-05 19:56 ` Hans de Goede [this message]
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=486FD209.5020709@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=bertrik@sikken.nl \
--cc=linux-dvb@kaiser-linux.li \
--cc=video4linux-list@redhat.com \
/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