Decoding h264 streamed through a named pipe
arjen at moonlightmedia.nl
Tue Sep 11 11:48:48 UTC 2018
On the OS level, the pipe will be closed when the sending process is
finished. This will inevitably result in an EOF on the named pipe, causing
your second pipeline to go into EOS and stop.
I once had the same problem and ended up writing a small named pipe proxy
script in python which basically kept the second fifo open if the first one
closed. After the first one closed, the named pipe proxy script would
immediately restart reading on the named pipe again.
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
More information about the gstreamer-devel