SHOUTcast DNAS 2 Beta v0.1

[SC_faisal]

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.

Download Link >> http://download.shoutcast.com/beta/s...a_02232010.zip

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....hreadid=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.


Comments / bug reports / feedback / feature requests welcome and encouraged!

Thanks!
- Neil and the SHOUTcast team.

[Nick@ss]

Good news all round,

Well done and a big thanks to the Shoutcast team,

Im sure this will be a good discussion point.

[chuckeh]

Great news! Will test the new version asap!

[Greg_E]

#1- good
#6- good

YP2 #2 - good

Does this require a different encoder? For those of us that have paid for an encoder this could be a bit of a problem.

If it works with my current encoders, I can throw it on something and give it a test since I have a couple encoders that are not used, and assuming that it runs on Windows.

[smoothbeats]

No more support for 7.html stats? I have no complaints about XML stats, but it was nice having an option that didn't require hardcoding the admin password into data collection scripts.

[SC_faisal]

Originally posted by smoothbeats
No more support for 7.html stats? I have no complaints about XML stats, but it was nice having an option that didn't require hardcoding the admin password into data collection scripts.

7.html will be deprecated in SC_SERV2. We are trying to move towards standardized broadcaster server "APIs" and stats access. 7.html was a hack anyway. ;-)

f.

[chuckeh]

Good decision!

Stats faking was a massive problem to the old YP and I hope it can be fixed with new sc_serv forever

[caraoge]

Great :-)

[Brutish Sailor]

This is ironic, because I was JUST making a joke this day would never come 4 days ago.

1-3 = Mount points? Zien! No more running port 80 streams from root! Time to drop IC2.

[jaromanda]

What impact, if any, does DNAS 2 have on nsv streaming?

[bored_womble]

i have to say, at the moment a little underwhelmed .... hopefully being the first drop this is just the basics and much more to come.

BW

[SC_faisal]

Originally posted by bored_womble
i have to say, at the moment a little underwhelmed .... hopefully being the first drop this is just the basics and much more to come.

BW

Yep - this is only a 0.1 release... Would love to hear your feedback and wish list of what we should focus on for oncoming releases.

Let us know!
f.

[smoothbeats]

Originally posted by SC_faisal
7.html will be deprecated in SC_SERV2. We are trying to move towards standardized broadcaster server "APIs" and stats access. 7.html was a hack anyway. ;-)

f.

I would like to see a way to retrieve server stats without having to pull that giant XML feed. Our main reason for pulling stats from the 7.html file rather than XML is because of the amount of data transferred. For an instance of sc_serv with 100 listeners, this means the difference between 419 bytes (7.html) and 26kb (xml) per request, a factor of 60. Multiply this by 20 servers that are queried once every 2 minutes, and the difference in the amount of data transferred is staggaring.

7.html = 173MB/month
index.html (screen scraper) = 2.7GB/month
xml = 11GB/month

While this amount of data is relatively trivial compared to the amount of bandwidth used by the streams themselves, it still seems silly to transfer 11GB of xml data when 7.html was able to accomplish the same thing in 1/60th the amount of data transferred.

Perhaps an alternate xml feed with just basic stats?

[Brutish Sailor]

Ok, I guess it isn't really mount points.

In your example:

stream config example

This server is providing three different streams for my station, and is
also relaying my friend's station

streamid_0=2
streamauthhash_0=abcdef
streampath_0=/bitrate/128

streamid_1=3
streamauthhash_1=abcdef
streampath_1=/bitrate/64

streamid_2=4
streamauthhash_2=abcdef
streampath_2=/bitrate/24

streamid_3=5
streamauthhash_3=aaaabbbbcccc
streampath_3=/headbash/relay/extra
streamrelayurl_3=http://foo.bar.whatever:80/stream/1074


Ok so if you are not using mount points to connect stream to server for multiple streams/single server, Im guessing the server is set to recognize the streamauthhash, and sets that stream as a separate relay for multiple streams/single server?

[nradisch]

Sorry, I couldn't follow your question.

--Neil