Support for opening network streams

[addisonj]

I am curious about support for opening up a multicast and/or unicast stream for video.

Ffmpeg and others support an input of the form: udp://@239.10.0.1:4000 (multicast) or udp://@:4000 (unicast) for retrieving a stream.

Support for something like that would be awesome.

Another option would be a streaming interface, so the networking could be handled by an outside the scope of this module and also allow for other interfaces (reading from a fifo pipe or file descriptor for example)

Any thoughts?

[manast]

It is actually quite possible to add streaming support as well as other kinds of input, as it is demonstrated in this gist: https://gist.github.com/mharsch/5144208 However, I have to investigate how to integrate streams as inputs in the current API. As outputs is trivial...

[velsa]

Any updates on that ?

I would really like to use navcodec to transcode http:// input stream in real-time and stream it via nodejs to HTML5 clients in webm format.

This is currently possible with ffmpeg (i.e. launching ffmpeg binary from nodejs and streaming its output to client), but it is not a clean and smart solution.

[velsa]

I've also created an issue on peerflix repo (https://github.com/mafintosh/peerflix/issues/45) which describes the idea in more detail. Hope this can be accomplished. Thanks !

[konobi]

I'd like to +1 this.

Having navcodec support a stream interface would make a lot of stuff so much easier. Right now, I'd probably go for a wrapper library, but I really really would like to use a stream based native library.

[siuying]

Any updates on this issue?

[soyuka]

+1

If you're spawning the process (like in the gist) it should be easy to pipe to a stream shouldn't it?

[pchand89]

Hey @velsa , Even i am looking for the same solution, did you get any update on this?