View Single Post
Old 25th July 2011, 16:23   #1
Join Date: Sep 2003
Posts: 27,873
SHOUTcast DNAS 2 (Build 29) 07/31/2011

This build is our latest GM release candidate and introduces new features as listed in the “Changes” section below, as well as addresses bugs reported in the previous RC builds.

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
  • Mac OS X (Intel)
  • BSD 8.x


You can download the updated version of the DNAS v2 from the direct downloads for the operating system version you require:

Build 29 (07/31/2011):
  • Changed SHOUTcast 2 client header to show the DNAS's actual version instead of just 'SHOUTcast 2.0'
  • Fixed SHOUTcast 2 compatible clients only allowed to connect as a SHOUTcast 1 client (build 27 / 28 specific)
  • Fixed more config files being shown than allowed on non-Windows versions when no configuration file specified

Build 28 (07/25/2011):
  • Added listen.asx to the /listen* playlist options available (so now pls, m3u and asx are available on a stream)
  • Added detection of sc_serv.ini if no configuration file was passed on loading (detects v1 configuration files)
  • Added 'type=xml' parameter to the 'updinfo' action to allow for v2 style XML metadata titles to be manually done
  • Changed streampath handling to allow '/' to be used again (was disabled in build 27)
  • Fixed kicking of listeners failing to respond / taking multiple attempts to react
  • Other miscellaneous code changes, improvments and related documentation updates
  • Everything else listed since the first v2 beta release (build 7)

Getting Started

If you already have a running instance of the DNAS v2 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 'docs\getting_started.txt' along with the example configuration files provided in this new version which should make it easier to get started. Alternatively you should consider looking at the configuration builder which is included in the 'config_builder' folder.

Finally, all copies of the documentation can also be found online at

Reporting Issues

If you do come across an issue with the DNAS v2, 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.

Known Issues

The following are known issues with the v2 DNAS raised in previous releases but not currently fixed / fully confirmed as needing to be fixed (i.e. intended behaviour):
  1. If the external IP is bound to a different device than the primary on the machine then the server will not work as expected (e.g. eth1 instead of eth0). This can cause the YP to fail to see the stream correctly even when destip has been correctly specified with it usually testing against the main IP of the machine. This is fixed for the next public release.
  2. Listing a relayed stream when using the YP2 mode is known to not work and will return a 474 error code from the attempt to connect to the YP. Setting the server as non-public or using the v2 DNAS in legacy mode (yp2=0) will allow the stream to be listed but means you lose all of the YP2 features. This is fixed.
  3. Some characters in titles (usually below ascii value 32) will cause the DNAS to drop the source connection as the title is processed. This will not be changed in the DNAS and will instead require sources to ensure they send titles without invalid titles. The Transcoder and Source DSP will be receiving these updates soon.
  4. On non-windows versions, it is possible for the DNAS to crash with a segfault due to invalid or corrupted metadata updates. This is fixed for the next public release.
  5. Depending on the platform version used, the realistic upper limit of client connections is currently ~300 before the DNAS begins to struggle & / or crash randomly. It is recommended to set maxuser=300 and use an additional DNAS / relay if you want to serve the stream to more listeners. This is fixed for the next public release.
  6. Some client connections (predominantly those using the RTMP protocol) can cause the DNAS to crash due to incomplete handling in the DNAS of this protocol. The only solution is to determine the IP address of the connection and ensure it is saved to the DNAS's ban list or attempt to add it to the system's firewall for inbound connections not allowed (depending on the OS being used). This is fixed for the next public release.
  7. When using a v1 source connection and setting the DNAS to be listed, in some cases the now playing information will not appear on the site's listing and will just show 'Now Playing:'. This is fixed for the next public release.
  8. The w3c log output does not contain the appropriate header values and can also output blank lines in-between the lines in the files' output. This is fixed for the next public release.
  9. The in-stream metadata as well as intro files (if specified) will cause issues with some flash player implementations leading to the stream stuttering when played back such as once the intro file has been played. This primarily comes from how the intro file works and most flash player implementations not coping with variations in the mp3 stream data compared to dedicated media players which can re-sync to the stream data correctly. This is partially fixed for the next public release.
  10. Some configurations will appear to loose the authhash which has been specified for a stream or the authhash is generated and not recognised. This is due to the streamid configuration option not being correctly written to the configuration file by the DNAS. See on what is need to resolve this issue with the current release. This is fixed for the next public release.
  11. Non-Windows builds can terminate when receiving a metadata update from the source where it contains characters in the range of 128 to 160 with an error like the following shown:

    terminate called after throwing an instance of 'std::runtime_error'
    what(): XML parser error: not well-formed (invalid token) at line 3

    The work around is to remove those characters from the file tags or disable metadata updates or use a source which strips those character codes for you or use the Windows version of the DNAS. This is fixed for the next public release.
  12. If a / is not specified at the start of a streampath entry e.g. streampath_1=stream instead of streampath_1=/stream then the DNAS will only provide the first stream running on the server. This is fixed for the next public release.
  13. If running the DNAS in the Program Files folder on Windows and you do not have write access to the folder (e.g. due to UAC on Vista and higher), when selecting a config file on the command-line the DNAS may crash. The workaround is to run the DNAS in a different folder which has write permissions or specify the configuration file to use directly (drag + drop the config file onto sc_serv.exe or create a batch file e.g. sc_serv sc_serv.conf and run that). This is fixed for the next public release.

Additional Information

Windows versions of the DNAS v2 are built with a dependency against the Microsoft Visual C++ 2008 SP1 Redistributable Package. If sc_serv is unable to start due to a dependency issue then you will need to install the correct version of the package so it can run which depends on the version of sc_serv you are attempting to run:

32-bit -
64-bit -

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