similar to: file only storing with ices 2 ?

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, recently I have tried to use Ices2 to encode my live (line-in) audio and I can't get rid of this error message: [2003-01-17 04:37:39] EROR stream/ices_instance_stream Failed initial connect to 147.32.127.199:8000 (Unknown error) I have checked all the settings on the server and in the ices-live.xml, but it's still the same. /dev/dsp and /dev/mixer seems to be set up correctly.

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

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>

This is to announce version 2.0.1 of ices. It is a small update to 2.0.0 and is compatible to existing configurations. The most user-visible part of this update is in the ALSA input driver, which some people have reported as being a problem in some cases. You can download the tar files from http://downloads.xiph.org/releases/ices/ Summary of changes since 2.0.0 . update ALSA input . add

This is to announce version 2.0.1 of ices. It is a small update to 2.0.0 and is compatible to existing configurations. The most user-visible part of this update is in the ALSA input driver, which some people have reported as being a problem in some cases. You can download the tar files from http://downloads.xiph.org/releases/ices/ Summary of changes since 2.0.0 . update ALSA input . add

>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

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

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

Apologies for asking so many questions - hope this isn't in the FAQ somewhere!? I would like to use the <savefile> option in ices but am wondering how to specify a unique filename to be created each time ices is executed so the previous savefile is not overwritten? eg, is there a way to specify: <savefile>mystream-%time-%date.ogg</savefile> that would for example create a

ehm, how many memory i need!? : ) i had first 64mb now i have 128mb but also: EROR stream/ices_instance_stream libshout error: Out of memory... --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body.

I have been trying to start up Icecast2 using http://www.howtoforge.com/linux_webradio_with_icecast2_ices2 as my docset. The icecast server comes up; I'm able to go to http://localhost:8000/ and see the pages. I can't seem to get the ices2 part working. I use the suggested config file: [...] <input> <module>playlist</module> <param

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

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

Okay I was poking around the logs, getting ready to test the yp server update, and then I decided to check the configs. I still had localhost set for the hostname, so I changed it to my real hostname. Now I get this in my ices.log when trying to start (although icecast is started fine): [2003-06-05 12:27:00] EROR stream/ices_instance_stream Failed initial connect to myreal.hostname.net:8000

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

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

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

Hello Everyone, I have a bit of a problem trying to set up Icecast2 + Ice2, on my debian box, I installed icecast2 ver 2.3.2-6 and ices2 2.0.1-8. I'm able to start icecast2 as shown in the logs: [2012-12-24 20:34:27] INFO main/main Icecast 2.3.2 server started [2012-12-24 20:34:27] DBUG yp/yp_recheck_config Updating YP configuration [2012-12-24 20:34:27] INFO

On Mon, Sep 26, 2005 at 05:30:11PM +0200, Michael Smith wrote: > > Assuming this is correct, the next question that arises is "Is Vorbis > > when used this way truly gapless?" > > Yes, it is. ... and I can confirm this. No gaps were perceivable decoding in ogg123. However, an interesting effect can be had if all the parts have the same serial number. You get a bump