adding pad names to pipe

[Yair Reshef]

for you example, ximagesink.sink will not work,
it will work just fine without the .sink running in gst-launch.
or use ximagesink0 (default generated name)
there is only one sink out of xvimagesink and gst-launch is aware of that.

elements have names, or get one automagicly (usually elemnt_named+0).
you can see them if you add -v verbose flag. or you can be explicit. like
in the following pad example .
https://gstreamer.freedesktop.org/documentation/tutorials/basic/gstreamer-tools.html#pads


pads have names as well, like tee0.video_0, tee0.video_1
  tee is the name of the element, and video_0 is the name of the pad.
or you can be explicit like ! tee name=mytee !
then it will be like
mytee=video_0

TIP, try to supply a generic gst-launch that uses videotestsrc or friends.
so we can run it straight without guesswork.



On Thu, Apr 23, 2020 at 5:12 AM William Johnston <wgj at cast.uark.edu> wrote:

> My understanding is that when you use gst-launch-1.0 you can give the
> element name or the element name and the pad name. For example, if I
> have an element called "ximagesink" with a pad call "sink" I can link it
> up like this: ximagesink.sink.  However, I have been having a hard time
> getting this to work.
>
> This works:
>
> gst-launch-1.0 filesrc location=/home/wgj/video/Truck.H264.ts ! tsdemux
> ! h264parse ! avdec_h264 ! videoconvert ! ximagesink
>
> But this does not:
>
> gst-launch-1.0 filesrc location=/home/wgj/video/Truck.H264.ts ! tsdemux
> ! h264parse ! avdec_h264 ! videoconvert ! ximagesink.sink
>
> it gives:
>
> WARNING: erroneous pipeline: No sink-element named "(null)" - omitting link
>
> Should it have worked or do I not understand something?
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20200423/dc72edfe/attachment-0001.htm>