re-listening tcpserversrc?

[fightling]

On 19.02.19 13:09, MaZderMind wrote:
> In order to be able to drop the EOS-Event you could use a Pad-Probe
> (https://gstreamer.freedesktop.org/documentation/design/probes.htm).
> See here for an example how this could be done in python:
> https://github.com/voc/voctomix/blob/master/example-scripts/gstreamer/source-nostream-music-from-folder.py#L155-L164

I do that now. With the exception that tcpserversrc.src is a static pad
and so it's easier to set up the probe.

> In
> https://github.com/voc/voctomix/blob/master/example-scripts/gstreamer/source-nostream-music-from-folder.py#L170-L172
> I stopped and restarted only a single Element of the Pipeline (here: an
> uridecodebin). The same should be possible with a tcpseversrc.

I tried that but when I try to reconnect ffmpeg via TCP I get a short
connection:

--
av_interleaved_write_frame(): Broken pipe
Error writing trailer of tcp://localhost:10000: Broken pipe
frame=    2 fps=0.0 q=-0.0 Lsize=       1kB time=00:00:00.58 bitrate=
15.7kbits/s speed=14.5x
video:6075kB audio:109kB subtitle:0kB other streams:0kB global
headers:0kB muxing overhead: unknown
Conversion failed!
--

On the gstreamer side the demux is getting crazy about the stream:

--
DEBUG TCPAVSource[cam1]: scheduling source restart and dropping EOS
DEBUG TCPAVSource[cam1]: restarting source 'cam1'
DEBUG TCPAVSource[cam1]: scheduling source restart and dropping EOS
ERROR Pipeline: Received Error-Signal on Source-Pipeline
DEBUG Pipeline: Error-Details: #9: matroska-demux.c(4383):
gst_matroska_demux_check_read_size ():
/GstPipeline:pipeline0/GstBin:TCPAVSource-cam1/GstMatroskaDemux:demux-cam1:
reading large block of size 4294967295 not supported; file might be corrupt.
--

Seems that I have to re-initialize that too.

I already tried to pass the EOS signal to inform the demux about that
the stream ends but this lead to no effect.

Do I have to create the right Bin arround tcpserversrc and demux? I'm
currently testing this but no breakthrough until now.

Reconnecting is still a problem.

-- 
regards, fightling.

fightling at elektropost.org
fightling at jabber.ccc.de
@fightling