[Bug 724521] v4l2object: Inconvenient handling of V4L2_FRMSIZE_STEPWISE

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=724521
  GStreamer | gst-plugins-good | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.4.0

--- Comment #21 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2014-07-01 19:29:08 UTC ---
Pushed:

commit a016f19de8ffb758c87db46be2c636d4ac4bfa44
Author: Tim-Philipp Müller <tim at centricular.com>
Date:   Mon Jun 30 10:29:54 2014 +0100

    v4l2: fix probing and enumeration of stepwise frame sizes

    The code enumerating STEPWISE framesizes would start from
    (min_w, min_h) and then add (step_w, step_h) to get the
    next framesize. However, it should really allow any width
    from min_w to max_w with step_w and same for heights.
    Secondly, we would add and probe each individual stepped
    frame size to the caps as separate structure, which would
    lead to hundreds if not thousands of structs ending up in
    the probed caps. Use integer ranges with steps instead.

    This was particularly noticable with the Raspberry Pi Cam.

    https://bugzilla.gnome.org/show_bug.cgi?id=724521
    https://bugzilla.gnome.org/show_bug.cgi?id=732458
    https://bugzilla.gnome.org/show_bug.cgi?id=726521

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.