dvbas.blogg.se

Ffmpeg rtsp tcp end of file
Ffmpeg rtsp tcp end of file





ffmpeg rtsp tcp end of file ffmpeg rtsp tcp end of file

OpenRTSP -4 -c | ffmpeg -re -i pipe:0 -f mjpeg pipe:1 I looked at the documentation and came up with this command: My first idea was to use openRTSP which works fine with both streams. I discovered that the camY transport is unicast but ffmpeg doesn't support this particular lower_transport as I read on ffmpeg forum. One of them(let's name it camX) kind of works with this ffmpeg command (sometimes it just stops, maybe due to packet losses): ffmpeg -rtsp_transport tcp -re -i -f mjpeg pipe:1īut the other one(camY) returns Nonmatching transport in server reply and exits. I own 2 IP cameras and both of them have rtsp server. I have a working solution for sending data to client and rendering it on canvas using websockets but it only works on one of my cameras. The idea is to run a child process in node and pipe output to node, then send the buffer to client and render it on canvas. I'm writing a web application for managing and viewing streams from ONVIF ip-cameras.







Ffmpeg rtsp tcp end of file