Re: Javascript source client
Thomas Ruecker <[email protected]>
| Newsgroups | gmane.comp.audio.icecast.devel |
|---|---|
| Message-ID | <CAL0v=_4Hh6TdiB21wJ7cSbcPz=x-2T1EOvpd1KG=9UZqTsXEEQ@mail.gmail.com> |
Hi, On 11 May 2013 04:44, Stephen Mahood <[email protected]> wrote: > I am new to the dev list here, but my question specific about any > development towards webrtc integration. I'm currently not aware of any such development. > Let me explain, a couple colleagues and I are currently working on our > webrtc build at live.mayfirst.org site useing nodejs. We are currently > looking into seeing if there is any development of a javascript source > client? This would be used to send the webrtc room to a public broadcast > on our icecast server. That sounds interesting. Let me reflect how I understand that and to open up this topic to other parties: You want to bridge an ongoing session (akin to a audio/video conference/chat) in one direction to an Icecast server. Presumably for consumption by an wider audience (think broadcasting a panel discussion). This sounds very interesting from several perspectives. Foremost as 'how do I broadcast a radio talk show with distributed participants?' is a recurring question that we face. Also 'collaborative VJ/DJing' might fit. Also as Icecast 2.4 will support the Opus and VP8 codecs out of the box, so in many(?) / most(?) cases there would be no expensive re-encoding. In addition 2.4 will support native HTTP PUT (currently there is a quick hack 'support' in beta 3 and trunk). From my perspective your challenges will be to get the containers right. WebM for audio+video Ogg for audio Also (I'm not that familiar with webRTC) you might need to reencode to Opus and VP8 in some cases? I'm very interested in this topic. Please keep us updated. Cheers Thomas