similar to: problems with icecast/ices

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

Mike / Karl - I've tried two different ways of setting up the "stream". In one URL, I named the file directly (http://foo.bar.org:8001/stream.ogg), and in the second, I made a stream.m3u file containing the afore mentioned http statement. Neither worked in Winamp. I had downloaded version 3 of WinAmp, so I uninstalled that, and went out and got the JOrbis (Java) player and the

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

Hi, i'm a newb to using icecast. what i'm using is, foobar2000, with the altacast encoder. I went in to the config file, and changed the adminname/password. i've left everything else at there defaults. I open up altacast, and add a new encoder, giveing it the user name, and password. it works fine. But when giveing the link to people to listen, they say they can't open it.

Hi, I'm trying to repair a remote system using the Live CD. I have VPN access to the subnet where it lives. An onsite person is booting from cd, and running a small script I provided to tweak the default firewall rule set to allow incoming ssh, and set a password for the centos user and start sshd so far so good I can remotely access the system. the problem is the live cd environment is

hello I have the following problem: is it possible to have several ices "feed" mp3 files to only one icecast process ? or do I have to make pais - ices/icecast - in order to have several streams on my machine ? thanks, petre -- Petre Bandac - petre@kgb.ro

I have an experimental installation of ices 0.4 streaming to icecast 2.2.0 on the same server (libshout 2.1). Ices had been very stable until this weekend, when it began dying after playing only a few MP3s (same files as before). Nothing in the ices.log to indicate a problem. The icecast error log shows this when ices dies: [2005-07-25 13:24:21] INFO source/source_main listener count on

ok, correct me where I'm wrong: - the <sources> tag defines max ices processes can feed icecast - several ices sources are sent to the same icecast process, but on different ports - the icecast process is configured with <relay> <server>127.0.0.1</server> ..... </relay> for each ices instance ? or with mount ? thanks, petre On 29 Sep 2005

Hi, On 2003.11.26 15:42 Karl Heyes wrote: > The reconnectattempts value is from the CVS code, and can be a bit awkward > in general. > > ices can have multiple instances and in these mods can have multiple shout > connections per instance. I don't think terminating ices for just one > shout > connection is acceptable, I'm more inclined to drop the reconnectattempts

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Michael and thanks for answer! On Tue, 13 Jan 2004, Michael Smith wrote: > This shouldn't be being passed to _check_pass_icy() at all - this isn't the > "icy" (shoutcast nasty ugly) protocol at all. We support that (icy) protocol > because it's widely used - but it's a horribly ugly hack to pretend that

On Wed, Jun 26, 2002 at 08:22:18PM +0200, Thomas Gutzler wrote: > > On Wed, Jun 26, 2002 at 10:08:20AM +0200, Thomas Gutzler wrote: > > > > > Can I force a special streamer "foo" always to be heard on a specified > > > mounpoint "/bar" ? > > > > Please rephrase the question im not sure i understand? > > OK. Theres a DJ

Hi, and a Happy New Year to everyone. I have followed this tutorial to install icecast on Centos 5.5, http://www.howtoforge.com/linux_webradio_with_icecast2_ices2 but cannot find the ices package for sending the audio to icecast for it to stream. I would like to send the data as mp3, if there is a suitable program to do this. Has anyone on the list done this on Centos? Kind Regards,

From: "Brendan Cully" <brendan@icecast.org> > Sorry Nick, I lost your last mail. One last thing, did you make clean > && make? The dependencies are not generated properly for ices, so even > if libshout got rebuilt it might not have been relinked. There's no other libshout on the system. Have rebuilt from scratch and it still exhibits the timing problems.

hello, i'm starting/stopping icecast (1.3.11) & ices (0.2.2) from a web interface. fine so far, but now i see strange things: both ices & icecast, once started , (ices -B ... , icecast -b ...), both processes and their childs are listening also to port 80, besides their normal operation. i've found out because apache didn't restart (Address already in use: make_sock: could

On Tuesday, 10 July 2001 at 01:26, Nick Ludlam wrote: > Not got to the bottom of it yet, but commenting out both LOG_INFO > lines in thread/thread.c stops it segfaulting. Now I'm back to the old problem > of a 128k stream not being sent fast enough to the clients. you should just be able to increase STACKSIZE in thread/thread.c from 8192 to 65536. The default stack size is too small,

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

On Saturday 05 April 2003 16:11, Geoff Shang wrote: > Hi: > > One thing to keep in mind. The example mountpoint configuration gives an > alternate username for the source of that mount. However, as far as I can > see, there is no way of changing the username yet in ices (or any other > source). So you have to comment this out if you want to use a mountpoint > configuration

Hello, I'm using Icecast, Ices, and the script module configuration to serve the playlist to the server. Playlists are scheduled once per day with regularely placed events (like spots) which run at specific times. Unfortunately it's being served too fast, so it's always getting ahead of schedule (gaining about 10 seconds on every hour). I have tried adjusting the flush-samples setting

Icecast / Vorbis community, I have a icecast/ices audio streaming server from which I stream ogg audio files. I know that I can encode different streams for low, medium and /or high quality broadcasts (for example). However, I would like to have one stream that uses bit rate peeling to send the user the highest quality stream that their bandwidth will allow. Has any one done this? Does any

So basically, I download and install ices 0.3, fire it up as well and then using the currently running icecast server, just set a new mountpoint. Instead of /ksl.ogg I would make a /ksl.mp3 mountpoint. This would be configured in the configuration file included with ices 0.3? I am only doing live streaming, feeding a raw audio feed into the box, and then encoding it on the fly. Thanks much. KJ