search for: iceing

I see that I don't understand why it is still using the xaudiocast protocol here is my config file located in this same directory. <?xml version="1.0"?> <ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices"> <ices:Playlist> <ices:File>test.txt</ices:File>

I'm no expert on Ices0.3 but that config doesn't look right to me. I'm guessing that it's imperative to have the server config as part of the stream section since you can have multiple streams from one source going to multiple destinations (I think anyways.. :) Take a look at my config for ices0.3 below : --------------------------------------------------- <?xml

*** the following config: <input> <module>playlist</module> <param name="type">script</param> <param name="file">/radio/getnextsongpath</param> </input> gets me: Could not find a valid playlist file. Ices Exiting... *** the following header of the config file: <?xml

On Thursday, 15 April 2004 at 08:07, Kristoffer R. Munroe wrote: > I am using the http protocol now and I still get the same results. <snip> > >DEBUG: Sending following information to libshout: > >DEBUG: Stream: 0 > >DEBUG: Host: 127.0.0.1:8000 (protocol: xaudiocast) According to the log file you attached, you're still using xaudiocast. Double check your

OS: FreeBSD4.8 okay I installed ices from /usr/ports/audio/ices copied ices.conf.dist to config.xml can somebody explain to me why the configuration file is not getting loaded root@hurricane# ices [/usr/local/etc/ices] IceS 2.0beta2 (c) Copyright 2001-2002 Michael Smith <msmith@icecast.org> Usage: "ices config.xml" root@hurricane# ices

hi don't know if i'm missing something, but how do i name mount points using ices? i assumed this was specified in the <ices:Stream> <ices:Name></ices:Name> </ices:Stream> chunk but whatever i put in there, icecast tells me that my stream is going to /ices (according to the output from configure/make, xml is being properly compiled it) --- ...ALSO, a

I am still working to insert mic in a stream. I found a walkthru here:http://www.daniweb.com/techtalkforums/thread6875.html and I have been trying to get ices to accept the sample script. I am seeing the complaint: XML Parser: Document of invalid type, no ices namespace found Logfile opened Could not find a valid playlist file. Ices Exiting... As far as I can tell, the config file's

I get a segmentation fault when starting the IceS encoder on a Linux-based QNAP NAS. I'm trying to set up IceS to stream an ALSA input to Icecast. Icecast works well and confirms when I stream using other things to it. However IceS hits a segmentation fault immediately after starting the encoder. The IceS log is: [~] # sudo ices /etc/ices.xml [2020-05-11 19:24:34] INFO ices-core/main IceS

Hello, I'd like to be able to run multiple instances of Ices (2.0), each with their own playlist and streaming to different mountpoints. Although I'm relatively new to Ices and Icecast, so far I have had little trouble getting it running with two or more instances of Ices feeding off fixed playlists (files). I'd like to be able to set each instance of Ices to run with script based

Why does cpanel want to remove ices files? How can I prevent this from occurring? What I get is /libexec/ld-elf.so.1: Shared object "libshout.so.3" not found, required by "ices" after cpanel does it nightly updates. Also if I do a SIGHUP to ices to update a playlist, do I just need to issue the command ices SIGHUP? What would be the correct format. Again, I apologize for

hiya. i'm using ices 0.2.2 with icecast 1.3.10 and otto 1.0 (a web/db playlist mgmt tool). overall, i'm very pleased with the setup, but i'm having a few problems. 1) whenever otto plays a track (by exec'ing ices), that same track keeps playing over and over. i have to direct otto to kill the track (and the ices process) in order to get it to play the next track. i notice this

Thomas: On Thu, 20 Nov 2014 19:26:30 +0000, you wrote: >Which version of RedHat is this? Fedora release 20 (Heisenbug) >Could this be a x86 vs amd64 thing? Just to be sure run "file" on the >binary? The processor is definitely a 64-bit processor, even though that's not verified with the above version name. However, I'm the one who installed it, I know it's the

You are trying to use ices 2 with an ices version 1 config file. On Friday, 13 June 2003 at 08:01, admin wrote: > OS: FreeBSD4.8 > > okay I installed ices from /usr/ports/audio/ices > > copied ices.conf.dist to config.xml > > can somebody explain to me why the configuration file is not getting loaded > > root@hurricane# ices

On Wed 29 Jan 2003, Karl Heyes (karl@pts.tele2.co.uk) wrote: > On Wed, 2003-01-29 at 17:13, Marc Remijn wrote: > >> But when I did 'make' it broke with: >> >> encode.c: In function `encode_initialise': >> encode.c:91: storage size of `ai' isn't known >> encode.c:92: `OV_ECTL_RATEMANAGE_GET' undeclared (first use in this function)

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

Hello, I have tried to build ices both from CVS and from the latest tarball from the web site (using a varienty of configure options, or autogen.sh in the case of cvs). Whenever I try to run it I get errors: cadmium:/work/dl/Audio/streaming/ices-0.2.3 # /usr/local/icecast/bin/ices --help /usr/local/icecast/bin/ices: error while loading shared libraries: libgcc_s.so.1: cannot open shared object

Hi, this just means that ices cannot be found in the global system PATH, because you did'nt run configure with option --prefix=/usr/. If you just run configure everything will be installed after a successful mak and make install in prefix /usr/local. Try to start ices like /usr/local/bin/ices -c /usr/local/etc/ices.conf.dist -B Hope this helps Sascha

Is anyone else experiencing what seems to be a memory leak with Ices? I can have icecast up and running with WinAmp streaming to it from my '98 box for days at a time with no problem. As soon as I start Ices I'll launch top to watch and my free mem starts dropping -fast-. Starting from about 160MB free, in 4-5 hours I have 2MB free with Ices crashed and the memory unrecovered which sends

I recently upgraded ices from 0.1.0 to 0.2.2. I have found that it is not reencoding my mp3 stream, even though I have it configured to. This is on a RedHat linux 7.0 system, kernel 2.4.11 ices build commands: ./configure --with-perl --with-lame \ --with-lame-includes=/usr/local/src/lame-3.89/include \ --with-lame-libraries=/usr/local/src/lame-3.89/libmp3lame/.libs gmake