hello, now that html5 audio becomes usable in some browsers, for example http://webaudiodemos.appspot.com/AudioRecorder/index.html ... has anybody thought about to implement a web based source client for icecast? that's for now beyond my coding skills, unfortunately... thx, uno
2014-05-03 11:14 GMT-05:00 unosonic <un at dom.de>:> > hello, > > now that html5 audio becomes usable in some browsers, for example > http://webaudiodemos.appspot.com/AudioRecorder/index.html ... > > has anybody thought about to implement a web based source client > for icecast? that's for now beyond my coding skills, unfortunately...I worked on that with Samuel last summer but the implementation(s) and API(s) across browsers were too young at that time.. Haven't checked it since then. We had a websocket-based streaming protocol supported in liquidsoap: https://github.com/webcast/webcast.js And a test client: https://github.com/webcast/webcaster that was kinda working on firefox nightly and chrome canary.. Romain
I have built a web-based source client using the Web Audio API and getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast source protocol for now, but I have the code nearly ready for the Icecast source protocol for when someone needs it. You can see a demo here: http://demo.audiopump.co:3000/ The Web Encoder is built with a jQuery Mobile UI optimized for mobile devices at the moment. It's compatible with Chrome (desktop and latest of mobile), Firefox (desktop and mobile), and Opera (desktop only). Binary web sockets are used for sending audio to the server, where it is encoded into the desired codec(s) and sent off to Icecast/SHOUTcast servers. The general idea was to make a really simple source client that could be launched with a single click (such as from a hosting provider's admin panel). The client accepts parameters on the query-string for configuring so that in a real-world environment, the user would not have to configure anything. It is also built in such a way that the UI can be thrown away, leaving the back-end code to integrate into another application. Let me know if there is interest. I can easily add the native Icecast compatibility. Brad Isbell brad at musatcha.com http://www.musatcha.com On Sat, May 3, 2014 at 11:14 AM, unosonic <un at dom.de> wrote:> > hello, > > now that html5 audio becomes usable in some browsers, for example > http://webaudiodemos.appspot.com/AudioRecorder/index.html ... > > has anybody thought about to implement a web based source client > for icecast? that's for now beyond my coding skills, unfortunately... > > thx, uno > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20140503/d6992c3e/attachment.htm>
Brad Isbell:> I have built a web-based source client using the Web Audio API and > You can see a demo here: http://demo.audiopump.co:3000/oh my, that looks great!!!> Let me know if there is interest. I can easily add the native Icecast > compatibility.definitely! i've only an icecast server available... thx, uno
On 05/03/2014 04:40 PM, Brad Isbell wrote:> I have built a web-based source client using the Web Audio API and > getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast > source protocol for now, but I have the code nearly ready for the > Icecast source protocol for when someone needs it. > > You can see a demo here: http://demo.audiopump.co:3000/That's pretty impressive.> The Web Encoder is built with a jQuery Mobile UI optimized for mobile > devices at the moment. It's compatible with Chrome (desktop and > latest of mobile), Firefox (desktop and mobile), and Opera (desktop > only). Binary web sockets are used for sending audio to the server, > where it is encoded into the desired codec(s)Out of curiosity, what are you using as the intermediate codec? I think most of those browsers support Opus (for webRTC) and it might be even possible to go directly to Icecast without the mediating server.> and sent off to Icecast/SHOUTcast servers.Please note, that we're about to release version 2.4 and will deprecate the SOURCE method in favor of plain HTTP1.1 PUT. Might want to keep that in mind. We're going to support SOURCE still for a long while, but it might be easier for future source clients to support PUT.> > The general idea was to make a really simple source client that could > be launched with a single click (such as from a hosting provider's > admin panel). The client accepts parameters on the query-string for > configuring so that in a real-world environment, the user would not > have to configure anything. It is also built in such a way that the > UI can be thrown away, leaving the back-end code to integrate into > another application.That's indeed very nice. I will have to ask a question though, will it be open source or is this a commercial solution?> Let me know if there is interest. I can easily add the native Icecast > compatibility.I think the echo on the list speaks for itself. :-) Cheers Thomas
Hi Brad, 2014-05-03 11:40 GMT-05:00 Brad Isbell <brad at musatcha.com>:> I have built a web-based source client using the Web Audio API and > getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast > source protocol for now, but I have the code nearly ready for the Icecast > source protocol for when someone needs it. > > You can see a demo here: http://demo.audiopump.co:3000/ > > The Web Encoder is built with a jQuery Mobile UI optimized for mobile > devices at the moment. It's compatible with Chrome (desktop and latest of > mobile), Firefox (desktop and mobile), and Opera (desktop only). Binary web > sockets are used for sending audio to the server, where it is encoded into > the desired codec(s) and sent off to Icecast/SHOUTcast servers. > > The general idea was to make a really simple source client that could be > launched with a single click (such as from a hosting provider's admin > panel). The client accepts parameters on the query-string for configuring > so that in a real-world environment, the user would not have to configure > anything. It is also built in such a way that the UI can be thrown away, > leaving the back-end code to integrate into another application. > > Let me know if there is interest. I can easily add the native Icecast > compatibility.That looks very promising. Do you have any code/documentation available? I'd be very curious to see how you guys work this out.. Romain
2014-05-03 18:40 GMT+02:00 Brad Isbell <brad at musatcha.com>:> The general idea was to make a really simple source client that could be > launched with a single click (such as from a hosting provider's admin > panel). The client accepts parameters on the query-string for configuring > so that in a real-world environment, the user would not have to configure > anything. It is also built in such a way that the UI can be thrown away, > leaving the back-end code to integrate into another application.Wow! That screams for integration with Icecast2 web admin panel if opensourced!! Cheers, Xabier Oneca_,,_