similar to: suggestion on appropriate source client

Hi, I have used the SVN icecast-2.1-trunk version in my production system at http://audioserver.nl for 2 months now without problems. The fallbacks work fine as long as you make sure that the format (sampling frequency and bitrate) of the mount and it's fallback match. I have also patched the icecast-2.1-trunk version (patch not published yet, needs work to extract) to enable fallback of

I'm looking for a way to tag my live feeds via an audio announcement every 30 minutes or so using the Linux install of Icecast. Some of the feeds I control locally, and other feeds are from remote locations - so implimenting this must be as painless as possible for each encoding location. As of now, the best way I can think of to do this is by running 2 instances of Icecast. Allowing the

Karl & All, Thanks for the replies.. It looks like there might be 1,000 ways to skin this cat. I was even looking at the LiquidSoap Harbor code as well- but only if I can run LiquidSoap as a service under CentOS. 73 Phil On Tue, 02 Nov 2010 21:15:47 +0000, Karl Heyes <karl at xiph.org> wrote: > On 02/11/10 19:35, W2LIE wrote: >> I'm looking for a way to tag my live feeds

Using latest icecast, let's assume the following hosting scenario. We have 2 mountpoints which are configured with authentication callbacks: /mount1 /mount2 Both mountpoints have configured the same fallback stream, mounted at '/fallback'. Both have fallback-override enabled, so they both can move listeners back from the fallback when they come online. Suppose that both mounts are

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

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

On Friday 18 July 2003 11:16, Ethan wrote: > Hello, I'm a long time user of Icecast. We currently run 12 streams on > Icecast 1.x (Mp3). I plan to expand this to 20 streems soon. They are all > low bitrate community service. > > Recently some friends and myself came across the thought of actually > generating our own content. Music, talk, etc. > > I've been running

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

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

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.

Each MountPoint has a different URL, but in the ways that I have described, you don't use it like that. You can have 2 or 3 MountPoints but, one you can just serve as a fallback for all 3 of them. Let's take this example for a few seconds. Say for example, if you had, "http://yourdomain.com:8000/mount1" that will just serve as the listener MountPoint. "/mount2"

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

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

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

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.

On Thu, Jul 17, 2003 at 09:55:04AM -0600, Jack Moffitt wrote: > Please speak to Ralph Giles <giles@xiph.org> about obtaining commit > access to CVS. We should check in your debian/ dir into the official > tree and that way we can be sure to sync releases. Also people using CVS > snapshots will be able to build their own debs. Well... Thanks! I've been maintaining my own

Hi there! I don't know, if there have already been such a question, so that it is... I have icecast2 and 7 livestreams on it (by some reasons 6 darkices' mp3 and 1 ices2's ogg). By the given order I need to summarize the time each mount is listened for (for example, /mount1 is being listened by 3 listeners for 3 hours, than by 2 listeners for 1 hour and then by 1 listener for 2

Hi, if i am not mistaken 2.4 has a servlet which provides json output for active mounts and stats. You can check it out at http://your host:8000/status-json.xsl Just upgrade your version and you should be fine. Hth In a search for access to various ways to interact with Icecast via Python, I ran across this: http://xiph.org/~brendan/pyshout2/pyshout2-0.0.1.tar.gz Which is now dead (404). I