On 15.03.2016 12:28, Antonio Ospite wrote: > On Tue, 15 Mar 2016 09:10:59 +0200 > Ran Shalit <ranshalit@xxxxxxxxx> wrote: > >> Hello, >> >> This is a bit offtopic, so I will understand if you rather not discuss that... >> >> I am trying to use gstreamer with v4l2 vivi device, >> I first check the capabilities with >> >> gst-launch-1.0 --gst-debug=v4l2src:5 v4l2src device="/dev/video0" ! >> fakesink 2>&1 >> >> and it gives many capabilities such as the following: >> >> video/x-raw-yuv, format=(string)YUY2, framerate=(fraction)[1/1000, >> 1000/1], width=(int) 640, height=(int)180, interlaced=(boolean)true >> > > A cleaner way to enumerate capabilities of a video device in GStreamer > is like that: > > gst-device-monitor-1.0 Video > > on Debian distributions gst-device-monitor-1.0 is in the > gstreamer1.0-plugins-base-apps package. No, you add some redundant GStreamer app instead of using just GStreamer framework internals, this is not a cleaner way. >> So I tried to run as following: >> >> gst-launch-0.10 v4l2src device="/dev/video0" ! >> video/x-raw,width=640,height=180,framerate=30 ! autovideosink According to the received caps use * video/x-raw-yuv * framerate=30/1 * and start from fakesink >> >> But it keeps giving me auto negotiation error -4. >> Trying to give other values did not help neither. > > BTW, the need for videoconvert is more likely because of the pixelformat > rather than the frame dimensions. > -- With best wishes, Vladimir -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
