<div dir="ltr">See the following:<div><a href="https://www.collabora.com/news-and-blog/blog/2017/11/17/ipcpipeline-splitting-a-gstreamer-pipeline-into-multiple-processes/">https://www.collabora.com/news-and-blog/blog/2017/11/17/ipcpipeline-splitting-a-gstreamer-pipeline-into-multiple-processes/</a></div><div><a href="https://gstreamer.freedesktop.org/documentation/ipcpipeline/index.html?gi-language=c">https://gstreamer.freedesktop.org/documentation/ipcpipeline/index.html?gi-language=c</a></div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Best Regards,<br>Eslam Ahmed</div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Sep 26, 2021 at 11:15 PM Marc via gstreamer-devel <<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I was wondering what is the best/efficient way to relay a stream to a different process for further processing.<br>
<br>
Say I have process a, that transcodes a stream and archives the original into a file.<br>
Say I have process b, that resizes the original stream of process a.<br>
<br>
Currently I am using this in process a<br>
t. ! queue ! tcpserversink port=4000"$CAMNR" async=0 \<br>
<br>
and this in process b<br>
tcpclientsrc port=40001 ! queue ! tsdemux<br>
<br>
<br>
I guess this is fine if you have some micro service architecture where you have to communicate via tcp. But if this all resides on the same host and networking is not necessary, is there a better way of doing this?<br>
<br>
<br>
<br>
<br>
</blockquote></div>