From: Yuri <yuri@rawbw.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Bugreport for libv4l: error out on webcam: error parsing JPEG header: Bogus jpeg format
Date: Mon, 19 Jul 2010 09:53:37 -0700 [thread overview]
Message-ID: <4C448311.6090704@rawbw.com> (raw)
In-Reply-To: <4C444388.9040901@redhat.com>
On 07/19/2010 05:22, Hans de Goede wrote:
> This is not really a bug in libv4l, but more of a problem with error
> tolerance in the application you are using. However many apps don't
> handle
> any kind of errors all that well. So the latest libv4l will retry (get
> a new
> frame) jpeg decompression errors a number of times.
You are right, application is quite rough and doesn't have any tolerance.
But why such bad bytes appear in the first place? I think they are sent
by the
camera deliberately to indicate something and Windows driver must be knowing
what do they mean. But libv4l just can't interpret them correctly.
Yuri
next prev parent reply other threads:[~2010-07-19 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 19:30 Bugreport for libv4l: error out on webcam: error parsing JPEG header: Bogus jpeg format Yuri
2010-07-19 12:22 ` Hans de Goede
2010-07-19 16:53 ` Yuri [this message]
2010-07-19 22:46 ` 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=4C448311.6090704@rawbw.com \
--to=yuri@rawbw.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
/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