Shoutcast 2.0.0 compatibility

[PARALAX]

Hello!

I've some questions regarding the protocol compatibility of the new Shoutcast Server, SC-Trans and Shoucast DSP. Currently we're using Shoutcast 1.9.8 (implended over CastControl panel) and the old "SAM Encoder Plugin V3.8.3" with Southcast 5.35. As many of our DJ's are using Shoutcast DSP instead, I've planned to opgrade this when a stable release will be announced with our CastControl service. I also need to upgrade the Winamp version to 5.5 or higher as I've learned from the german shoutcast blog. Unfortunately there are no infos about the shoutcast script/protocol compatibility. As our webseite use many scripts written by our side developer, there are cunnetly routines which are getting the listeners, song titles, online status, AIM status, last played tracks etc which will displayed directly on the page. My worry is that some of this script has changed of removed for sc_trans2 or DSP 2 and I have found no further information of this.

Did already somebody test the current script functionality with old scripts like: http://xx.xx.xx.xx:8000/admin.cgi?pa...=updinfo&song= or something?

Currently we're using many scripts which use the Shoutcast V1 XML script language, for example:

Will this also work with Shoutcast 2.0 and DSP 2.0 and just adds new commands which must not be used?

Another question is, wether Shoutcast 5.5 or higher will be compatible with the "Oddcast song requester" and the "SAM2 plugin", SID Plugin, and some old Winamp 2/3 Plugins which we're still using now. Did anyone already use this plugins with Winamp 5.5 or higher?

Thanks you very much!

[DrO]

Originally Posted by PARALAX

I also need to upgrade the Winamp version to 5.5 or higher as I've learned from the german shoutcast blog. Unfortunately there are no infos about the shoutcast script/protocol compatibility.

the v2 DSP can be run in a legacy mode (i.e. able to connect to a v1 DNAS) which acts like the v1 of the plug-in though without all of the crashes, etc that have plagued it over the years.

Originally Posted by PARALAX

As our website use many scripts written by our side developer, there are currently routines which are getting the listeners, song titles, online status, AIM status, last played tracks etc which will displayed directly on the page.

most of that information is available as xml responses though it's likely you will need to change the scripts however i've not looked at what you've attached / other query scripts available so i'm not sure how much you'd need to change things. details on the externally queryable options can be found at http://dev.winamp.com/wiki/SHOUTcast...Administration

Originally Posted by PARALAX

Did already somebody test the current script functionality with old scripts like: http://xx.xx.xx.xx:8000/admin.cgi?pa...=updinfo&song=

that will work (once converted to the multi-stream version) though there's a bug in the current drop of the v2 DNAS (build 14) where it only works on the first stream irrspective of ths stream id specified - is fixed for the next build however.

Originally Posted by PARALAX

Currently we're using many scripts which use the Shoutcast V1 XML script language, for example:

Will this also work with Shoutcast 2.0 and DSP 2.0 and just adds new commands which must not be used?

the v2 tools generally add more information to the xml reported though there is a chance that some of the information is reported in a different way to the v1 tools (not having used v1 i really cannot say how it compares).

Originally Posted by PARALAX

Another question is, wether Shoutcast 5.5 or higher will be compatible with the "Oddcast song requester" and the "SAM2 plugin", SID Plugin, and some old Winamp 2/3 Plugins which we're still using now. Did anyone already use this plugins with Winamp 5.5 or higher?

that's the hardest one to answer as not knowing exactly the plug-ins being used (like how there's a few SID plug-ins which all work differently). basically the only way to know is to make a test install and see how it goes with the plug-ins. if there are issues then it's down to trying to find updates from the plug-in author or finding an alternative which does the same thing which works / is supported by the plug-in author. as long as the plug-ins aren't doing anything crazy in how they interact with Winamp (as a lot of older plug-ins for 2.x normally follow) then there's a reasonable chance things will work ok.

------------------------------------------------------

overall, if you're looking to go to v2, your best option is making a test setup to see how things work with the current versions available and see how things work (or not) as there is an effort to get the v2 tools out of beta very soon so the v1 DNAS will be deprecated so is as good a time to at least start on the test strategy for moving to the v2 platform

-daz