search for: simensen

Beau D Simensen <simensen@halogen.org> writes: > I tried admin rehash for the first time since upgrading to 1.3.12 today. The > rehash took at least 30 seconds [If not longer -- I didn't time it very > closely] and icecast slowly snuck up to 99% CPU usage. I tried issuing the > 'alias'...

are there any decent alternatives to live audio streaming [via. soundcard] to darkice or liveice? after a few days fighting with darkice, i finally managed to bring it up only to see that it takes 55% of my cpu just to encode one 128kbps stream using libmp3lame. a similar 128kbps stream only takes up 36% cpu using liveice. maybe i have something configured wrong, but i was sortof expecting darkice

On Thu, 11 Apr 2002, Beau D. Simensen wrote: > in any event, if there are some great alternatives to liveice or darkice out > there, i'd be happy to look into them. i was extremely happy to have found > ices a few months ago. it had been there all along, just not described or > explained very well. i'm guessing the...

nope no ALSA drivers, everything is supported in the freeBSD kernel.......... <p><p>>On Tue, Apr 23, 2002 at 01:16:34AM -0400, jim wrote: >> here at wkdu.org our minds are blown trying to figure out what our >> problem is, we are using a dell optiplex gx1 with a soundblaster live >> card. we are getting a nasty hum on the line in. the thing is we plug >>

Something I'd be interested in setting up is specific passwords for each moutpoint. Maybe this functionality exists somewhere already and I just haven't found out how to activate it yet. All I've seen is one encoder password per icecast server instead of one password per moutpoint. If I've missed something, please point me in the right direction. If I haven't, may I ask if

I tried admin rehash for the first time since upgrading to 1.3.12 today. The rehash took at least 30 seconds [If not longer -- I didn't time it very closely] and icecast slowly snuck up to 99% CPU usage. I tried issuing the 'alias' command just to try and get a response from the console and that never responded. [I waited about two minutes] I had the same experience both of my

This might have been something else that changed since I've upgraded. Or maybe I simply never noticed before. If one of my sources die, the clients will eventually get bumped over to another source that hasn't died yet. I'm not sure what functionality this is called or how [or if] this can be disabled. I turned off mountpoint fallback, which I would have thought would have taken care