similar to: Two streams problem

We just built a new server to run Icecast 1.3.11 and Ices 0.22. It's a Dual PIII running RH7.1. We put it online last night and Icecast ran fine for 20 hours. Then it started throwing some errors.. That's when Ices died. Ices reported a libshout error. Part of the Icecast log is included. What can I do about this? Hunter [26/Aug/2001:16:05:01] [32:Connection Handler] Accepted

Hello. I want to configure an audio streaming server on a linux machine(Fedora Core 1) in the following way: i want to receive data from internet(a radio) and to transmit it into my local network.I want to ask you for you help,if you can tell me a solution for this(preferably,non-GUI solution). I found the xmms-liveice project and it is what i need:i put into xmms playlist the radio's

With perl 5.8.3, 'configure' is fine but 'make' dies giving ------------------------------------- /usr/lib/libc_r.so: WARNING! setkey(3) not present in the system! /usr/lib/libc_r.so: warning: this program uses gets(), which is unsafe. /usr/lib/libc_r.so: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc_r.so: WARNING! des_setkey(3) not present in

Greetings everyone.... When I run liveice, I get an "Error:sending data to remote server message" from liveice, and then it hangs (I actually have to open another console window to kill the process). The IceCast server respond with the following: Kicking source 1 [127.0.0.1] [Access Denied (tcp wrappers (source connection))] [encoder], connected for 1 seconds, 0 bytes transfered.

Just a shameless bump incase anyone missed this... :P <p>>From: "Joe Jones" <joe_jones64@hotmail.com> >Reply-To: icecast@xiph.org >To: icecast@xiph.org >Subject: [icecast] Problems with Ices0.3 >Date: Fri, 12 Mar 2004 15:26:23 +0000 > >With perl 5.8.3, 'configure' is fine but 'make' dies giving >

Greetings everyone.... I tried posting this once before, but got no response. When I run liveice, I get an "Error:sending data to remote server message" from liveice, and then it hangs (I actually have to open another console window to kill the process). The IceCast server respond with the following: Kicking source 1 [127.0.0.1] [Access Denied (tcp wrappers (source connection))]

After one minute of connection the stream from our icecast 1.3.10 server (debian package 1.3.10-2) starts stuttering. And after some stuttering the client is disconnected by the server. The usual client is a windows winamp. The icecast logs shows that the the client is not receiving data fast enough. A small part out the logs is shown below. That the data is not received fast enough is rediculous

Not got to the bottom of it yet, but commenting out both LOG_INFO lines in thread/thread.c stops it segfaulting. Now I'm back to the old problem of a 128k stream not being sent fast enough to the clients. Nick ----- Original Message ----- From: "Nick Ludlam" <nick@ivision.co.uk> To: <icecast@xiph.org> Sent: Monday, July 09, 2001 8:54 PM Subject: [icecast] Problem with

Hi, got a little problem with the current cvs version of ices. I'm invoking it with the following: ices -v -F /home/nick/icetest.pls -h localhost -P <my password> which seems to connect ok, get past password validation, and gives me the following: DEBUG: Sending following information to libshout: DEBUG: Stream: 0 DEBUG: Host: localhost Port: 8000 DEBUG: Password: hack Icy Compat: 0

Hello! I've just started useing Icecast and Ices. Both has mainly the defaults in their conf files. fe.: Ices uses the default /ices mount point, end so on. After playing serveral hours, problems come up... Ices dies. In the ices.log these can be found: Error during send: Libshout reported send error, disconnecting: Libshout socket error. Error during send: Mount failed on

Hi ! I am new to the list. I have been using icecast togeahter with ices and live streamers for almost a year now. We have between 10 to 300 listeners, localsite and outside world. It has not been troublefree, icecast was stable util a week ago, just crashed and refused to work anymore. We upgraded in hope to get rid of problems. It worked for maby 24 hours and then it just stops by random after

I need help configuring Samba v3 to do file sharing with Windows 2000pro and XP through SWAT. I've listed my user groups in the read, write, and valid fields of my share's parameters page. My security level is set to USER, and read-only option is set to NO. From any Windows workstation I am able to successfully map a drive to the Samba share; however, I can not write to it ("Access

Ok - here's what I want to do... I compiled and installed icecast 1.3.11 and ices 0.2.2, and can get a single lame-encoded stream working. What I'd like to do is set up two streams - one at 48kbps, one at 128kbps - from one source. Reason being is that I'd like to listen to the high-bandwidth stream locally (ie: in another room of the house) while I listen to the 48kbps stream

First off, I managed to build iceS 0.2.2 with Python 2.1, though I had to add -lutil to the $LIBS definition whilst ./configure'ing. Otherwise, configure won't find Py_Initialize Secondly - multiple streams I've added a second "stream" definition to my ices.conf, and both streams show up as sources for icecast, (http://blah.com:8000/list.cgi), though when i try to connect

> > We will have thousands of 24 hour playlists generated everyday by > software I'm developing. If we encode all our audio files at 32kb/s, > could we not just supply a link to the playlist files directly on our > server. So in effect, our server is just acting like a hard disk and > listeners are playing the files directly. Would this work? you mean you have a pool of

OK...since Liveice doesn't support Icecast 2 I've set up an Icecast 1.3.12 server. <p>When I run Liveice I still get the problem: ------------------------------------------------------- /local/liveice/temp.playlist ...... done setup_pipes()... Initialising pipes for stream 0 Successfuly set up fifo .liveice_temp_files/raw.pipe0 Successfuly set up fifo

> > >you don't want to do live simulcast sh0ws , correct? .. just offer 24-7 > >music ( which will change depending on the time ) . you don't want to have > >actual radio shows w/ song intro's , etc . . > > > That is correct, however, there will be song intro's etc because they > will be pre-recorded as audio files. right . but all the content is

Hello, I'm new to the list, just want to say thanks a head of time to who ever can help me out with some streaming problems Hareware/software: Athlon 700 128megs of RAM 256megs swap FreeBSD 4.2-RELEASE 100mbit connection icecast 1.3.10 ices (beta) My setup: I am running 2 spawns of icecast and 2 spawns of ices. one ices process is reencoding to 24bit and the other to 128bit and both are

On Sat, 2003-11-22 at 00:43, Lukas Österreicher wrote: > >it supposed to, check the log file for details but there is no reason > >for it not to work with 2 instances. > > > >Note as well, that you should have 2 instances each of which has the > >icecast connection details and an encode section. > > > > I don't quite understand. You always talk about

In the ices-playlist.XML file there are two tags <logpath>/pathtofile</logpath> and <logfile>ices.log</logfile> You can choose a different name for each instance/stream: <logfile>mylist.log</logfile> Or you can change the path for the each instance/stream: <logpath/media/music/</logpath><logfile>ices.log</logfile> Just be sure the account