public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Yuri <yuri@rawbw.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Bugreport for libv4l: error out on webcam: error parsing JPEG header: Bogus jpeg format
Date: Tue, 20 Jul 2010 00:46:02 +0200	[thread overview]
Message-ID: <4C44D5AA.8060600@redhat.com> (raw)
In-Reply-To: <4C448311.6090704@rawbw.com>

Hi,

On 07/19/2010 06:53 PM, Yuri wrote:
> 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.

That is not very likely as they are in the middle of the jpeg data stream
(special bytes would normally be in the header or footer of each frame).

Most likely the cause is a not 100% usb connection, or some subtle linux
driver bug causing this.

Regards,

Hans

      reply	other threads:[~2010-07-19 22:42 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
2010-07-19 22:46     ` 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=4C44D5AA.8060600@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=yuri@rawbw.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