Icecast Streaming Media Server

[Anonymous]

Hello,

I've recently setup and run ices 0.4 on my FreeBSD machine that is also running the icecast2 daemon. For months I (and others) have been sourcing to this icecast2 without any problem. I have recently migrated my music collection to this server so I may setup a 24/7 stream without chewing up lots of my local bandwidth.

I setup ices fine, created a simple playlist, and successfully connected to icecast2. Everything appeared to be going well for the first few seconds, and then I started encounting rebuffering with my WinAMP client every few seconds. Several other people have reported the same. So far I've tried

Turning off reencoding.
Lowering the reencoded bitrate (64kbps).
Increasing the queue size in my icecast config.

None of these changes appeared to make a difference. Below is a copy of my ices.conf and icecast2.xml config files. Any advice/help would be appreciated!

Cheers,

ices.conf

[karlH]

rebuffering generally means that the data rate is not enough. As you have already tried, the CPU could be max'd out if reencoding or network/connection link could be max'd out or possibly even ices has problems with the file it's playing. You have to check the log to see if the latter is an issue, but you could try something like curl/wget just to see if you are getting the expected amount of data through the link.

karl.

[Anonymous]

Thanks for the tips karlH.

I forgot to mention I did check whether to see ices was consuming too much memory and/or CPU resources but neither appears to be an issue. Both icecast2 and ices processes consume less than 1% of total CPU or memory resources with people streaming.

The ices log reports no problem. Since the ices client and icecast2 daemon are hosted on the same machine I don't see how there could be an issue between those two.

I'm not sure what you're referring to with regards to using wget and curl. Are you suggesting I wget the stream for a set period of time (locally) and see if the bitrate*time calculation matches up? Would this be an accurate measure? How would I go about timing the stop of the wget?

BTW, I started of ices and it's looping at the following address:
http://radio.***.com:8000/ices-test.m3u @ 64kbps

I started up my home -> icecast server mountpoint to prove that it's not a network issue. It is encoded at a considerably higher bitrate.
http://radio.***.com:8000/thewire.m3u @ 224kbps

Any more ideas? =)

Appreciate your help.

-w

edit>
relevent processes:

wladek 22017 3.9 1.0 8108 3704 pf S+ 12:36AM 0:27.57 ./ices
wladek 22243 0.0 0.2 1508 848 pe S+ 12:45AM 0:00.01 grep ice
icedaemon 1241 0.0 1.6 10804 6160 pi- S 12:40PM 5:05.06 /usr/local/bin
/icecast -c /usr/local/etc/icecast.xml -b

load averages: 0.34, 0.18, 0.07

[Anonymous]

Resolved. This was a VPS issue, there is a client setting within the VPC that dictates how often processes may request processing fromt the CPU.

[Anonymous]

how do i configure the virtual servers configuration????
whats the setting u have to edit there
pls help noob

[Anonymous]

@xpander54

The problem was fixed by making the necessary changes to the /boot/loader.conf file:

[Anonymous]

[Anonymous]

Nope, that config code is for your vmclient on the virtual machine, it has nothing to do with icecast2. You're interested in the /boot/loader.conf file.

[Anonymous]

HEY MAN THANKS ALOT FOR THE HELP YOU THE MAN!
but
my question is
im using winamp in the virtual machine(client) to connect to the icecast host machine (server) which is in the us and i am in canada.

the server in us has a speed of 100mbps i ftp files from there to here at 700kbps.

when you are listening to the radio it rebufers or simply cuts the stream.
server is running winamp f.3 full free version and oddcast V3 to conect to icast 2x.

stream rebufers on clients machine cutting the whole stream, or simply stops playing

the conf file you talking about is in clients winamp?????

or where i cant find boot folder no place
thank you alot bro for your help

if theres anything i can do for you just say
peace