SHOUTcast DNAS 2.4.7 (Build 256) 31st March 2015

[DrO]

This build is our new update and introduces new features as listed in the “Changes” section below, as well as addresses bugs reported in the previous build. It is recommended to update to this build as soon as possible over any previous DNAS builds being used due to the stability, security and other compatibility improvements it provides.

This release is now available for the following platforms:

• Windows 32-bit (Windows 2000 and up)
• Windows 64-bit (Windows XP64 and up)
• Linux
• Linux 64-bit
• BSD (8.x)
• Raspbian (Raspberry Pi - works on RPi A/A+/B/B+ and RPi2 with the same compile!)
• Mac OS X (Intel)

Downloads

You can download the updated version of the DNAS from the main download page here for all of the supported versions.


Changes

See http://yp.shoutcast.com/v/2_4_7 for all changes in this release (there's a lot in the ~5 months since the last release!)


Getting Started

If you already have a running instance of the 2.x DNAS then there should not be any issues with replacing your current version with this new version.

If this is a new install then make sure to read through the information in 'Readme_DNAS_Server.html' and the related documentation as well as considering using the setup mode which should make it easier to get started over all prior 2.x builds (and 1.x based releases).

Finally, all current copies of the documentation are included with the installer / archive and is the recommended point of reference for this release. The information found online at http://wiki.shoutcast.com/wiki/SHOUTcast_Broadcaster for the DNAS server only relates to the build 29 release (this will be updated shortly).


Reporting Issues

If you do come across an issue with the DNAS, then please do post in this thread with as much information as possible about what you're doing at the time, the system you are using and anything else which will make it easier to understand what is or isn't going on with your install.

Posts relating to authhash management issues will be ignored as this is not the thread for posting such issues. The correct thread is here.


Known Issues

The following are known issues or known changes which may have an impact when using the current 2.x DNAS release:

1. The advert and metrics code (when enabled) is new so there may be some minor issues so keep a look out for updated DNAS versions! Most if not all known issues are fixed as from v2.5.x onwards.
2. Any existing setup using the experimental 'streamportlegacy' option will need to be updated to use the official multi-1.x source support due to this option having been removed.
   
   This is only expected to affect a small number of Centova based setups where multiple streams are being provided (Centova were informed of this change ~2 months before this release)
3. With some specific setups when using the SHOUTcast 2.x protocol for all broadcasting stages, Winamp 5.6x listener connections may stop playing after a few seconds before eventually timing out (usually after ~30seconds). This should not affect listeners using the 1.x protocol / plain HTTP connections i.e. most listener connections are not affected.
   
   This has only been reported in a few cases so far (28th April 2015) and has now been internally fixed (14th April 2015) for the next DNAS release.
   
   The recommended workaround for those who experience this issue is to change the source to connect using the 1.x source protocol until a fixed build is made available.
4. When using sc_trans as a source and it provides specific 'coming next' titles (usually starting with "nextsong"), the DNAS will generate "Title update rejected - value not allowed" errors. These are generally non-critical errors and changes will be made for the next DNAS release to better help determine true title rejections vs intentional rejections.
5. In some cases, the usage of punctuation characters in passwords can lead to the DNAS rejecting attempts to login to the DNAS or to accept 1.x source connections (including related 1.x-style title updates). This issue is being looked into and should be resolved for the next DNAS update. (Impact appears to be low due to this only just coming to our attention)
6. If running multiple streams on the same DNAS without a specific streampath set and just an empty config item for this value and there is no stream #1 active, then it is possible for the YP to reject the attempt to list the stream(s). Explicitly setting the streampath value for all streams will resolve the issue (which is fixed for the next DNAS release).
7. For Windows builds, if the install path contains accented characters then the DNAS may not start. Running the DNAS from a folder without such characters will allow the DNAS to start (this is fixed for the next DNAS release).

Discussion about the previous version of the server including changelogs can be found in the following threads

• GM (Build 167 / 168)
• GM (Build 164 / 165)
• GM (Build 147)
• GM (Build 123)
• GM (Build 109)
• GM (Build 107)
• GM (Build 29)
• RC2 (Build 28)
• RC (Build 27)
• Beta (Build 18 + 19)
• Beta (Build 17)
• Beta (Build 13 + 14)
• Beta (Build 10)
• Beta (Build 7)

