Re: Processing WebRTC video stream at server-side

[Bryan Donnovan]

+1 for server side recording / mashup

[Amit Nishry]

This might help

http://www.smartjava.org/content/record-audio-using-webrtc-chrome-and-speech-recognition-websockets

It is only for voice.

[javier cerviño]

Hi Joao,

You could use Lynckia (www.lynckia.com), it's an open source MCU
written in C++ and Node.js. You can check the documentation and
subscribe to the mailing list to ask any question.

Cheers,
Javier.

On 15 December 2012 00:04, Joao Barbosa <joao.b...@gmail.com> wrote:
>
>
> This is exatly what i would like to know..i'm trying to build a node.js
> server that process media from PeerConnections. What can i use to do that?
> Or i only pass media streams to the without PeerConnection API?
>
> Thanks
>
> --
>
>
>

[Aleks Clark]

just an FYI for all the server-side hopefuls, from lynckia's 'documentation', it would seem processing the media stream server-side isn't currently implemented. I'm currently attempting screen + audio grabbing in a VM with the native client to see if it can be managed rapidly enough. been struggling with the native example client to achieve the same end but not luck so far.

[Joao Barbosa]

So if you try to use, for example, ErizoAPI, the video+audio aren't processed? I mean they can't be added in the server and then sended to clients that have an WebRTC implementation?

[Pedro Rodriguez]

Hi:

If by processing you mean forwarding streams, it is already in there. However, the c++ examples are quite outdated, you should look at the node addon (erizoAPI) and examples of its use (like basicServer).

You can definitely implement more complex server side processing with ErizoAPI. It implements a WebRTC stack, although it's still far from the complete standard it's compatible with Chrome. However, you will have to code your own processing in c++. The media branch of lynckia can point you in the right direction, it implements some processing and the interfaces are (hopefully) a little bit clearer.

While I agree the 'documentation' could be better, you can always ask in our mailing list. We try to keep the documentation updated for those that use the whole solution though the javascript bindings. Fiddling with the separated modules will be a lot more confusing at this stage but we are always willing to help.

Cheers

-- 

Pedro Rodriguez

--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Brandon Harvey]

I'm also interested in getting streams of video from a web client and processing them with a (Node JS) server. 

It's easy enough to create a stream on the client side, but I'm still unsure how to use the Node server as a peer.  So far I've used the webRTC.io module with limited success.  Any pointers appreciated.

Brandon