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
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
