similar to: ices2, metadata, bumps and crashes

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

[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

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

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> >

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?ve successfully implemented IceCast on a Raspberry Pi and can access the stream ONLY if I use an ffmpeg statement to start the stream. Unfortunately, the stream is choppy and the sound quality is poor. I?ve tried using ICES, but I don?t get any sound. Terminal command that works: ffmpeg -ac 2 -f alsa -i hw:0,0 -acodec mp3 -ab 48k -ac 2 -content_type audio/mpeg -f mp3 icecast://source:password

Hi, Is it possible to generate an ogg stream at less than 22KBps ? I tried several configuration with ices and darkice, but I always get an configure encoder error: [2003-03-17 16:07:17] INFO input-oss/oss_open_module Opened audio device /dev/dsp at 2 channel(s), 44100 Hz [2003-03-17 16:07:17] INFO audio/resample_initialise Initialised resampler for 2 channels, from 44100 Hz to 22050 Hz

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

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 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, I've been having LOTS of problems lately getting ices to work the way I want on my computer and I've just about gotten to the last problem. When broadcasting live media off of any sound card other than the primary (Default, aka: /dev/dsp) sound device I only end up broadcasting silence. Furthermore, the connection time is much longer than usual and not because of buffering. I

> On Tue, 2003-05-27 at 21:06, adam leigh wrote: > > Unfortunately, ices2 isn't writing anything to the logs. I've got them on > > debug mode, but there still isn't anything being written to indicate it's > > having a known problem. > > well thats a problem, you should at least see > ices started > if not then try to resolve that first. Email

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

I posted the other day with a question about a player that mysteriously quits playing the icecast stream. I believe the problem is related to the icecast stream for two reasons. 1) Because it quits on more than one different player (Winamp 5 and Foobar2000) and 2) Because I used to use shoutcast with Winamp 2 and never had this problem. Anyway, I tried to get as much information about the problem

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>

Hello, hmmmm sweet problem. All I can recommend you is have you tried another player? I've heard that WinAmp3 has certain problems with .ogg streaming. No other idea :(. Martin On Fri May 16 2003 11:14, photos-ifree wrote: > 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

On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Caught it yesterday, as I was already running level 4: This line: [2005-08-15 04:10:58] EROR stream/ices_instance_stream Send error: No error (Success) is the one that catches my attention. Unfortunately, ices's error logging is somewhat sub-standard. Can you cross reference this against your icecast error.log to see

>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 two instances. Do you really mean two instances of ices2 called seperately? Do I have to make

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

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