Multiple clients on server-rpi??

[markjerz]

Subject says it all ... i've tried to wrap the start_feed function with a bool so as not to start the spawned process a second time but I don't get any output on the second client; the first continues to work fine.

Any ideas?

start_feed() {
        if (this.isFeedStarted) {
            return;
        }

        var readStream = this.get_feed();
        this.readStream = readStream;

        readStream = readStream.pipe(new Splitter(NALseparator));
        readStream.on("data", this.broadcast);
        this.isFeedStarted = true;
    }

[131]

Multiple listener should be "easily" achivable
But you'll need to separate the input feed from the broadcast stream (using a stack/queue)
I've an alternative implementation of the server that can bring this logic somewhere, 'ill post it someday.

[radojko]

Can you post solution for multiple clients, I´m also looking for that option.

[pimterry]

+1 @131 can you post an example of this, or some more explanation of what you mean?

[adrhc]

@131
I'm interested too in a ws broadcast solution.

[adrhc]

hi, I'm trying to achive this using another web-socket server implementation (websocket-relay.js).

Basically I'm doing this:
camera -> ffmpeg (rawvideo) -> websocket-relay.js (the unchanged input) -> browser (h264-live-player's index.html changed accordingly).

I'm successfully using server-ffmpeg.js with this configuration:
var args = [
"-rtsp_transport", "tcp",
"-i", "rtsp://172.20.19.103/media/video1" ,
"-an",
'-c:v', 'copy',
'-f' ,'rawvideo',
'-'
];
and a SONY RTSP Server camera so I tried the same parameters with websocket-relay.js:
ffmpeg -rtsp_transport tcp -i "rtsp://172.20.19.103/media/video1" -pix_fmt yuv420p -an -c:v copy -f rawvideo http://127.0.0.1:8081/supersecret
but I see nothing in browser.

Any idea why?

[pimterry]

@adrhc I'm not sure exactly why what you're doing isn't working, but you might be interested in https://github.com/pimterry/raspivid-stream. I wrote this up as a solution for the original issue here generally for the raspivid case. Like the code in this repo, it creates a stream of frames, but it ensures there's only one video streaming process, and keeps track of the overall stream state it has already seen, to let it create new streams for later consumers, who can then start watching from the current live stream too.

Code is here - it works by storing the initial SPS and PPS (configuration) frames sent when the raspivid process first starts streaming, and then keeping track of the latest IDR (full non-diff) frame as the videos plays. Whenever a client joins, that client is sent those original SPS & PPS frames, followed by the latest IDR frame, and then the rest of the stream from wherever it is currently. I'm not sure exactly how that maps to your situation, but it's a good solution for anybody pulling video from raspivid, and hopefully it's helpful!

[KevinNovak]

@131 Could you post your implementation of multiple listeners?

[Richardn2002]

See here
I have written a script to enable multiple clients.
Repo set up.