similar to: Problems with 1.3.10 and Ices (CVS)

I'm wondering if Ices (CVS) loops it's playlist automatically or if I have to add something to the configuration. I looked through all the docs and found no reference to looping... Hunter -- Hunter Hillegas hunter@lastonepicked.com Who is Sharky Towers? What is BroTools? --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To

you need to set netscape for that. your netscape is not yet set to send .pls/m3u files to your mp3 player. t. * Hunter Hillegas <lists@lastonepicked.com> [010824 16:53]: > I'm curious what method y'all are using for getting your streams going on > the client. > > We've been using a hyperlink to the stream like this: >

Hmmm... Maybe I wasn't clear. This is a public Web site. Some people are using Netscape, most using IE... All different kinds of media players, mostly WinAmp, Real, WMP, and iTunes. What I'm looking for is a way for the media player to be launched automatically. If I choose "Open from this location" from the link, WinAmp DOES open. .pls files *are* mapped to WinAmp, I'd

I'm using whatever comes with Icecast 1.3.11 and Ices 0.22. Just grabbed both tarballs from Icecast.org. Is there a way to find out the libshout version? I can't really tell from the Ices source... Hunter > From: tim <tim@nvhs.nl> > Reply-To: icecast@xiph.org > Date: Mon, 27 Aug 2001 17:57:07 +0200 > To: icecast@xiph.org > Subject: Re: [icecast] Icecast Problems

I notice two versions on the Web site, 0.2.2 being shown as developmental. I'm building a new server that will run Icecast 1.3.11 and I'm wondering how stable Ices 0.2.2 is? Are there enough fixes in it that it's worth using it? Thanks, Hunter --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list,

Hunter Hillegas: > I'm wondering if Ices (CVS) loops it's playlist automatically or if I have > to add something to the configuration. > > I looked through all the docs and found no reference to looping... > well, it loops, out of the box, i recognized. (at least the tarball from icecast.org, didn't try cvs) check it with a mini playlist of one song... uno --- >8

The Icecast problems I mentioned yesterday on our new server are getting worse. This time the server only stayed up for about 30 minutes before dying (no more music - process is still running). Obviously this won't fly. Again, ices reports: Error during send: Libshout reported send error, disconnecting: Libshout socket error That's when everything stops. What can we do? Thanks,

Icecast is not going to log the TCP packet overhead, or your ethernet frame overhead, or resends, or collision. A switch would log all of that. It if it's less than a 15% discrepancy, you probably are just seeing packet overhead. jack. On Thu, Jul 26, 2001 at 09:10:42AM -0700, Hunter Hillegas wrote: > I'm seeing some discrepancy between our switch traffic logs and our Icecast >

Howdy, I''m trying to debug a situation where a Rails app running on Mongrel +Apache stops listening to requests. Restarting Mongrel and Apache brings it back to life. First off, here''s some info on versions, etc...: Red Hat Enterprise Linux ES release 3 (Taroon Update 8) ruby 1.8.5 (2006-12-04 patchlevel 2) [x86_64-linux] Mongrel 1.0.1 Rails 1.2.1 fastthread (0.6.2)

FYI, since turning off directory updates, the streams have been up 18 hours. So, if that does turn out to be the issue, is there anything that can be done to "fix" that? Is it a known bug? > From: Brendan Cully <brendan@icecast.org> > Reply-To: icecast@xiph.org > Date: Mon, 27 Aug 2001 16:06:31 -0400 > To: icecast@xiph.org > Subject: Re: [icecast] Icecast Problems

I'm curious what method y'all are using for getting your streams going on the client. We've been using a hyperlink to the stream like this: http://www.fatfreeradio.net:8000/playlist.pls?mount=/hifi&file=dummy.pls It works okay but people get prompted to save or open the file. It would be better if it just opened their streaming player each time, without the dialog. Anyone know

Some of the ices config files were pointing at localhost for the host name, even though the Icecast server is specifically told which IP to listen on. I changed them to make sure they matched. Here's some more info on our configuration: We launch three instances of Icecast, each with it's own configuration file that listen on different IPs and different ports (8000, 8001, 8002). Ices is

Hi, I've used Samba several years without any problems. Last week I added a new disk to my system, and Samba started to behave very strange. It's slow in terms of establish a connection and time to list directories. I've tried to resolve the problem without success. No other daemon has problems, both ftp and http works fine as well as internal communication. Below I've attached

On Friday, 08 June 2001 at 10:12, Hunter Hillegas wrote: > What is multistreaming? It's a new word :) I'm just making ices be able to reencode its playlist at multiple bitrates at the same time, so you can broadcast the same stream for broadband and POTS users. I've already got this working (and I've been listening to it for about an hour and a half so far), but I'm not

On Monday, 27 August 2001 at 09:36, Hunter Hillegas wrote: > > Does icecast 0.1 behave differently? (possible problem: bug in ices > > 0.2.2) > > Nope, Ices 0.1 does the same thing. > > > > > Let's try and narrow the scope a bit. > > Great. Let me know what other info you need. I believe you are using some yp servers. Try turning them off and see if

On Monday, 27 August 2001 at 13:03, Hunter Hillegas wrote: > Okay. It died again after about 4 hours. > > I will turn off the yp servers and see if that helps. > > Any other ideas? Same thing, BTW, ices reported a libshout error. What did you change for this last test, if you didn't turn off yp? --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project

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. Nick ----- Original Message ----- From: "Nick Ludlam" <nick@ivision.co.uk> To: <icecast@xiph.org> Sent: Monday, July 09, 2001 8:54 PM Subject: [icecast] Problem with

Hello Mongrels, Release candidates for Mongrel 1.0.2 and its dependencies are now available. Note that gems are now signed, so please add the Mongrel public certificate via: $ wget http://rubyforge.org/frs/download.php/25325/mongrel-public_cert.pem $ gem cert --add mongrel-public_cert.pem Now you can verify and install the candidates via gem install: $ sudo gem install mongrel

From: "Brendan Cully" <brendan@icecast.org> > 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

From: "Brendan Cully" <brendan@icecast.org> > On Tuesday, 10 July 2001 at 03:21, Nick Ludlam wrote: > > From: "Brendan Cully" <brendan@icecast.org> > > > That handles the segfault, I don't know why the stream wouldn't be > > > sent fast enough though... > > > > Tried with winamp, sonique and freeamp. All exhibit the