From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Antonio Ospite <ao2@ao2.it>, Ran Shalit <ranshalit@gmail.com>
Cc: <linux-media@vger.kernel.org>
Subject: Re: gstreamer and v4l2
Date: Tue, 15 Mar 2016 13:05:18 +0200 [thread overview]
Message-ID: <56E7EC6E.1070102@mentor.com> (raw)
In-Reply-To: <20160315112808.8ad0c7dfb8eec41a873ec8e2@ao2.it>
On 15.03.2016 12:28, Antonio Ospite wrote:
> On Tue, 15 Mar 2016 09:10:59 +0200
> Ran Shalit <ranshalit@gmail.com> 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
prev parent reply other threads:[~2016-03-15 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 7:10 gstreamer and v4l2 Ran Shalit
2016-03-15 7:18 ` Hans Verkuil
2016-03-15 7:22 ` Ran Shalit
2016-03-15 10:28 ` Antonio Ospite
2016-03-15 11:05 ` Vladimir Zapolskiy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E7EC6E.1070102@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=ao2@ao2.it \
--cc=linux-media@vger.kernel.org \
--cc=ranshalit@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.