Icecast Server: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 4: Line 4:


* [http://www.icecast.org/ Icecast homepage]
* [http://www.icecast.org/ Icecast homepage]
* [http://www.chatixdating.com/ Dating Chat Rooms]
* [http://www.teensay.com/ Teen Chat]
* [http://dir.xiph.org/index.php Stream directory]
* [http://dir.xiph.org/index.php Stream directory]
* [http://www.nabble.com/Icecast-f2880.html Icecast archive / forum] - an Icecast mailing list archive that combines both user and dev lists. It is hosted by [http://www.nabble.com/ Nabble]. You can search or browse Icecast discussions here.
* [http://www.nabble.com/Icecast-f2880.html Icecast archive / forum] - an Icecast mailing list archive that combines both user and dev lists. It is hosted by [http://www.nabble.com/ Nabble]. You can search or browse Icecast discussions here.

Revision as of 01:07, 19 April 2010

Icecast is an open source multi-platform streaming server. It supports Ogg Vorbis, Ogg Theora, and MP3.

External links

Development

  • trunk http://svn.xiph.org/icecast/trunk/icecast
  • kh-branch http://svn.xiph.org/icecast/branches/kh/icecast
    • diff to trunk
      • fast pre-buffering aka burst-on-connect.
        State a burst size in bytes to indicate how much should be sent at listener connect.
      • mp3 accepts artist and title separately on the url.
      • program invocation at stream start and end, per mount based.
      • on-demand relays, activated on first listener, disconnected when listenersfalls to 0.
        Available for master relays as well.
      • multiple Ogg codec streaming. Current codecs handled are Theora, Vorbis, Speex, Writ.
      • Clients are started at theora key frame if theora is being streamed.
      • Added URL and command based listener authentication
      • server xml reload, and reopen logging available via admin url
      • slave startup re-organised so that relays are more independant
      • on xml reload, active sources are updated as well
      • When max-listeners reached, a HTTP 302 code can be sent to redirect clients to alternative slave hosts.
      • authenticated relays, those that match the relay user/pass, bypass the max-listener check