I'm using nginx as the RTMP receiver server.īoth these apps sometimes recover from network plug pull/restore, but mostly not.Īlso, ffplay doesn't even start rtmp feeds reliably. ![]() ![]() I've recently learned that is a problem with VLC and ffmpeg (demonstrated with ffplay in my tests). It also needs to be able to survive network outages and resume the feed when the communications I was having NGINX provide 3 server outputs- live1, live2, live 3 and setting up 3 iinstances I'm having one pc produce a 3 trmp playouts via scheduled playlistĪnd these go to a PC that will take the 3 independent streams and play them to 3 independent Decklink HD-SDI channels. its not a traditional stream thing that most Only after passing this will I bother trying to get them talking to decklink.Īnyway this is off topic now for this board, so I'll see if there is anything meaningful to So as usual with these free tools I get stuck just as I think I 'm getting going. ![]() I see posts related to this but no definitive solutions.Īre fully working versions of these kept proprietary? Hmmmm. Need three concurrent inputs going to three different destinations). I'm left with no solution to receive streams and do something with them (and I Sometimes they start rolling again, sometimes not.įfplay, run from the command line won't even exit so that I could put it in a reconnect loop I was very excited to get streams displaying at willīut neither VLC nor FFPlay can reliably recover from a network error like disconnecting and Receiving streams from a playout system on Windows in formats RTMP (NGINX server) and RTP direct from IP port and just displaying in a window. However, I'm bumming on the whole concept because I've been testing VLC and FFPlay The plug in sounds like a winner compared to rebuilding VLC.
0 Comments
Leave a Reply. |