similar to: Re: keeping liveice running

I'd love to take a look at this script, and, more than likely, I'm not the only one :) Please post an example. > Liveice definitely needs a keepalive script of some kind. It's tricky, > though - since it can lose connection to the server & stop streaming, but > continue to run. The only truly reliable keepalive I've used polls the > server to see if it says the

> I'd love to take a look at this script, and, more than likely, I'm not > the only one :) > > Please post an example. > > OK - This is a quick & dirty hack - I'm sure there are several more elegant solutions... But it works. NOTE: this is designed for a Shoutcast server. You'd need to change the check= lines to work with Icecast. Couldn't find an

running: latest CVS of icecast-1.3.11, liveice, and lame. i initially launch the server with the following shell script: #!/bin/sh /usr/local/bin/icecast -c /usr/local/etc/icecast/conf/icecast.conf -b /bin/sleep 5 /usr/local/bin/liveice -F /usr/local/etc/liveice/liveice.cfg >/dev/null 2>/dev/null & everything runs fine for a random period of time (sometimes hours, sometimes days) until

http://www.xiph.org/archives/icecast/1732.html Apply the same concept using the "lsof" command and you should be set. GHERdO wrote: > > Hi ppl! :) > > I'm streaming a LIVE radio station with icecast 1.3.11 and liveice. It > works, but I've a problem: > > >[04/Jan/2002:18:48:51] [9:Source Thread] Didn't receive data from source after 500000

i run the latest CVS versions of: icecast / liveice / lame without problem on freebsd-4.3. > I am very tempted to try and use icecast as the weapon of choice > to realize a live audio stream for the radio station I work for. > > Now, the last time I tried the FreeBSD port of Icecast, it > immediately consumed something like 95% CPU time, even without > any client connected. I

There seems to be some discrepancy between rpcclient's man page and "rpcclient --help" in regards to the servername. It seems that the proper usage of rpcclient is rpcclient [options] server this is the format that is specified in "rpcclient --help." rpcclient's man page, however specifies that the servername should come directly after rpcclient. I.E.

I've been trying to figure out as to why sometimes connections are properly negotiated and sometimes not. For example, using mpg123 as a client, I point it at my server (live.wuga.org): Directory: http://live.wuga.org/ Playing MPEG stream from ... MPEG 1.0 layer I, 96 kbit/s, 44100 Hz stereo Illegal Audio-MPEG-Header 0x62dd8776 at offset 0xfffffffb. It has

could someone please point me to a good icecast log analysis tool? i'm looking for something that generates html based on client IPs and their connect times. thanks in advance. -- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu

> > Ices will reload the playlist file if it changes on disk. So if the > > file changes every track, everything will be fine. Alternatively you > > could write your MP3 to a FIFO, which ices could pipe to your icecast > > server. > > that looks like an interesting alternative, tho i have no clue how to do > that, and particularly in the context of otto (which,

> If you want something broken and stupid, the original patch you posted > will probably work ok. Change 'while (1) {' to just '{'. > > Being young and naive, I am still surprised when people are willing to > work twice as hard to do things the wrong way, just because they heard > about that way first. > being old and lazy i'm willing to take the easy

> assuming otto can execute an arbitrary shell command whenever the > track plays (I assume it can call whatever mp3 decoder you want), you > can > a) have a script that does something like > echo $1 > /path/to/playlist.txt > Then ices will reload the playlist file (size: one entry) at the end > of the track. > > b) do > mkfifo ices.fifo > echo ices.fifo >

I've been through this on the list a while back. Unfortunately what you are asking is not possible, nor are the authors of ices interested in solving your problem :) I'd recommend ices-0.0.1.beta5.tar.gz (as recommended by otto's author) and seeing otto/misc/icecast/ices.readme. I use the recommended setup things run great. brian moseley wrote: > > hiya. i'm using ices

I'm just wondering how people are keeping Icecast and Liveice running. If it crashes at some point do you just restart everything by hand or do you have something to keep an eye on the processes (e.g svscan/daemontools program)??? I will be running a stream for a radio station and if the stream crashes I would like it to know that it has crashed and either reboot the system or restart the

hello alexander... you may or may not be acquainted with the program otto; it is a web-based jukebox solution. it has the ability to play both locally as well as to an icecast server via ices. however, as there is not a static playlist, ices needs to to exit after streaming an individual song. the author of otto had the following suggestion for stream.c per ices-0.0.1.beta5: --- i modified the

Hi ppl! :) I'm streaming a LIVE radio station with icecast 1.3.11 and liveice. It works, but I've a problem: >[04/Jan/2002:18:48:51] [9:Source Thread] Didn't receive data from source after 500000 microseconds, assuming it died... >[04/Jan/2002:18:48:51] [9:Source Thread] Lost connection to source on mount /radio, waiting 30 seconds for timeout What can I do? I have no idea

On Wed, 21 Mar 2001, Matthew Mencel wrote: > Yes, I downloaded the aumix utility and am using it now. Set line in to %50 > then %25 and to record but still the same thing. It doesn't matter what the _line_in_ volume is set at just make sure it is selected to record. then set the _rec_ volume, it's a different thing. I use the interactive curses interface, select _line_in_ to

Your distro probably came with an sound mixer application. I use aumix on the console which i had to go get, but you may already have, see if you have a man page. Else you can search freshmeat.net for it. You will need to make sure _line_in_ is set for recording and set the _rec_ volume at 1/2 to start and adjust by trial and error. NOTE: the _line_in_ Volume adjusts how loud you HEAR the source,

Yesm i hear, and it sounds like you are recording from the wrong input. Have you found a mixer application and adjusted volumes? Are you recording (streaming) from a playlist file or the soundcard (or both)? Harvey On Wed, 21 Mar 2001, Matthew Mencel wrote: > If you want to hear what it sounds like, take a listen. I'll have it up for > another 20 mins or so. > >

I've been using liveice to feed an encoded stream to an icecast broadcast server. Now I want to feed two streams at the same time to the broadcast server. To acomplish that I am using a dual soundcard setup in a debian linux server. I've setup two different mountpoints in the icecast server wich will receive the stream and in turn will broadcast the streams to the listeners. This is, the

I've used a Sound Blaster AWE32 / Liveice combo before. Sounds like your record volume is set WAY to high or more likely you are recording from the wrong input. Make sure that it's the _line_in_ that's selected for recording in you mixer app. Also If i remember you have to use HALF_DUPLEX mode (in liveice.cfg) at least if you're using MIXER mode... I'm not sure about in