Slashdot Mirror
Icecast 2.0 Released
ArcRiley writes "After 3 years of development and 6 weeks of beta testing, Icecast 2.0 has been officially released! Features include support for both MP3 and Ogg Vorbis, a web administration interface, support for listing in directories (such as dir.xiph.org), and is freely available under the GNU GPL for Linux and Windows."
..would mean 3 years of testing, beta or otherwise. It is after all an open source project...
"Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
Any idea if there is a better interface for controlling which songs play, yet?
Before, IIRC it could only shuffle through a bunch of files in a directory.
I'd like to run Icecast in our office relaying to some external streams to utilize bandwidth for many listeners. Unfortunately, Icecast stays connected to the relays even when there are no listeners, which is a waste. I remember earlier versions of Icecast had this feature, but it has now since gone.
for non-pro/home broadcasting to take off, there needs to be an underlying p2p network layer. This is particularly true as live video-streaming becomes more popular. http://www.peercast.org/ exists, but sadly doesn't seem to have been updated for 9 months, and activity in their forum is fairly low.
Does this support non-Vorbis Ogg codecs such as Speex or FLAC?
Only if you have Winamp 3 but why would you?
Winamp 2 and 5 support Icecast 2.0 OOB
http://www.icecast.org/3rdparty.php
Incase anyone cant fig it out, icecast is avialable for debian as "apt-get install icecast-server".
If I wanted easy I wouldnt be an engineer or a patriot.
Gotta love the slashdot effect. 15 comments and the servers down..
I used to run small stations in college, using Shoutcast on both Windows and FreeBSD. Very simple to install and run. I've read the Icecast FAQ, and I'm a bit confused. It says that it's compatible with Shoutcast servers. Does this mean shoutcast.com's listing servers? Has anyone seen how Shoutcast and Icecast compare as far as memory footprint, system usage, bandwidth usage? or are they more or less the same?
Nothing but the finest in meaningless drivel
Mirror
that I was somehow annoyed that they declared the old version (1.3.2 or something?) as deprecated long time before releasing 2.0. And the website has been unmaintained for quite a long period of those three years.
Actually I turned off my little community-radio-streaming-project just because ogg support was flaky and administration and monitoring was difficult.
But hey, it is always easy to bitch and not to help hands on.
Maybe now Iwill pick up this thing again..
-silence
Dyslectics of the world, untie!
Apologies; an ill-timed cron job strangled the disk throughput on the web server.
But really, who the Hell reads Slashdot before noon? Jeez people, go sleep. CVS will still be there come dusk...
Monty
.. especially for streaming, since a 64kbps stream sounds as good as a 128kbps mp3 stream, which means more people can listen to it, even on their congested at-work LANs, and if you don't attract more people, then at least you cut your bandwidth bill in half. Other codecs that sound sweet at 64kbps exist (windows media, real, quicktime) but they're not free, so you end up paying more than you save in bandwidth.
And if you go legal with your streams, some licensing authorities (for want of a better word) haven't been clued in to how good ogg sounds at half the bitrate, so they'll give you a sucky-quality discount.
If you want to go legal w.r.t. streaming BigFive content in The Netherlands, I don't recommend it btw. BUMA/Stemra seem to have a process in place that's relatively sane (i.e. flat fee for non-commercial use) but you ALSO have to pay SENA (not that it's not spelled SANE..) who are total fucktards in their pricingstructure (BUMA/Stemra are fucktards as well, but at least the pricing schedules seem doable. Anyway, having investigated the options I decided against it (and no, I don't stream unlicensed either).
SCO employee? Check out the bounty
When OggFile becomes useable support for it will be added to Icecast, whereas we'll have support to stream Flac, Speex, Theora (video), any other Ogg codec available at the time. Also, with OggFile, source clients and media players will be able to support these codec combinations, whereas very few players currently support Speex or Flac streaming now.
It always worked properly; you misunderstand how the timing has to work.
When a connection is momentarily interrupted, the streaming server doesn't just stall the timing on the connection; it's still tracking how much data had to go out in a given period of time. The total output at any time will always be up to date. Thus, if the network connection is interrupted momentarily, the data will indeed burst forward to the correct point when connectivity resumes. It's like squeezing off a very stretchy hose for a short time.
The connection is dropped only if connectivity disappears for longer than a certain threshold. Oh, and naturally, if you're trying to listen to a broadband bitstream over a 28.8 modem, you're going to get kicked pretty quickly. The hose only stretches so far, and if it bursts your connection gets dropped. That's not a bug.
Also, a client that falls behind on its own will eventually burst the hose. That's a bug in the client; you won't fall further and further behind unless a) your playback rate is way off or b) your buffering is pooched. It's the client's responsibility to accept data at the rate the streaming server sends it. The streaming server's timing is correct; if something happens to mess with the client timing, the client has to deal with that.
As for 'flooding data at the beginning of a connection', that doesn't really make sense in a system where every client has a configurable, different sized prebuffer.
Monty