After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 629033 - Cheese records choppy video with uvcvideo MS Lifecam vx-5000, but loopback beforehand is fine
Cheese records choppy video with uvcvideo MS Lifecam vx-5000, but loopback be...
Status: RESOLVED DUPLICATE of bug 564957
Product: cheese
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal major
: 2.32
Assigned To: Cheese Maintainer(s)
Cheese Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-09-08 07:51 UTC by roygbiver
Modified: 2011-10-26 20:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description roygbiver 2010-09-08 07:51:39 UTC 
When I set to video mode, the playback is perfect on instant loopback, but once I hit record, it chops every few seconds.  Recorded file has the chops and locks.

Not sure if this error is related.

(cheese:13813): GStreamer-WARNING **: pad source:src returned caps which are not a real subset of its template caps
libv4l2: error converting / decoding frame data: v4l-convert: error parsing JPEG header: Bogus jpeg format
xlibv4l2: error converting / decoding frame data: v4l-convert: error parsing JPEG header: Bogus jpeg format
Comment 1 Frederik Elwert 2010-09-24 09:14:59 UTC 
I can confirm this issue with an uvcvideo Logitech Webcam 9000 for Business.

I could improve this by installing guvcviewer and changing the settings to YUYV for video and PCM for audio transfer. These settings are global and also affect Cheese. With these settings, the recorded video also chops for the first few seconds, but then works smoothly afterwards.

I don’t know anything about the internals, but maybe Cheese works better when getting uncompressed input from the webcam instead of having to first decode it?
Comment 2 David King 2011-10-26 20:09:10 UTC 

*** This bug has been marked as a duplicate of bug 564957 ***