[DrO]

*new version bump*
this build is a much recommended update for all existing 2.x DNAS installs due to the functional improvements, stability and crash fixes, memory and CPU usage optimisations and related security fixes.

those who have been using the beta / release candidate builds over the last few months lead up to this release must update to this final release build as soon as possible (preferably before the end of April and ideally sooner than the end of the month).

[MRGrp]

Thank you for the great news DrO.

Would you please confirm if the Centova team has been involved during the testing phase of this new DNAS?
As we know, few months ago the DNAS update made us discover that there was an incompatibility between Centova Cast software and that DNAS version (streams were going offline every few minutes and randomly).
It would be great to know if that issue has been addressed now, and if this time Centova team was somehow involved, not to see again so many radio stations going offline.

Thank you again for your excellent job and great assistance.

Best regards,

MRGrp

[DrO]

they were contacted but never replied to our messages, so that's a no to your question and until you try the updated build, I don't know if it fixes your issue or not (as you were not able to run non-release builds which massively hinders trying to confirm bug fixes until it's far too late i.e. you then have to wait for another release if the issue is not fixed). though I suspect you won't be updating until Centova flag the update to you, so when you'll be able to try the update, I have absolutely no idea as it's out of control.


however, we have had people manually running the beta / release candidate builds under Centova and it's worked ok. it's only in cases using known issue #2 that there may be an issue e.g. if using the Liquidsoap auto-dj solution they now offer with multiple transcoded streams going to the same DNAS. from the listed stations, we don't believe this will affect many stations.

in that situation, stream #1 will work but others will not and that requires config changes to the Liquidsoap setup. i've been advised by one tester that it's a relatively simple config change to make in the Liquidsoap config files to correct the issue so it will use the now officially provided method to accept multiple source connections via the 1.x protocol instead of the experimental feature which has now been removed (as it was not intuitive and the new way is better and far easier to make use off).

[MRGrp]

Thank you for your prompt reply DrO.

I opened a ticket asking to the Centova Team for their recommendations.

In fact, as a Centova Cast customer, I would expect them to work on this matter together with your team.

Yes, I installed theDNAS few months ago was forced to roll back because I cannot have 16 radio stations going offline every few minutes, nor I can keep using a service open to the public to try new versions of DNAS letting the streams offline.

This is why I keep wondering why Centova is not actively testing such updates using some "dummy" installation... Live servers are not supposed to be used for testing purposes, or they can be and then, if things get weird, there is no other choice than rolling back and keep the service up and running.

Thank you again, I will certainly inform you if I get feedback from Centova.

Best regards

[DrO]

yet most issues only arise when running 'live' so if we cannot replicate issues under testing (as was the case with a number of the issues which were finally able to be fixed as part of this release), then it often does require having to install on a 'live' setup.

and yes issues can happen, but any of the builds we've sent out to people for testing could have been released as a 'final' build and so the line blurs on what is 'final' and what is not. i understand your point of view as it comes up all too often that unless it's on the main download page, it won't be touched. but then people also won't update unless they know an issue is definitely fixed and so an impasse arises.

however, it's best practice to get confirmation that a bug is fixed before pushing it out to the greater number of users. hence the last 5 months of lots of testing that has been gong on with those willing to use builds not marked as 'final' but in most cases could have been released as one, is what has led to the lengthy changelog for this release (which is now more work than went into the 2.2 release which itself was a hefty update compared to prior releases).

[stillcut]

Awesome fixes listing !

But I cannot find the way to properly upgrade the DNAS. This is my my fisrt upgrade ...
I hope you can guide me !

[neralex]

stillcut, if you are using allready DNAS 2.x then download the new package and overwrite the sc_serv file on your server. After that restart it - done! If you are using a playlist-management software you should restart it also after the restart of the sc_serv file to let reconnect it.

[Bryon Stout]

Thanks DrO.

Off to the centovacast forum now to see what they have to say.

[stillcut]

Thank you Neralex for your help.
I'll try to update during a night in the next few days.
Hope it will be ok.
I'll give my feedback here.

[DrO]

stillcut: in addition to what neralex has said (which is how DNAS updates have always been done i.e. in-place update and just ensuring you restart it for it to apply - or stop first and then do things just to make sure), it's covered in the 'Getting Started Guide' as is included with the DNAS in the docs folder (section 3.5.1.1 to be specific) and as linked to from the readme file.

[neralex]

Is anyone out there with the same issue with this build? Got it on Linux 64-bit...

http://forums.winamp.com/showthread.php?t=380869

[Jmet]

DrO,

The Raspberry PI revision, is that only for the Pi1 or will that also work on the Raspberry Pi 2?

[DrO]

neralex: you and abides are the only ones I've seen report such issues and I've tried Winamp based listener connections to a number of the newer DNAS builds (as well as during the last few months of development) and haven't had such a situation arise. will likely follow-up with you directly regarding this issue over the next few days.

Jmet: I'm not 100% sure as I've only got original RPis (specifically v1.1 and v2.0 model B boards) and I don't have a RPi2 yet.

I'm sure I'd read somewhere that it should work but until I can try (as I think the build as-is will be able to leverage the multi-cores in relation to how the DNAS works in such setups), I was hoping someone who's got a RPi2 would be able to try it out and give some feedback about whether it does work or not.

[Jmet]

I was unable to execute sc_serv, I will gather the exact error tonight and will let you know. Thanks!

[merged]

Originally Posted by DrO

Jmet: I'm not 100% sure as I've only got original RPis (specifically v1.1 and v2.0 model B boards) and I don't have a RPi2 yet.

I'm sure I'd read somewhere that it should work but until I can try (as I think the build as-is will be able to leverage the multi-cores in relation to how the DNAS works in such setups), I was hoping someone who's got a RPi2 would be able to try it out and give some feedback about whether it does work or not.

The error I got was a simple "Cannot execute binary file", might be related to the fact that the Pi 1 & 2 use a different underlying archetecture?

[DrO]

i assume you've chmod'd the sc_serv file ? i guess I'll need to order an RPi2 sooner rather than later...

[seanbruno]

Noted that this release appeared and started the update process for the FreeBSD port this week.

The release for FreeBSD seems to be missing all the config_builder bits. Is this intentional? I didn't see an immediate answer in the release notes.

[DrO]

it was intentional.

[Jmet]

Originally Posted by DrO

i assume you've chmod'd the sc_serv file ? i guess I'll need to order an RPi2 sooner rather than later...

I will spend some more time with it this weekend hopefully and will let you know, thanks!

[seanbruno]

FreeBSD port has been updated for anyone looking to update and run the latest release via the ports/pkg system.

https://svnweb.freebsd.org/ports?vie...evision=383680

Reviews and comments welcome.


I note there is an armv6 RPI release. Is this a linux only architecture release?

[DrO]

Originally Posted by seanbruno

I note there is an armv6 RPI release. Is this a linux only architecture release?

its a specific build for use on the Raspbian distribution.

[seanbruno]

Originally Posted by DrO

its a specific build for use on the Raspbian distribution.

Let me know if there is a desire to get a freebsd armv6 version built. I can assist if needed.

[DrO]

there's no desire for doing that as that sounds super niche and is really not worth the effort on our part. it would make more sense to provide a sparc build again than what you've suggested. so thank you, but we'll pass on that one.

[DrO]

Originally Posted by neralex

Is anyone out there with the same issue with this build? Got it on Linux 64-bit... http://forums.winamp.com/showthread.php?t=380869

I've just updated the known issues as we've now found the cause of this issue (which is only affecting a few people as per the quoted thread) as it's a pat your head and rub your tummy type of bug which is now fixed for the next DNAS release. thanks go to neralex for helping with testing builds to fix the issue.

other reported issues are still being looked into and will advise those people involved once the issues have been triaged further / fixed.

Originally Posted by Jmet

I will spend some more time with it this weekend hopefully and will let you know, thanks!

did you have any chance to try it out or have any further information ?

[electroradio]

Our stream dosen't work with the 256'build at Radio.de (web Player) - try http://electroradio.radio.de/

[DrO]

from a quick check, the player request appears to be seen as a web page request on the root DNAS page and so it's getting a copy of that (i.e. a html page) rather than the stream.

if you can, you should try using an url for the player with the appropriate mountpoint e.g. /stream so that there is no confusion on what the request to the DNAS is trying to access.

[neralex]

electroradio, which streamlinks you sent to radio.de? i'm also listed on radio.de and i think it has nothing to do with the DNAS version, its only a question of your stream-urls.

[electroradio]

Thank you. my mistake...

[milosz]

Monday 4/13/15, I've put sc_serv 2.4.7 on my new Ubuntu 12.04 - 64 server, feeding it with sc_trans and it's all quite good. Stable, and good connection to YP.

I have abandoned the idea of using LiquidSoap or some other front end. The reason I wanted to use something other than sc_trans was so I could implement some compression & limiting in DSP, but as my program consists of a fixed rotation of MP3 files, I just applied processing to all the MP3 files and now use those 'pre-processed' files which have been adjusted to my needs.

Works fine. Fewer moving parts, too, than LiquidSoap or another front end, which is always good for stability.

So far, very happy with 2.4.7

The HTML player is not working.
Current code:

code:
<audio controls preload="none"><source src="http://shoutcast-host.com:8000/" type="audio/mpeg"></audio>

Can you change (update) to:

code:
<audio controls preload="none"><source src="http://shoutcast-host.com:8000/;" type="audio/mpeg"></audio>

I added the ";" char - it's working.

How this player working for other channels (mount points)?

[DrO]

in which browser is it not working for you ? as all of the ones tried prior to release would play without the need for the semi-colon with the current DNAS release.

it uses either the configured stream path or /stream/x/ (where x is the number of the stream). this is all covered in the docs provided with the DNAS on how to access / reference different streams running on the same DNAS.

Google Chrome 42.0.2311.90 m and Google Chrome 42 on my Android 5.1 smartphone.

Server patch is: http://my-server.com:8000/index.html?sid=1

[neralex]

Originally Posted by magoli

Google Chrome 42.0.2311.90 m and Google Chrome 42 on my Android 5.1 smartphone.

Server patch is: http://my-server.com:8000/index.html?sid=1

It works fine on my end with all browsers, aslo with your examples and also with android 4.x. But i have set a streampath as DrO recommended.

[ram130]

Originally Posted by magoli

The HTML player is not working.
Current code:

code:
<audio controls preload="none"><source src="http://shoutcast-host.com:8000/" type="audio/mpeg"></audio>

Can you change (update) to:

code:
<audio controls preload="none"><source src="http://shoutcast-host.com:8000/;" type="audio/mpeg"></audio>

I added the ";" char - it's working.

How this player working for other channels (mount points)?

Originally Posted by magoli

Google Chrome 42.0.2311.90 m and Google Chrome 42 on my Android 5.1 smartphone.

Server patch is: http://my-server.com:8000/index.html?sid=1

I have no such issues as well. Our radio plays fine with the current build. And on my Android 5.0 phone and Android 5.1 tablet.

[DrO]

quick update, there will be some changes to the handling of the HTML5 audio control with the next DNAS release (so none of what I'm saying is in 2.4.7) which will ensure there is a ; on the end (so the DNAS will fully treat it as a stream request - which using a streampath for stream #1 (and any other streams) will also achieve) as well as adding a ?nocache=xxx dummy parameter.

this dummy parameter is an attempt to work around Firefox caching paused / stopped streams even when you previously refreshed the page (which is apparently a long standing Firefox 'quirk' according to this).

and please remember, that this is just adding the default HTML5 audio control the browser provides onto the pages and so will vary in handling / appearance between browsers and is just provided as a quick way to check what the stream is doing at the time. for a fuller featured option which can be put into a more specific page (rather than the default pages from the DNAS), there are plenty of options including ths for those looking for something more.

[DrO]

ThunderRoll's posts have been split out to http://forums.winamp.com/showthread.php?t=381045 as the cause of the issue and the fixes needed have been determined.

[DrO]

the known issues have been updated due to recently found issues. the impact should be low (primarily due to it taking so long for issue #5 to be fully reported).

[1073WKCR]

Dro this will be my first update in the 5 years i have had my server can you help me.

[DrO]

without any knowledge of your existing setup (like if you're running the DNAS directly or using some management software / control panel), what you're intending to do, etc, it'll probably be best to email us (using the details in my signature) with all applicable information and advice, etc can then be provided from there once it's better known about your setup and requirements.

[Bryon Stout]

sorry for the lame question. Its been a while since I updated. Other than replacing the old version with new one, is there any other files I need to replace like the .pem file or anything else?