About 2 years ago I posted my first announcement for SHOUTcast 2.0. Now, nearly 2 years ago they released the very first beta version of the new SHOUTcast Server version sc_serv 2 Beta v.01, also named as SHOUTcast DNAS 2!

We are currently testing the version and will update this post very soon to get you updated on the new SHOUTcast software. If you have any questions, just ask!

Here you can download new sc_serv 2 BETA v0.1 (SHOUTcast DNAS 2)!

By the way: The SHOUTcast team also released a new version of sc_trans 2 BETA 6

Presenting the first Beta point-release of what will be the next-generation of SC_SERV SHOUTcast DNAS broadcasting server! This drop is the result of the SHOUTcast broadcasting community’s list of feature requirements over the years.

The goal of SC_SERV2 is to provide enhanced serving features and access to the new yp2 infrastructure (in development)
while maintaining as much backward compatibility with the previous sc_serv as possible.

Release Notes:

1) Serve multiple streams from a single server instance
2) Relay multiple streams from a single server instance
3) Multiplex all server activity through a single IP port.
4) Shoutcast 2 wire protocol support for sources, relays and clients
5) Repackaging of Shoutcast 1 and Shoutcast 2 data as appropriate for the connecting client(s)
6) yp2 infrastructure support

To take advantage of these new features you will also need the following:

1) sc_trans version V2 B38 or higher: http://forums.winamp.com/showthread.php?s=&threadid=317229

2) authorization hashes (register as a broadcaster in the new infrastructure and you will be issued the necessary hashes) – COMING SOON!

sc_serv must be configured to use the yp2 infrastructure to take advantage of the multiplexing and multiple stream support. The original yp interface had no means of
expressing multiple streams from a single port.

The yp2 interface is still in development and will be released soon! Stay tuned for updates.

If you are going to connect multiple sc_trans instances to sc_serv, you must use the Shoutcast2 protocol.
The original Shoutcast protocol had no means of specifying a stream ID. Clients connecting to the
server do not need Shoutcast2 support, since sc_serv will repackage the stream data and metadata for them as appropriate.

Since the SHOUTcast Team released the very first BETA of sc_serv 2 today, they also released sc_trans 2 BETA 6.

The 6th version of the SHOUTcast Transcoder 2 became many changes which I will post very soon to this blog. Will keep you informed in the next days!

Here you can download sc_trans 2 BETA 6!

Here are the first infos of the new version. Next are following the next days!

Release Notes :: 2/3/2010 – sc_trans drop 6 version 2 revision 39

NEW STUFF:

- A new type of event as been added to the calendaring system that allows you to relay other stations. (see calendarxml.txt for more information)

- You can now create your playlists dynamically in real time. A new playlist entry construct will allow the invocation of an external program to fetch the next playlist entry (see docs.txt section 10)

- You can change the way your metadata is displayed in clients (this comes with lots of caveats though). See the new displaymetadatapattern conf file option (docs.txt)

- In order to encode your stream in mp3, you need an MP3 license key. This is a legal requirement to comply with all broadcasting laws. You can grab the code and pay the $5 license fee here:http://gc.digitalriver.com/store/winamp/en_US/pd/productID.165220700

- The conf file values unlockkeyname and unlockkeycode have been added to suport the MP3 broadcasting key.

- /writeconfig command added to web API. This will force the state of sc_trans to be written to the conf file (before it was only being done with sc_trans exited. See docs.txt)

- /timeshift command added to web API. This is very experimental and was added for the “We Choose The Moon” project at AOL. It allows extremely crude time shifting of the stream. (see docs.txt)

BUG FIXES:

- Shoutcast2 protocol changed for compatibility with sc_serv2

- Network timing fudgefactor defaults are now zero for compatibility with sc_serv2

- Special files always transfered on reconnect for uvox 2.1

- Fixed problem parsing conf file, where last line was missed if there was no cr/lf at end of file

- An empty main playlist will no longer cause the application to abort. It will just sit their quietly, mumbling to itself.

- VU Meter failure after internal restart fixed

- Better error reporting for shoutcast 1 protocol

- Unix warnings about missing priority playlist directory are now debug level warnings

- DJ data should be correctly escaped now.

- In adding the relay feature it was necessary to rewrite a large portion of the metadata handling. Hopefully the metadata will now change more reliably when switching between scheduled sources.

- Update title request had bad HTTP header line (how did I get away with that for so long)?