search for: mayfirst

...lab.com/jamie/icecream As Romain Beauxis responded to my initial email, webrtc was unsuitable and websockets was the way to go. Thanks for the help! jamie 0. http://lists.xiph.org/pipermail/icecast-dev/2013-July/002223.html -- May First/People Link Growing networks to build a just world https://mayfirst.org https://support.mayfirst.org OpenPGP Key: http://current.workingdirectory.net/pages/identity/ xmpp: jamie at mayfirst.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 858 bytes Desc: OpenPGP digital sig...

...u4FSJbOfdEHTn2YNkya0wOZM1i1XVD7x1Q> I would recommend reading over the original project's documentation, particularly its license terms and security notes, before proceeding. Brad Isbell brad at musatcha.com http://www.musatcha.com On Thu, Mar 8, 2018 at 6:49 PM, Jamie McClelland <jm at mayfirst.org> wrote: > Five years after initially posting to this list[0], I finally completed > as browser-based video source client iceast. > > The code is here: > > https://gitlab.com/jamie/icecream > > As Romain Beauxis responded to my initial email, webrtc was unsuitable &gt...

I'm following up on a thread started by Stephen a couple months ago about building a JavaScript source client using webrtc. The first step suggested was to figure out how to mux the audio and video. After I posted a feature request on the webrtc experiment js library, we seem to have a solution: https://github.com/muaz-khan/WebRTC-Experiment/issues/28#issuecomment-20791759 Based on the last

...ster/js I'm curious why encoding speed on the browser is an issue. If you are sending the data to a nodejs app on a server, why not have the nodejs app doing any additional encoding necessary? jamie -- Jamie McClelland May First/People Link Growing networks to build a just world http://www.mayfirst.org https://support.mayfirst.org OpenPGP Key: http://current.workingdirectory.net/pages/identity/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature Url : http://lists.xiph.org/p...

Hey everyone, I am new to the dev list here, but my question specific about any development towards webrtc integration. 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. sincerely, Stephen Mahood -------------- next part -------------- A non-text attachment...

...cyberunions.org> 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 u...

...but is too slow to encode :-o All in all, if we keep forging, it is very likely that once mozilla finishes implementing the web audio API, we should have a function browser source client using firefox. And Chrome when their asm.js perfs improve as well. Romain 2013/7/23 Jamie McClelland <jm at mayfirst.org>: > I'm following up on a thread started by Stephen a couple months ago about > building a JavaScript source client using webrtc. > > The first step suggested was to figure out how to mux the audio and video. > After I posted a feature request on the webrtc experiment js l...

...keep forging, it is very likely that once mozilla > finishes implementing the web audio API, we should have a function > browser source client using firefox. And Chrome when their asm.js > perfs improve as well. > > Romain > 2013/7/23 Jamie McClelland <jm at mayfirst.org <http://lists.xiph.org/mailman/listinfo/icecast-dev>>: > >/ I'm following up on a thread started by Stephen a couple months ago about > />/ building a JavaScript source client using webrtc. > />/ > />/ The first step suggested was to figure o...

...; All in all, if we keep forging, it is very likely that once mozilla > finishes implementing the web audio API, we should have a function > browser source client using firefox. And Chrome when their asm.js > perfs improve as well. > > Romain > 2013/7/23 Jamie McClelland <jm at mayfirst.org <http://lists.xiph.org/mailman/listinfo/icecast-dev>>: > >* I'm following up on a thread started by Stephen a couple months ago about*>* building a JavaScript source client using webrtc.*>**>* The first step suggested was to figure out how to mux the audio and video....