[gstreamer-bugs] [Bug 517203] [dshowvideosrc] creates wrong caps on the source pad (width and height range)

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=517203

  GStreamer | gst-plugins-bad | Ver: HEAD CVS




------- Comment #1 from Julien Isorce  2008-02-18 12:18 UTC -------


So I propose to define 3 more properties:
force_size (is yes, filter will use given size)
width (given frame width)
height (given frame height)

So then gst-inspect-0.10 return :
  force-size          : Use forced size
                        flags: readable, writable
                        Boolean. Default: false Current: false
  width               : Forced frame width
                        flags: readable, writable
                        Integer. Range: 80 - 1920 Default: 720 Current: 0
  height              : Forced frame height
                        flags: readable, writable
                        Integer. Range: 60 - 1080 Default: 576 Current: 0


And the command line is like this :
gst-launch-0.10 dshowvideosrc force-size=1 width = 720 height = 576 !
ffmpegcolorspace ! autovideosink
or
gst-launch-0.10 dshowvideosrc force-size=1 width = 720 height = 576 !
video/x-raw-yuv, format=(fourcc)UYVY ! ffmpegcolorspace ! autovideosink if
I want to be sure to use UYVY for example.

It is possbile to use the filter normally :
gst-launch-0.10 dshowvideosrc ! ffmpegcolorspace ! autovideosink
or
gst-launch-0.10 dshowvideosrc ! video/x-raw-yuv, format=(fourcc)UYVY,
width=320, height=240 ! ffmpegcolorspace ! autovideosink
or
gst-launch-0.10 dshowvideosrc ! video/x-raw-rgb ! ffmpegcolorspace !
autovideosink


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=517203.