similar to: html5/js source client?

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.

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

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

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

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 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

Thanks everyone! I will answer your questions regarding the AudioPump Web Encoder (http://demo.audiopump.co:3000/): *> Can you please explain the process exactly? what is the encoding server?* There is a server built on Node.js that receives audio data, control data, and metadata from the client over a binary websocket. All of these are multiplexed down the same connection. When the server

Thanks for this information, but the two connections do not die out when using my player in the Android browser. In fact they even stay when the Audio.src is set to some invalid string. You can observe this here: http://concertzender.nl/wp-content/themes/cz-theme/App/test/ , by clicking one of the large icons - and then monitor the corresponding stream here: http://streams.greenhost.nl:8080/

i was wandering if anyone could give me a free mountpoint to set up my little station for streaming? i will be streaming at 32 KBPS .AAC thanks Timothy Your friend in the music industry follow me on twitter @timothyclark13 to check out music, photos, videos, press, show dates, and more go to http://www.reverbnation.com/timothyclark13 feel free to give me a call at 7244011224 note, if

Dear all, The problem I am facing, is that one of my clients is concerned about data usage. My client monitors the current number of listeners in the Mount Point list streams.greenhost.nl:8080. The case is, when I start a stream from an HTML app on an Android device, I can see two listeners being added to "Current Listeners". This peculiar behaviour only occurs on Android, not on

I’m setting up my system on a Mac, and have successfully gotten Ladiocast to feed Icecast and can access it on my server Mac at localhost:8000/stream. If I try to access it at the IP of the Mac at 192.168.0.5:8000 or port forwarded from the internet, I CAN successfully access the admin page. However, if I try to access the stream from either the local IP or port forwarded from the internet, I

html5/js source client? (Xabier Oneca -- xOneca) 2014-05-04 21:00 GMT+02:00 <icecast-request at xiph.org>: > Send Icecast mailing list submissions to > icecast at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xiph.org/mailman/listinfo/icecast > or, via email, send a message with subject or body 'help' to

It's behaving as it is meant to: if a listen client gets too far behind, Icecast2 server is kicking them off. error.log says, "INFO source/source.c Client 120 (xxx.xxx.xxx.xxx) has fallen too far behind, removing" I don't see a setting in icecast.xml that sets the value for "too far behind". I'm guessing it's related to <queue-size>. I wish Icecast

Thanks, Brad -- I first turned to VLC but my stream-client device is a Raspberry Pi 3, and there doesn't seem to be a build for the device. That said, I just stumbled across mpg123, a command-line mp3/stream player that has audio buffer and timeout setting which so far looks quite robust. For Icecast2 content, when Icecast kicks a client off for being "too far behind" -- what

Hello! I'm having trouble embedding my url-authenticated stream on my website on certain browsers. I'm hoping someone can offer some advice. My site offers a subscription to the stream where the username and password are system-generated and unique to the subscriber. The system-generated password is stored in the database and passed to the page based on which subscriber is logged in.

I looked at these requests and started trying to interpret the data of the header and the stream. I receive a header, and even when I added the parameter to the request to try and get meta-data, it seems that it is not being included. Namely, the number that is supposed to tell the distance between each meta-data section that is sent in the stream. I couldn't figure out the config setting

The server doesn't control the rate, the source does. Provided you aren't getting corrupt stream data (and it doesn't sound like you are), you don't have a server bug in this case. At a basic level, the server level takes the data that comes in from the source, buffers it, and sends it right back out the door at the rate at which it came in. It isn't entirely clear to me

Hi Thomas, > I wrote solid IPR evaluation for a reason. It might be helpful to ask bitmovin as a starting point, they have released the reference code under LGPL: http://www.bitmovin.net/libdash.html The LGPL preamble says: "we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license."

Logs indicate everything's running correctly, my player says I'm connected, and the Web page for the server says it's playing files, but there's no audio. Strange. Any thoughts? Did I possibly convert the MP3's to Ogg Vorbis incorrectly?

Hi all. I?m not sure f this is the correct list to talk about this here but if not please forgive me. but anyways, I was wondering how you would go about configuring ices? I have tried writing my own .xml file but got errors like parsing errors. and I can?t find the examples any where. I?ve looked in my root directory on my server and the way I?ve installed ices is by apt-get. I?m running a VPS

My icecast https stream (https://vertenradio.com:8443/stream) does not work on a Sonos ONE player. It might have something to do with the ssl handshake. >From the developer page from sonos i found this: Some common reasons for SSL handshake failures include: ? Expired certificate: Every certificate has a validity window before it expires. You need to present Sonos with unexpired