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 570215 - v4l2src captures non complete images off webcam
v4l2src captures non complete images off webcam
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.18
Other All
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-02 13:49 UTC by T.J.Pinkert
Modified: 2011-05-19 17:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description T.J.Pinkert 2009-02-02 13:49:46 UTC
Please describe the problem:
I have had several webcams attached to my computer using v4l2src and all of them have the same problem with gstreamer, the image is only half captured. the rest of the image is then filled with the last captured line of video.

It seems to me like a buffer issue or some initialisation issue, because at 640x480 approx. 1/4 of the image is captures correctly, at 320x240 approx. 1/2 of the image is captured and then at 160x120 the complete image is shown.

The webcams are:
- Philips PCVC740K ToUcam Pro (via pwc module)
- Logitech QuickCam Deluxe (via uvcvideo module)
- Philips SPC620 NC (via uvcvideo module)

Steps to reproduce:
I ran all of this with the following command:
$ gst-launch-0.10 v4l2src device=/dev/video2 ! video/x-raw-yuv, width=640, height=480 ! xvimagesink


Actual results:


Expected results:


Does this happen every time?
As far as I've seen this behaviour is reproducable and happens all the time.

Other information:
At least the Philips PCVC740K ToUcam Pro produces good video with the 'camstream' application. The other webcams are not producing nice video through the 'luvcview' application and seem to have the same error there. (So that makes me wonder if this is really a gstreamer bug or if it occurs somewhere in V4l2)
Comment 1 Sebastian Dröge (slomo) 2011-05-19 17:22:56 UTC
If it happens with non-gstreamer applications like you said this is a v4l2 driver bug.