similar to: limiting sources

Hi: this changing data issue raises a problem we've hit using traditional MP3 streaming and I wondered if there were any way to overcome this, either using icecast 1 or 2. I'm involved in a project called ACB radio interactive (http://interactive.acbradio.org) which consists of a number of DJ's from all over the world taking it in turn to use a common server. We currently broadcast

I'm trying to setup Icecast so that clients can stay connected indefinately. Basically sources will connect on occasion, but may disconnect until they get instructions to connect again (think about a jukebox that does not play music until something is selected. Now add in distrubuted, thin clients and you realize why this is an important feature). According to the icecast authors, it is

I've written a few times, but haven't seen any responses, so please forgive me if this has been answered. How many max users can be served by IceCast? We can't seem to serve more than 40 users at a time and I have no idea what to do at this point. Any suggestions? This is what everything is set to: max_clients 100 max_clients_per_source 100 max_sources 5 max_admins 5 throttle 1.0

Using Icecast 1.3.12 If the Source Strea gets disconnected from Internet (i.e. OS-Crash or something) the Server dows not kick the death source stream automaticly. I have to do this via admin console then. Whats the problem? COnfig file max_clients 30 max_clients_per_source 30 max_sources 1 max_admins 3 throttle 10.0 use_meta_data 0 streamurllock 0 streamtitletemplate %s streamurl sth

hi folks, in my (unlucky) first test of ogg vs other encoders, i found a case where wma and mp3pro sound much better than ogg at 64k. can anyone suggest a setting that i haven't tried yet that can rival the wma and mp3pro samples at 64k? it's the "gravel effect" that is troublesome. the part in question is the first 15 seconds of this wave file:

Answer to your question: Live365 is strictly mp3 Much more than you wanted to know: I started using Live365 about a zillion years ago and of course it was wonderful "back in the good ole daze". After you signed up with them, you could park 365 meg of mp3s (up to 56k) and/or set up a relay (using either icecast or shoutcast) all for free. (Dirty little secret was at first, although

hello folks, i had a problem with streaming on icecast. Version 1.3.10 / shout 0.8.0 the server startet successful , and shout is eatblish an stream on localhost port 8001. if an client read the stream via winamp on a windows machine in the lan , then is there in the first 10 sec anything ok, but after this time is the permanently drops for one sec the mp3 files are in diferent bitrates , most of

Hi, This patch (against the current CVS tree) is intended to add secure configuration to icecast 'out of the box'. It adds two configuration directives, 'icecast_user' and 'chroot_dir'. These are intended to be used together to reduce the privileges icecast runs under to the minimum necessary. When this is enabled and run as root icecast will enter the specified chroot

Has anyone been succesful using live365 as a relay for icecast and getting listed in the various directories? What would be neat is having a listing in the directories that would either send the listeners straight to live365 or to a page on my web server that would redirect them to live365. Being able to support 365 listeners is a lot better than being able to support 3 or 4... I've been

this is probably caused by the lack of buffering in icecast2. Their relay client may be doing some buffering in itself, and if it's expecting for there to be buffering on the server side as well, it might exhibit a behavior you are seeing....(that also is a difference between iceast1 and icecast2 - no server-side buffering in icecast2 and there was in icecast1)... fwiw, I am trying to

I've got two quick q's about icecast. If these two q's have already been answered, could someone let me know when so I know where to look in the archives? Here's the siutation. Macamp has now gone bunk and I need to broadcast my dj show from my home to a server that has NullSoft shoutcast. The dj's normally use winamp's shoutcast plugin to broadcast to the shoutcast

I have successfully set up a IceCast server relay at live365. My stream is 64 Kbit/s. I can se my self if the stream list. And I can find my self if I search on the station name. To create a link to the station I copied the link that I got from live365, and put it in a WinAmp .pls file. My station: http://ramzeus.hn.org/radiolegion/ ~~ Patrik Lindahl

k' then. now our problem... We have (in the netherlands) a site which has the top 100 singles in Real. We have the copy bit on, still Warner wants us to only stream 30 seconds of each song. Even worse, our on demand 'radio station', which has thousands of songs on request is threatened too. Any idea how we stand? Maarten ----- Original Message ----- From: "Jack Moffitt"

Hello, we're running a radio using Icecast2 and Winamp5/Oddcast as the source. We have several DJ's who broadcast from their homes, which means that the quality of the source->server connection varies wildly. Several of our DJ's have massive problems when broadcasting to Icecast: the music constantly goes on a pause, sometimes for a second or two, sometimes for long enough

The main stream is going to a Shoutcast server via Winamp. Works fine. A Relay stream goes to Live365. Works fine. I set up a Relay under SAM to point to the Icecast server running on another box on the network. In SAMs Realy section it tells me that it's connected - and Icecast seems to be telling me the same thing. Obviously I'm missing something in the setup of IceCast - I think?

Hi All, I attempted to switch my MP3 server from Icecast 1 to Icecast 2 today. I run a Live365 station, Big Planet Radio, which simply relays my local Icecast server. My Icecast 2 error.log file shows a lot of the following messages when the Live365 server, Nanocaster 2.5.6, is connected to it: [2003-05-14 22:09:15] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error

Hi All, I attempted to switch my MP3 server from Icecast 1 to Icecast 2 today. I run a Live365 station, Big Planet Radio, which simply relays my local Icecast server. My Icecast 2 error.log file shows a lot of the following messages when the Live365 server, Nanocaster 2.5.6, is connected to it: [2003-05-14 22:09:15] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error

Another, but more recent problem, I am having is Live365. I haven't done much work with it, but can you relay to Live365 properly? They give me an ip and it works, but I don't show up in their listings, and the song title doesn't show up in the client's mp3player. (whereas if someone listens to the local broadcast they do get the song titles). Using latest, from CVS, Icecast

Asym, What streaming program are you using? I'm using icecast 1.3.10 with meta data turned on and it doesn't want to list on yp.shoutcast.com. Can you e-mail me your icecast.conf and your streaming config file via e-mail? Thanks... Louis > I saw a post a minute ago and stupidly hit the delete button instead of > reply, so no quoted response but.. You don't have to relay to

I am trying to relay a streamtuner Live365 stream across a ssh tunnel to a remote XP pc, where I would pick it up using winamp. I have a similar setup with a non-live365 stream routed using streamripper to port 9001 and this plays correctly in winamp For my Live365 stream, I have a RealVNC root session that is streaming the Live365 broadcast from streamtuner (using XMMS). I can see XMMS playing