AW: Using the valve plugin correctly in a gstreamer pipeline
keith.thornton at zeiss.com
Thu May 4 04:54:25 UTC 2017
I gave up using valve because it blocks events as well as buffers (you won't get EOS). If you use valve you have to set drop to false at the start and then when the pipeline has prerolled you can set it to true. However I would recommend using pad probes instead. You have much finer control over your pipeline. Sebastian has written a good guide if you google dynamic pipelines.
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] Im Auftrag von xargon
Gesendet: Mittwoch, 3. Mai 2017 17:46
An: gstreamer-devel at lists.freedesktop.org
Betreff: Using the valve plugin correctly in a gstreamer pipeline
I am trying to use the `valve` plugin to basically block one branch of a `tee` in a gstreamer pipeline but this is setting my whole pipeline to `PAUSED`. So, what I am doing is basically saving H264 encoded video from my camera stream and also displaying it on the screen at the same time.
I try to use the `valve` plugin to block off a branch as follows;
However, this basically seems to set the whole pipeline to PAUSED rather than just the branch. I was still expecting to see the camera stream on the display but that is not the case.
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Using-the-valve-plugin-correctly-in-a-gstreamer-pipeline-tp4682904.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
More information about the gstreamer-devel