similar to: ices, alsa, dsnoop plugin a metadata update

Hello I've discovered, that sending a SIGUSR1 signal to ices causes it's shutdown when recording from an alsa dsnoopped device. > [2004-11-01 18:51:51] INFO signals/signal_usr1_handler Metadata update requested > [2004-11-01 18:51:51] DBUG metadata/metadata_thread_signal meta thread wakeup > [2004-11-01 18:51:51] DBUG stream-shared/stream_wait_for_data Shutdown signalled:

[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

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

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

Hi Pete, El jue, 28-11-2019 a las 09:51 -0500, Rondejavu escribió: > I am starting IceCast first. The log indicates that everything is > working. Maybe I need to change something in my HTML code? > > audio controls > Source src=“ipaddress:port/stream” > /audio > > -Pete > Not change your HTML code, in fact, it is already working ok. You must solve the problem on the

Hi, I just installed 2.0.1 but I'm unable to use it. It doesn't want to connect to my server, but instead, it tries to connect to localhost:8000 (default). My configuration file is the same than before. It's working fine with ices 2.0kh60 I wanted to change because since I installed icecast 2.3.1, ices freeze every day at each network interruption (xDSL IP change). My ices runner

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

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

Hello, I'm running Icecast2 server (cvs-2003-03-19) with program of Czech public radio stations "Czech Radio". I'm affraid I found something wrong in the yp-directory subsytem of the Icecast2. I'm using this access to directory server: <directory> <yp-url><a

On 16-01-13 21:52, Clemens Ladisch wrote: > Rene Herman wrote: >> I'm out of touch of with alsa -- but should dmix/dsnoop still be >> enabled by default on hardware that doesn't do hardware mixing? > > Yes. > >> I believe that it should be from /usr/share/alsa/cards/ICH4.conf, >> but I don't get mixing on this setup when using the

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

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

Hello, ices kh48 seems to have some trouble... See the stranges characters avec metadata update. (before, it was written bad address) and also, it is not connecting to icecast: socket error, ... I go back to kh47 for the moment. Chris [2003-11-25 10:45:50] INFO ices-core/main Streamer version IceS 2.0-kh-pre48 [2003-11-25 10:45:50] INFO ices-core/main libshout version 2.0-kh22 [2003-11-25

... [2009-02-14 20:54:27] INFO ices-core/main Shutdown complete [2009-02-14 21:01:02] INFO ices-core/main IceS 2.0.1 started... [2009-02-14 21:01:02] INFO signals/signal_usr1_handler Metadata update requested [2009-02-14 21:01:02] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/etc/ices2/playlist.txt" [2009-02-14 21:01:02] WARN

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

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

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

mmm... ok. well i got ices2 installed properly now (i hope) after some effort and help (cheers Michael for the prompt response!). the goal is to get ices2 to stream to a peercast client on port 2768. but somehow things are still not going quite as planned. here is the log ----------------------------------------------------- idoru:/var/log# ices /usr/local/etc/ices.conf [2003-03-20 22:55:29]