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 485828 - [v4l2src] Fixates to lowest resolution on new kernels
[v4l2src] Fixates to lowest resolution on new kernels
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal normal
: 0.10.7
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 490818 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-11 19:24 UTC by Filip Palm
Modified: 2007-10-27 15:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Image taken on Ubuntu 7.10. (114.54 KB, image/jpeg)
2007-10-11 19:25 UTC, Filip Palm
Details
Image taken on 7.04. (216.54 KB, image/jpeg)
2007-10-11 19:27 UTC, Filip Palm
Details
Debug log from Ubuntu 7.04. (608.35 KB, text/plain)
2007-10-12 15:16 UTC, Filip Palm
Details
Debug log from Ubuntu 7.10. (985.39 KB, text/plain)
2007-10-12 15:17 UTC, Filip Palm
Details

Description Filip Palm 2007-10-11 19:24:52 UTC
I've upgraded my computer from Ubuntu 7.04 to 7.10 and when i run cheese i get a very bad image quality from my webcam.

This didn't happen with Ubuntu 7.04, the image quality where very good.

Other information:
Gstreamer 0.10.14 and Cheese 0.2.4
Comment 1 Filip Palm 2007-10-11 19:25:45 UTC
Created attachment 97083 [details]
Image taken on Ubuntu 7.10.
Comment 2 Filip Palm 2007-10-11 19:27:05 UTC
Created attachment 97084 [details]
Image taken on 7.04.
Comment 3 Tim-Philipp Müller 2007-10-11 19:35:47 UTC
Same versions of cheese, or different versions of cheese?
Comment 4 Filip Palm 2007-10-11 19:41:40 UTC
Same version of cheese, different version of Gstreamer.
Comment 5 Tim-Philipp Müller 2007-10-12 12:06:06 UTC
Could you run cheese like this:

 $ GST_DEBUG=*v4l*:5,GST_PADS:5,capsfilter:5  cheese  2>dbg.log

on both systems and attach the gzipped dbg.log.gz files?

Comment 6 Filip Palm 2007-10-12 15:16:33 UTC
Created attachment 97126 [details]
Debug log from Ubuntu 7.04.
Comment 7 Filip Palm 2007-10-12 15:17:01 UTC
Created attachment 97127 [details]
Debug log from Ubuntu 7.10.
Comment 8 Tim-Philipp Müller 2007-10-13 12:04:31 UTC
This is a problem with the way the caps are probed and fixated.  v4l2src in CVS (and gutsy) seems to use a new API to query the supported sizes on new kernels and falls back to another API on older kernels.  This results in the caps looking differently and fixation being done in a different way: with the old API we end up with a range for width/height, so fixation will just fixate to the biggest size, while with the new API we get a different structure in the caps for every supported size, and fixation will just pick the first structure in the caps.  Because the probing is done from smallest size to highest size this will result in the smallest resolution supported by the camera - not ideal.

This should fix it:

 2007-10-13  Tim-Philipp Müller  <tim at centricular dot net>

        * sys/v4l2/gstv4l2src.c:
        * sys/v4l2/v4l2src_calls.c:
          When probing the formats and sizes a camera supports, make
          sure the best ones (highest resolution, prefered format)
          end up at the beginning of the probed caps and the less
          desirable ones at the end.  This is important because the
          order within the caps matters for things like fixation and
          negotiation, ie. what format is chosen in the end.
          With recent kernels, the current probing code will end up
          querying the supported sizes from lowest resolution to
          highest resolution, adding them to the probed caps in that
          order, resulting to v4l2src fixating to the lowest possible
          resolution if downstream does not express a size preference.
          Also make up a somewhat random ranking of prefered output
          formats for the same reason. Fixes #485828.
Comment 9 Tim-Philipp Müller 2007-10-27 15:18:29 UTC
*** Bug 490818 has been marked as a duplicate of this bug. ***