similar to: Ogg stream at less than 22KBps 22KHz

I'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

Hello, I have a problem with icecast icecast-2.0-kh8: - the source disconnect - icecast didn't notice it - the source cannot reconnect until - the source cannot reconnect (it tries every 8 seconds) - after two hours, the source is able to reconnect Here is the interesting parts of the log files: Thanks for your advices and help. Chris (icecast machine has +3sec in its time, that's

On Sun, 2003-11-23 at 00:35, Kerry Cox wrote: > Now I tried to add a third stream by adding the following <instance> to > the above config: > > <instance> > <hostname>xx.xxx.x.xxx</hostname> > <port>8000</port> > <password>secretpasswd</password> >

It was kind of working for a while but I could not hear the stream but it was running. I started messing with alsamixer and now it crashes. I see the error but I don't know how to fix it. ices-oss-xml: (alsa is the same just a different input module) <?xml version="1.0"?> <ices> <!-- run in background --> <background>0</background>

Hi... first post to this list so be gentle with me! I've got Icecast 2.2.0 running well, and using Ices 2.0.1 to feed the OGGs. All was working, then all of a sudden I've started getting these messages in the (ices) log... [2005-05-08 12:10:19] INFO ices-core/main IceS 2.0.1 started... [2005-05-08 12:10:19] EROR stream/ices_instance_stream libshout error: Out of memory [2005-05-08

Hi everybody, I'm in charge of an ices2 setup that's broadcasting a local radio station on the Net, and I'm currently under fire because one of our streams has been down twice in two days, forcing me to restart ices2 on each occasion. Our client is understandably unhappy about this. OUR SETUP: I've got ices2 installed on a local machine, broadcasting to an icecast server across

Hello. I am running an up-to-date cvs snapshot (10 Aug 03) of ices2, and I cannot get the Metadata update from file to work (indeed this has always been true on all previous versions of ices2 that I have used). If I send the ices process a SIGUSR1, then the error log shows that the update is taking place, but immediately followed by a read error from the OSS input module, causing ices to die. I

I am having problems getting Ices to work with ALSA. If I use arecord (arecord -D plughw:0,0 output.wav) I can record the input from my microphone into a file. The playback works perfectly. However, if I use Ices with the same values I hear nothing on the receiving end of my broadcast (although I can connect to it). In order to do a further test, I setup a <savefile> tag in my

Got it all compiled nicely.. I called it ices2 so I can keep using my existing ices executable as well.. Tried getting it up and running but it seems to be having trouble connecting to my soundcard.. sample from ices.log [root@darkice root]# less ices.log [2003-08-06 01:11:09] INFO ices-core/main Streamer version IceS 2.0-kh35 [2003-08-06 01:11:09] INFO ices-core/main libshout version 2.0-kh19

Thanks Karl, I will give it a try. Do I have to install your modified libshout or isn't it required if I am live streaming? Cheers, Matt On 5 Aug 2003, Karl Heyes wrote: > not in CVS ices2, the problem is fairly involved to get into, not so > much for the initial filename but for things such as timing out or if > there's a problem with the link to icecast. > > If you

I tried to stream two different playlists in two different mount points. I created playlist1.m3u for ogg compressed at 96 Kbps and playlist2.m3u for ogg comressed at 32 kbps (wich each playlist contain the right path to ogg files) i created another ices-plylist.xml called ices-playlist32.xml in this one i had changed the path to the playlist file <param

Hmmm, I guess more is incorrect here than I thought. I changed the resample in-rate to be 44100 like it should have have been. But still no joy. Here is the error message as shown in the error.log file. I'm looking things over and am not seeing my error. It looks like the audio resample for this particular stream is good. [root@icecast conf]# ices /usr/local/icecast2/conf/ices.stream.3.xml

[In case anyone is wondering, the missing message is because I emailed Mike directly, not realising I wasn't sending to the list.] On Tue, Aug 16, 2005 at 12:56:57PM +0200, Michael Smith wrote: > On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > On Tue, Aug 16, 2005 at 10:31:09AM +0200, Michael Smith wrote: > > > > > This shouldn't cause any

Hello, I'm testing icecast2(apha2) and ices2(beta2). (sources 2003-08-12) ices2 with ices-playlist works fine! But I have troubles whith ices-live. When ices2 trays to read /dev/dsp a log message appears: INFO input-oss/oss_read Reached EOF, no more data available. and ices2 shutdown. the complete log file (debug=4): ******************* log *******************************************

Hy, I've just installed the latest release of icecast2 and ices from CVS. I have a linux Slackware 9.0 with the default packages. After install of ices and icecast & relative libraries (with no errors), I've started the icecast server. When starts ices, this is the debug: --- INFO ices-core/main ices started... INFO input-oss/oss_open_module Opened audio device /dev/dsp at 2

Now every thin works fine good, thanks a lot for helping me, but there is another problem. in ices-playlist.ogg the are to sections first section is: <input> <module>playlist</module> <param name="type">basic</param><!-- Only 'basic' implemented --> <param

Karl, I installed icecast/ices from the latest stable ebuild on gentoo portage. It appears from the log file that ices is only version 2.0.0 even though the ebuild is version 2.1.0. I just reinstalled icecast with the newest (unstable) ebuild and it still doesn't seem to have version 2.0.1 of ices. Do you recommend that I manually compile or that I find a way to use a wrapper for ALSA to

On Sun, 2003-11-23 at 03:51, Kerry Cox wrote: > Hmmm, I guess more is incorrect here than I thought. I changed the > resample in-rate to be 44100 like it should have have been. > But still no joy. Here is the error message as shown in the error.log > file. I'm looking things over and am not seeing my error. > It looks like the audio resample for this particular stream is good.

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the