similar to: icecast refuses to accept encoder after losing original feed

Matt -- I actually came up with a much more elegant script. On FreeBSD there is a command 'fstat' (I'm sure this could be modified to use 'lsof' or something of the like). First of all, while liveice and icecast are running properly, # fstat -m | grep liveice |wc -l for me yeilds 56 or 57. I let liveice die and checked again, and that number went significantly down.

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

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

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

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

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

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

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

Hi, > icecast / liveice / lame > > without problem on freebsd-4.3. thanks a lot. How about OSS then, no troubles? What sound card do you use for A/D-changing? -- Radio HUNDERT,6 Medien GmbH Berlin - EDV - j.muenther@radio.hundert6.de --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a

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

i know with icecast2/ices , karl heyes has some example config files for mixing live/static content ( if i recall correctly ) . however, what i had done in the past is add the static file to the .pls prior to the live mount . if you generate the .pls files on demand , this would work . ALSO , i'm quite sure that both icecast1/2 support intro/outtro files , etc .. this may achieve the same

I've been running classic icecast + liveice for some time now (several years) without problems. A couple days ago, the station manager (NPR affiliate) came to me and asked if we could 'inject' a static file into the stream. Basically what he wants is for the client to first receive a static file (requesting donations of course) and then on to the live stream (*not* intermittently).

Since upgrading our openldap (v1.2.13) server to 4.8-STABLE from 4.7-STABLE, we've noticed that the slapd server increasingly eats up memory, before dieing and coredumping after about 15 minutes. I rebuilt the package (via ports), post-upgrade, to see if that fixed the problem and no dice. I've rebuilt libc_r and the pkg with debugging symbols, yielding the following: # gdb ./slapd.static