similar to: more on default values....

> Firstly, I'm one of those people who thoroughly reads through a config file > before firing up the server, so the final decision won't affect me much > from a server admin point of view. From the point of view of a listener, > I'd be happy enough for burst on connect to be the default, providing the > buffer isn't too big. I'd also like to see it be

If this isn't supported, then I apologize for the disruption, I'll just tell my customer / client / friend it's time to seriously rethink what they're trying to do. If support is possible, here's the problem: I took a running icecast.xml file from a configuration that works. It has live, backup, and listener (called /broadband) mount points. A continuously running stream

here's my icecast.xml <icecast> <limits> <clients>10</clients> <sources>2</sources> <threadpool>5</threadpool> <queue-size>102400</queue-size> <client-timeout>30</client-timeout> <header-timeout>15</header-timeout> <source-timeout>10</source-timeout> </limits> <authentication> <!--

I posted the other day with a question about a player that mysteriously quits playing the icecast stream. I believe the problem is related to the icecast stream for two reasons. 1) Because it quits on more than one different player (Winamp 5 and Foobar2000) and 2) Because I used to use shoutcast with Winamp 2 and never had this problem. Anyway, I tried to get as much information about the problem

Hi all, I have a question about the relationship between the "queue-size" and the "burst-size" <limits> parameters. Q: When a client connects is the burst-size immediately added to the queue-size? If this is the case then the slack for a 16kpbs client goes down from 50 sec (102400[queue-size] / 16kbps = 50 sec) to 18 seconds ( (102400 - 65536[burst-size]) / 16kpbs =

Hello, first of all thank you for your patience and having answered you. I tried to change port from 8000 to 8001 but nothing happened. I am using a vps server so I don?t need to open port from router. I paste here all my icecast.xml configuration file. can you please give a llok and tell me if all seems ok to you? still thank you! *** root at mail2:/etc/icecast2# nano icecast.xml GNU nano

I am using Winamp, Icecast2 Server, and Edcast. I believe I have set these up properly so that I can set up and broadcast an internet radio station. These are the links I used to help me: https://www.pcworld.com/article/190705/start_your_own_internet_radio_station_for_free.html https://www.fastserv.com/kb/article/edcast_winamp_-_easy_steps_to_streaming_to_icecast_or_shoutcast/

Good morning, On Tue, 2023-02-28 at 01:07 +0000, Coolvibes Reloaded wrote: > i'm trying to config the usr authentication > but when i goto add myself into the admin part > i get add user failed check log? > > so i did and i'm getting this > [...] > [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename > given in options for authenticator. >

Hello, in the first listen socket, I put 8001 to make a test, generally it is always set to 8000. should I change also the second listen socket? Il giorno 30/lug/2014, alle ore 22:15, Jos? Luis Artuch <artuch at speedy.com.ar> ha scritto: > El mi?, 30-07-2014 a las 21:41 +0200, Simone Dal Maso escribi?: >> Hello, >> first of all thank you for your patience and having

i'm trying to config the usr authentication but when i goto add myself into the admin part i get add user failed check log? so i did and i'm getting this [2023-02-28 00:46:16] INFO admin/admin.c Received admin command manageauth.xsl on mount "/live.mp3" [2023-02-28 00:46:16] EROR auth_htpasswd/auth_htpasswd.c No filename given in options for authenticator. [2023-02-28

I am trying to determine exactly what the difference in Burst-on-Connect is between SHOUTcast and Icecast2. There are a number of players that are having difficulty with the Icecast2 Burst-on-Connect feature. To determine where the problem might be, I tried to lower the burst-size to 32768, but doing so will not allow sources to connect to the Icecast2 server. Anyone know what accepted

I am trying to determine exactly what the difference in Burst-on-Connect is between SHOUTcast and Icecast2. There are a number of players that are having difficulty with the Icecast2 Burst-on-Connect feature. To determine where the problem might be, I tried to lower the burst-size to 32768, but doing so will not allow sources to connect to the Icecast2 server. Anyone know what accepted

Thank you for your time...we made some changes to our config file and the server doesn't want to start with the command icecast -c /path/to/icecast.xml giving the error: 'Could not create listener socket on port 8000 Server startup failed. Exiting' can you look at the config file bellow and let us know of any changes that might help. we need to be able to have 10,000 clients

Hi, I have installed the Icecast2 on my Ubuntu Linux and I was not able to figure out how I could stream static mp3 files. Can anybody help me? What should I do to do this? I put the mp3 file in the webroot and I tried to retrieve it with the " http://host:port/try.mp3" URL but I could only download it (as a whole) but not as a streamed media. Do I have to convert the mp3 to another

Can anyone explain what the fundamental difference between the Burst-on-Connect mode that Icecast2 uses versus SHOUTcast? There is a thread starting on the VLC Player list that is stating that the problems that VLC has playing Icecast2 Burst-on-Connect (default) streams is the fault of Icecast2. I don't believe this is true, as Winamp has no problem with Icecast2 streams. I'm hoping

Hi, I?ve seen that shoutCAST sends data much faster than real time when you connect (for a while I assume, otherwise you?d be travelling to the future:). That?s useful for fast buffering. With icecast I don?t get that behavior, stream downloads at real time. Is there a way to buffer data faster than real time? Maybe a ?seek? feature? I need that because I need to allocate a special large

Hi team, Please accent my apologies if this is NOT the place/distro list to be raising this. I had major dramas with the standard forum - registration and decided this may be a better route. My current instance icecast server has been built with --with-curl --with-openssl options as outlined within this post: https://weekly-geekly.github.io/articles/350236/index.html and the build version is

I am having problems getting Ices to work with ALSA. If I use arecord (arecord -D plughw:0,0 output.wav) I can record the input from my microphone into a file. The playback works perfectly. However, if I use Ices with the same values I hear nothing on the receiving end of my broadcast (although I can connect to it). In order to do a further test, I setup a <savefile> tag in my

Lol... It has started! But it appears that the username had to be 'source' as Phillppe said! Sent from my iPhone > On Oct 23, 2015, at 14:19, Alan Bowness <awi3 at live.com> wrote: > > maybe wrong english words are being used? > > I have a feeling that the default settings are at fault here, in the .xml file, there is a line that has to be uncommented so that the

-----Originalmeddelande----- Fr?n: "Per Gunnarsson" <per at 80-244-81-186.customer.t3.se> Till: per.gunnarsson at lappstockholm.se Datum: 2012-02-25 15:20 ?mne: [Icecast] Same problem as last time, with IPv6 off OK, this is my configuration file: <icecast> ? ?<limits> ? ? ? ?<clients>100</clients> ? ? ? ?<sources>2</sources> ? ? ?