similar to: Couldn't Open Pipe to Program

> [2003-02-20 15:24:05] EROR playlist-script/playlist_script_get_filename > Couldn't open pipe to program "/usr/local/icecast2/ices-ad.pm" Segmentation > fault > > I'm running a perl script that apparently (rarely) kills ices for this reason. > The error occurs approximately once per day for no apparent reason. For the > rest of that period the script

Hi: I hit a problem where a script that should return one of a list of files to be played is returning the same one each time. This is obviously not an ices problem, it's what ices did with it that bugs me. Here's the error: [2003-08-12 12:17:26] DBUG playlist-script/playlist_script_get_filename Program/script ("/usr/bin/egosched") returned filename

Hi, I'm currently migrating from Shoutcast/MP3 to Icecast/OGG/Vorbis using ices. Unfortunately, when initialising the encoder, ices crashes with a bus error. Is there anything I can look into? Details as follows: icecast2-2.1.0,1 ices-2.0.0,1 libshout2-2.0_5,1 libogg-1.1.2_1,3 libvorbis-1.1.0_1,3 (All were installed from the ports tree) On FreeBSD ares.radiozilvervos.com 5.3-RELEASE-p4

I have been successful in running a playlist through Ices and Icecast... I have run into difficulty running a live stream through the soundcard, however... The following is the log when I attempt to run ices ices-mylive.xml: INFO ices-core/main ices started... EROR input-oss/oss_open_module Couldn't set sample format to AFMT_S16_LE EROR input/input_loop Couldn't initialise input module

I have just downloaded from anoncvs@xiph.org the ogg, vorbis, icecast, and ices modules. I compiled and installed all four modules without any errors. I seem to have icecast working correctly (no errors in the logs), but I cannot get ices started. I receive the following errors in the log file: [2001-11-09 07:04:54] EROR playlist-builtin/playlist_open_module No playlist type given, cannot

Hi, I wonder if you can help. I am running Icecast 2.4.4, Ices 2.0.2 and libshout 2.4.3. There has been a recent upgrade to libshout and I notice that my previous ices configuration no longer works. In the ices log I get the error message: [2019-07-10 11:10:30] INFO ices-core/main IceS 2.0.2 started... [2019-07-10 11:10:30] INFO signals/signal_usr1_handler Metadata update requested [2019-07-10

Hi... now, I have a trouble on one source machine. I'm using oss to get the sound. encoding is ok with ices 2.0kh60 but with ices 2.0.1, I'm getting [2006-06-07 23:17:48] INFO ices-core/main IceS 2.0.1 started... [2006-06-07 23:17:48] EROR input-oss/oss_open_module Couldn't set sampling rate [2006-06-07 23:17:48] EROR input/input_loop Couldn't initialise input module

Hi! I've installed icecast and ices on a FreeBSD box. When I try to start ices, I get following output: [2003-08-11 11:02:14] INFO ices-core/main ices started... [2003-08-11 11:02:14] INFO signals/signal_usr1_handler Metadata update requested [2003-08-11 11:02:14] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/home/wim/playlist.txt" [2003-08-11

G'day Karl, I've been using your multiple instance version ices-2.0-kh43 for live streaming from my soundcard. After about 24 hours, connection to my icecast server is lost - checking my netstat I see that the connection is in "CLOSE_WAIT" status - this seems to stop it from being able to reconnect. Here is some sample ices.log output: [2003-10-09 06:57:17] DBUG

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

/me grumbles about upcoming finals: I note that the mountpoint entry displays the current songs title and artist, but not the album. In the particular case of my station, album is often more important (recognizable) as there are a variety of pop/classical artists who do music for anime. So I'd like to add an album nature but am going to need a quick overview on how stats.xml is generated.

On 22 Mar 2003, Karl Heyes wrote: > ethereal is a good tool for that, start a capture (maybe with a capture > filter of "port <port>" or "host <ip>" to limit it if the box has plenty > of traffic), connect the source, wait a second then stop the capture. > Pick one of the packets that relates to the source stream and do > tools->follow tcp stream.

Me again.... After getting regular playlist streaming working, I'm not trying to complete the project and implement the live streaming. Unfortunately, due to the sad, lacking documentation for icecast and ices (especially what the xml tags in the configuration files actually DO and how they can be used), I've run into another snag that only you guys can help me out with. Here it goes.

>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

Last I checked, iTunes was unable to play my static playlist ogg vorbis stream. Assuming this is expected behaviour and not an anomaly; Does iTunes 4 resolve this issue? --thanks Michael Edwards http://www.walledcity.ca <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

Hello, I will take your last version, but I have fresher news about the bug that occurs every mornings in fact... I think this is ntpdate which is causing the problem, as the time of the machine change for more than one second. Here is all the info: 09:46:17 up 1 day, 1:22, 2 users, load average: 0.60, 0.71, 0.68 86 processes: 84 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 10.4%

Hi I'm trying to setup a new streaming server for us. We are a radio station which we stream live and have archive files (mp3). We currently are using icecast-1.3.12 on solaris9 and darkice-0.13.1 also on solaris9. I have setup two new servers using icecast-2.2.0 on solaris9 and ices-2.0.1 on solaris9. I'm not sure if I have setup the conf files correct (see attached files) but I am

Hi all, I'm fairly new to icecast / ices - been using icecast (2.2.0) to stream audio files for a few weeks, it works very well, now I'm trying to add live feeds via ices (v2.0.1). I've built and installed (on SuSE 9.3 platform) with no apparent errors, copied ices-alsa.xml to user area and modified paths, server password etc. When I run ices (using "ices

i can do it, but i mean it would not talk much to you ; ) [2003-05-31 12:00:25] INFO ices-core/main ices started... [2003-05-31 12:00:25] EROR stream/ices_instance_stream libshout error: Out of memory [2003-05-31 12:00:31] INFO signals/signal_int_handler Shutdown requested... [2003-05-31 12:16:47] INFO ices-core/main ices started... [2003-05-31 12:16:47] EROR stream/ices_instance_stream

I'm still having trouble (after reading the archives) geting ices2.0.0 to work with ALSA (I seem to be able to do arecord just fine. I'm using the following packages (along with ices-2.0.0.tar.gz). kernel-smp-2.4.22-1.2188.nptl kernel-smp-module-alsa-1.0.4-1_2.4.22_1.2188.nptl alsa-driver-1.0.4-1 alsa-lib-1.0.4-1.1.fc1.fr alsa-lib-devel-1.0.4-1.1.fc1.fr (and a few other alsa ones, but