Dear Moritz, I don't mean to be too picky about your choice of words, but you are > not telling us what you are trying to achieve, but only what you are > actually trying. ;-) >
I am not really sure what you are referring to :) I am trying to copy the stream and prepare it for a different transport... one push one pull one reliable one unreliable, one connectionless one connection oriented :) But I am open to discuss specifics. So you're trying to output both to udp and to a pipe, which goes to > netcat? > True. Thanks for providing a tip. Actually I am not sure how I would incorporate listem 1 into a tee muxer and I would appreciate your help. In regards to the tee muxer I could only think of "tcp://ip:port?listen " syntax. Capital L is listen closely :) - or re-listen on socket close. Does listen 1 switch provides the same behavior ? re-listen on socket close ? timeouts etc... What if I shortly lose connectivity and I want it reestablished ? I am also not aware of nc64 buffering mechanisms so eventually it might or might not work. Indeed I am trying/testing EX. stransmit was not performing well in my case over unreliable link with hevc-mpegts. Rather I had to shape the stream and go with tcp. I could not try rtp_mpegts/rtsp_transport tcp/prompeg features as I am not aware of software player being able to listen for columns and rows checksum on two different ports.... I was looking for elecard... (please suggest) and just a few days ago there was an email about missing metadata support in rtp_mpetgts muxer.... Regards. Dragan On Sun, Jul 15, 2018 at 10:25 PM, Moritz Barsnick <[email protected]> wrote: > On Sun, Jul 15, 2018 at 21:46:58 +0200, Dragan Randjelovic wrote: > > I am trying to achieve the following under windows and I am wondering > what > > would be the right syntax for it, > > while explicitly I do not want to invoke another ffmpeg process. > > > > -f tee "[onfail=ignore][f=mpegts] pipe:1>nc64 -L -p > > 1234|[f=mpegts]udp://IP:1234/" > > I don't mean to be too picky about your choice of words, but you are > not telling us what you are trying to achieve, but only what you are > actually trying. ;-) > > So you're trying to output both to udp and to a pipe, which goes to > netcat? > > The nc call needs to be outside the ffmpeg command, receiving its data > from the pipe. You would attach that on the command line as > | nc64 -L -p 1234 > (a pipe _after_ the ffmpeg command, which picks up its stdout). > > Note the '|'. The '>' you used is an operator for redirecting to files. > The redirection also shouldn't be part of ffmpeg's muxer command. > > BTW, ffmpeg can also listen on a TCP port, as you're doing with netcat: > $ ffmpeg [...] -listen 1 -f mpegts tcp://localhost:1234 > Don't ask me how to combine that into the tee muxer's syntax, I'm sure > you're up to that task already. :-) > > Cheers, > Moritz > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
