SHOUTcast DNAS 2 Beta (Build 19) 02/25/2011

[DrO]

Presenting the latest BETA drop of the SHOUTcast DNAS server for broadcasters, developers and testers. 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 BETA builds.

This BETA release is now available for the following platforms:

• Windows 32-bit and 64-bit versions) (Windows 2000 and up)
• Windows 64-bit (Windows XP64 and up)
• Linux
• Linux 64-bit
• Mac OS X (Intel)
• BSD 8.x

Downloads

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

• Windows (32-bit)
• Windows (64-bit)
• Linux (32-bit)
• Linux (64-bit)
• Mac OS X (Intel)
• BSD 8.x (32-bit)

Changes

Build 19 (02/25/2011):

• Changed password handling to not allow 'password' to be the same as 'adminpassword' with relevant checks on the per-stream passwords
• Changed Ultavox 2 Winamp clients (typically prior to v5.60x) to receive a v1 SHOUTcast stream instead of an Ultravox 2 stream to resolve missing stream titles
• Changed some of the reported details in the http headers used for SHOUTcast 2 (Ultravox 2.1) streams
• Changed the stream admin page to also report the user agent of the connected clients
• Fixed some more issues with password handling related to the changes in builds 17 and 18

Build 18 (02/24/2011):

• Added prompt for configuration file to load if one is not specified or there is an error loading the configuration file in non-daemon / service mode
• Fixed some admin options not working due to password related changes in the previous release e.g. prevented legacy client title updates
• Fixed loading issues on non-Windows versions related to the handling of the banned and reserved IP files

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 http://dev.winamp.com/wiki/SHOUTcast_Broadcaster


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.


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):

• 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)
• 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 being worked on.
• When connecting Winamp 5.60x to a v2 SHOUTcast stream when using the Bento or Big Bento skins will cause the Winamp UI to lockup for up to 60seconds (depends upon the machine, etc). Install http://download.nullsoft.com/shoutca...Stream_Fix.exe to resolve this issue (this patch will be shipped with the next version of Winamp after 5.60x)

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 - http://www.microsoft.com/downloads/e...d-3802b2af5fc2
64-bit - http://www.microsoft.com/downloads/e...4-157cfdffee4e


This new version has been tested on a number of current Linux versions (Ubuntu, Fedora, CentOS) so should hopefully run on other versions as well and without any dependency or locale related issues (as affected the first version).


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

• SHOUTcast DNAS 2 Beta (Build 17)
• SHOUTcast DNAS 2 Beta (Build 14)
• SHOUTcast DNAS 2 Beta (Build 13)
• SHOUTcast DNAS 2 Beta (Build 10)
• SHOUTcast DNAS 2 Beta (Build 7)

-daz

[MADxHAWK]

I ran into another strange thing.

I just took a look to my shoutcast Logfile and mention a lot of lines like this one here:

2011-02-23 19:27:41 I msg:[src 213.239.***.***:52945 sid=1] Shoutcast source connection.
2011-02-23 19:27:41 E msg:[src 213.239.***.***:52945 sid=1] connection denied. Bad password.

The IP of the source trying to connect is the IP of my server.

Currently im using build 7 again due to the titleupdate issue with sc1 protocol.
Strange thing, only 3 instance of shoutcast are running, one on port 8000, one on 8010 and the last one on 8050. There is no instance of sc_trans running or any other programm im knowing about that could try to connect to sc as a source.
Those connection tries appears aprox. every 15-20 seconds.
I realy have no idea what the hell is trying to establish a source connection to my shoutcastserver and i also have no idea how to figure out what is going on or what is trying to connect to my shoutcast on my server.

Any hints how i could figure out whats going one here?

Im running a Debian Lenny 2.6.26-2-amd64 system

Thanks again
Martin

[DrO]

[edit]
reverting to build 14 now should not be a problem with the release of build 18. build 17 was the current version at the original time of this reply being made.
[/edit]

build 7 is a bad one to use, i still think if you are going to revert to at least go back to build 14

i've seen things like that a few times myself and is usually from an IP going back to China and just seems like something is trying to connect to the DNAS blindly. other than adding it to the ban list and cycling passwords, there's not too much which can be done about random attempts for a source to connect. only other thing might be to enable some of the debug logging options to see what user agent and other details are noted about the attempt.

-daz

[MADxHAWK]

Hi DrO,

well the strange thing is, that the ip trying to connect to the DNAS, is the ip of my own server and not a unknown ip.
I have checked my server but didnt found anythin that could cause the conecction trys.

I will switsh to build 14 tomorrow and check again if the connection trys still persist.

greetings
Martin

Originally Posted by DrO

build 7 is a bad one to use, i still think if you are going to revert to at least go back to build 14

i've seen things like that a few times myself and is usually from an IP going back to China and just seems like something is trying to connect to the DNAS blindly. other than adding it to the ban list and cycling passwords, there's not too much which can be done about random attempts for a source to connect. only other thing might be to enable some of the debug logging options to see what user agent and other details are noted about the attempt.

-daz

[DrO]

Originally Posted by MADxHAWK

well the strange thing is, that the ip trying to connect to the DNAS, is the ip of my own server and not a unknown ip.

that is strange especially as the time between events doesn't match with any of the normal timeout values. maybe it's some other network activity which the DNAS is incorrectly interpreting as a source attempt. other than that, am a bit confused

-daz

[zetaf]

Originally Posted by DrO

that is strange especially as the time between events doesn't match with any of the normal timeout values. maybe it's some other network activity which the DNAS is incorrectly interpreting as a source attempt. other than that, am a bit confused

-daz

i can also confirm that my own serevr ip is trying to connect as source attempt 50 times although this from the older version on the previous build


also for the server access the logins are right.
just use root as username for login

for the both issues get fixed asap

[DrO]

zetaf: it doesn't matter about the server access now though confirmation from you that the lockup doesn't happen if the ban and rip files are removed would be good.

as for the attempts to connect as a source, i'm just not able to reproduce that at all - all i get are the random attempts from chinese IPs to connect as a client or as a source to my private test server.

the only thing i can think off is that it's possibly a sc_trans issue (i primarily use the Source DSP) so until i can get around to working with sc_trans again i don't believe the issue is the the DNAS and that is the focus of this thread and development at the moment.

-daz

[MADxHAWK]

Hi,

i have checked it again, here what i found out so far

2011-02-24 11:11:59 I msg:[src 213.239.***.***:45486 sid=1] Shoutcast source connection.
2011-02-24 11:11:59 E msg:[src 213.239.***.***:45486 sid=1] connection denied. Bad password.
2011-02-24 11:12:34 I msg:[src 213.239.***.***:45493 sid=1] Shoutcast source connection.
2011-02-24 11:12:34 E msg:[src 213.239.***.***:45493 sid=1] connection denied. Bad password.
2011-02-24 11:13:04 I msg:[src 213.239.***.***:45499 sid=1] Shoutcast source connection.
2011-02-24 11:13:04 E msg:[src 213.239.***.***:45499 sid=1] connection denied. Bad password.
2011-02-24 11:13:10 I msg:[src 213.239.***.***:45501 sid=1] Shoutcast source connection.
2011-02-24 11:13:10 E msg:[src 213.239.***.***:45501 sid=1] connection denied. Bad password.

There are only 3 instance of the DNAS running,
1st: Port 8000
2nd: Port 8010
3rd: Port 8050

There is NO instance of sc_trans running while this happens. so the connectiontries could not come from a sc_trans instance.
Netstat also shows theres something trying to connect, see below.

netstat -antp |grep 8000

tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8000 127.0.0.1:46636 TIME_WAIT -
tcp 0 0 213.239.***.***:8000 213.239.***.***:45501 TIME_WAIT -
tcp 0 0 213.239.***.***:8000 217.225.***.***:63458 TIME_WAIT -
tcp 0 0 213.239.***.***:8000 217.225.***.***:63459 TIME_WAIT -

but it looks like normal network traffic cause theres no pid given for the connection
(tcp 0 0 213.239.***.***:8000 213.239.***.***:45501 TIME_WAIT -
where the port matches the port from the last 2 lines of the DNAS Logfile)

I will now install build 14 and will chek if there will be the same problem. I will edit this post to report what happens

Greetings
Martin

[DrO]

thread now updated now that Build 18 has been released which fixes the lockup and password related issues.

as a note, i've left some of the posts from the build 17 thread in this thread incase they do apply to build 18.

-daz

[MADxHAWK]

Hi DrO,

first of all, thanks for the new release

I just installed the new build 18 of DNAS, but im sorry, ther's still no titleupdate on the DNAS statuspage and in winamp when im straming with SAM 4
The statuspage doesnt show anything and winamp only show something like
http://213.239.***.***:8000/stream/1

With shoutcastsourcedebug=1 the logfile only shows the folowing entries:

2011-02-24 17:11:02 I msg:[SRC 78.34.***.***:57173 sid=1] SHOUTcast source connection.
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [content-type:audio/mpeg]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-aim:NA]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-br:192]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-genre:Various]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-icq:NA]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-irc:#********]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-name:*******]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-pub:0]
2011-02-24 17:11:02 D msg:[SRC 78.34.***.***:57173 sid=1] icy header [icy-url:http://www.*****.de]

But there are no metatag updates, even if a new title is played.

Im using the same config like on build 14 where everything works fine with SAM.

Config:

log=1
shoutcastsourcedebug=1
screenlog=0
logfile=/home/stream/shoutcast/logs/dsl.log
w3clog=/home/stream/shoutcast/logs/dsl_w3c.log

banfile=/home/stream/shoutcast/control/sc_serv.ban
ripfile=/home/stream/shoutcast/control/sc_serv.rip
saveriplistonexit=1

maxuser=500
listenertime=0
autodumpusers=1

portbase=8000

;streamid=1
;streampath_1=/dsl

password=*****
adminpassword=*****
publicserver=never

yp2=0

Also i still got those mysterious source connections comming from my own server-ip

2011-02-24 17:32:06 I msg:[SRC 213.239.***.***:37051 sid=1] SHOUTcast source connection.
2011-02-24 17:32:06 E msg:[SRC 213.239.***.***:37051 sid=1] connection denied. Bad password.
2011-02-24 17:32:14 I msg:[SRC 213.239.***.***:37052 sid=1] SHOUTcast source connection.
2011-02-24 17:32:14 E msg:[SRC 213.239.***.***:37052 sid=1] connection denied. Bad password.
2011-02-24 17:32:33 I msg:[SRC 213.239.***.***:37053 sid=1] SHOUTcast source connection.
2011-02-24 17:32:33 E msg:[SRC 213.239.***.***:37053 sid=1] connection denied. Bad password.

I have started 3 instance of sc_serv with 3 different config files that are identicaly, only the portbase is different.

1. 192kbps DSL-stream Port 8000
2. 32kbps Modem-stream port 8010
3. Teststream Port 8050

There is no instance of sc_trans or streamtranscoder or anything else running, that might connect to DNAS as source.
What i mentioned is that these connectiontries only appear on the first instance running on Port 8000.
The other 2 instance on port 8010 and 8050 doesnt showing up those lines in their logfiles.


System: Debian Lenny 2.6.26-2-amd64 64bit
DNAS: Version 0.2.0.0 0.0.18.0/posix(linux x64)




Greetings
Martin

[DigiBC]

I've installed the latest build 18, but the reported problem still remains:

http://localhost:8080/admin.cgi?mode=viewxml&sid=1&pass=******

is asking for a password unlike build 14.

[DrO]

/me goes back to the drawing board... the password stuff had been working so i don't see why it's broken (again) *meh*

i can only hope that in the mean time that zetaf and maksimilian can confirm it's not locking up / not responding on loading whilst i try to re-fix things.

[edit]
Found the cause of the password regression!!!

DigiBC: what OS are you using so i know what test build to send to you?

-daz

[DigiBC]

@DrO:

Right now I'm using Windows XP x86. (Just in case I could also run a test with Windows 7 x64.)

[DrO]

DigiBC: k, check your pm's please

MADxHAWK: i've got 3 instances running on different ports like you've done and i just cannot get things to appear as you are. when i can i'll try the same on my Linux VM (am doing this on the Windows version at the moment) but i cannot see anything off hand which would be leading to what is being seen.

-daz

[DigiBC]

Yes, now it works again!

So I guess you are going to update the build 18 files now...

[DrO]

i need to get confirmation from MADxHAWK at least for a resolution of the SAM4 handling once i've run off a linux x64 test build. will roll an official update out as build 19.

-daz

[ghiooo]

Hello,
my server is debian 2.6.30-2-amd64 x86_64 GNU/Linux

the sources are winamp (latest) + dsp plugin (latest) on windows xp 32bit.

My experience with the earlier version, (17) the 32 bit and the 64 bit: after reaching a few hundreds of listeners, it was just crashing, i needed to relaunch the sc_serv.

With the latest, SHOUTcast Server Version 0.2.0.0 0.0.18.0/posix(linux x64)
still working fine, i noticed no errors until now.

I am always directing the logs to /dev/null because of the large amount of traffic

If i enable the ban file (v18), the server starts but will not be connectable, nor displaying the web ui. it happens the same if i activate the rip file, but only after i am reserving the desired ip, no web ui, not starting anymore.

i am waiting to see what's happening with v18. if it crashes again...

the old 1.9.8 is working perfect, supporting 10000 listeners without any problem.

thanks

my machine, if it helps:

Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
total used free shared buffers cached
Mem: 3956 388 3568 0 0 270
-/+ buffers/cache: 117 3839
Swap: 4682 0 4682
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller (rev 02)
01:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller

[DrO]

can you please edit your post so the sentences make sense as i'm currently struggling to follow what you're trying to say about the different versions.

-daz

[zetaf]

thanks works now but now theres issue

my server ip is listening to the source which is wierd, using dsp to tune in the radio but still my main server ip display on lsiteners ip
also theres issues that songs skips after 20 seconds when someone change the new songs
despite using modern, bento it still skips the song. Djs using the dsp get diconnected and connected whn current songs ends
this occur alot with djs and listeners, when using 128kps and above it lags alot for listeners and it frequently disconnects the djs dsp despite using all winamp skin. Some reason when next songs play it will skip ahead of 20 seconds of the song
and i got huge huge log showing socket error while waiting connection reset, is that normal, the logss is up to 2 GB, i did enable it just to see if radio was working.

the reconnection happend so many times that winamp frequently crash
2011-02-24 14:30:04 Logging starting
2011-02-24 14:30:25 Reconnecting [0]
2011-02-24 14:30:25 Connecting
2011-02-24 14:30:25 Cipher Response received
2011-02-24 14:30:25 Receiving Authorization Response
2011-02-24 14:30:26 Response received
2011-02-24 14:30:26 Sending Bitrate
2011-02-24 14:30:26 Response received
2011-02-24 14:30:26 Sending Buffer size
2011-02-24 14:30:26 Response received
2011-02-24 14:30:27 Sending max Payload size
2011-02-24 14:30:27 Response received
2011-02-24 14:30:27 Sending Flush
2011-02-24 14:30:27 Sending Standby
also got this

2011-02-23 19:27:41 I msg:[src 213.239.***.***:52945 sid=1] Shoutcast source connection.
2011-02-23 19:27:41 E msg:[src 213.239.***.***:52945 sid=1] connection denied. Bad password.

same as the other mmember and i dont have transcoder

[ghiooo]

well, after 1 hour of working fine, SHOUTcast DNAS 2 Beta (Build 18) crashed.

[DrO]

ghiooo: i still cannot follow your first post so would appreciate some clarification. as for the crash, is there anything in the logs at the time it happens or anything reported in the console to show what the error is or is it just a segfault error?

zetaf: have you got the SC2 patch for Winamp installed (link is in the first post).

i've seen a few people say there's issues with higher bitrate connections but i've not been able to reproduce it and that is the issue with any of the reports, not being able to reproduce the issues makes it tricky to fix.

so what versions of the DSP are they all using?

as for the random connection issue, i still cannot reproduce it though it seems that linux x64 is the only common thing between what is being seen though as you're using the non-test version, it's possible the test version i've sent to MADxHAWK might resolve it. the only thing i can now think off which could be causing it might be the moving of when the ban and reserved ip's are checked (as had to be done to allow for per-stream handling).

i guess i've got more work to do which puts back any fixes for the transcoder again *shrugs*

-daz

[zetaf]

all djs are using dsp 2.1.3

and heres my djs reply on the skipping broadcast

http://forums.winamp.com/showpost.ph...90&postcount=6

hope the testversion solves the issue

[zetaf]

also would it be possible to show at least 100 songs in song history since showing 10 songs in history is just too short

[DrO]

Originally Posted by zetaf

hope the testversion solves the issue

it resolves the issues build 18 was meant to resolve with the password and title sending from legacy clients (so that's the main thing). however i'm trying to see what i can reproduce (now i've had some sleep - so i should be a bit less grumpy now).

Originally Posted by zetaf

also would it be possible to show at least 100 songs in song history since showing 10 songs in history is just too short

http://dev.winamp.com/wiki/SHOUTcast...#Miscellaneous - songhistory option.

-daz

[MADxHAWK]

Originally Posted by zetaf

also would it be possible to show at least 100 songs in song history since showing 10 songs in history is just too short

I worte a php-script that runs every 60 sec. via a cronjob and stores the the songhistory for the last 48hours in a mysql db. The script depends on the phpbb3 forum and uses some of it funktions but should be simple converteted to run as standalone version. If you are interested i can send the script to you

cheers
Mad

[DrO]

thread now updated now that Build 19 has been released. will filter out build 18 specific posts over the weekend to keep things to just the new build.

thanks to MADxHAWK and DigiBC for confirming the fixes and additional testing

-daz

[lyov]

Hello after update new version it don't want to start this is my server log(server is ubuntu 10.04 23bit)
msg:*******************************************************************************
2011-02-26 05:20:45 I msg:** SHOUTcast Distributed Network Audio Server (DNAS)
2011-02-26 05:20:45 I msg:** Copyright (C) 1999-2011 Nullsoft, Inc. All Rights Reserved.
2011-02-26 05:20:45 I msg:** Use "sc_serv filename.conf" to specify a config file.
2011-02-26 05:20:45 I msg:*******************************************************************************
2011-02-26 05:20:45 I msg:[SHOUTcast] DNAS/posix(linux x86) v 0.2.0.0 b 0.0.19.0 (Feb 25 2011) starting up...
2011-02-26 05:20:45 I msg:[MAIN] PID: 5988
2011-02-26 05:20:45 I msg:[MAIN] Loaded config from sc_serv.conf
2011-02-26 05:20:45 I msg:[MAIN] Calculated CPU count is 4
2011-02-26 05:20:45 I msg:[MAIN] Starting 4 network threads
2011-02-26 05:20:45 E msg:Connection timed out
2011-02-26 05:20:45 I msg:[MAIN] Terminating sources
2011-02-26 05:20:45 I msg:[MAIN] Waiting for final YP remsrvs
2011-02-26 05:20:45 I msg:[MAIN] Runner shutdown
2011-02-26 05:20:45 I msg:<***> Logger shutdown

[DigiBC]

Everything works fine now!

At least I've found no new issues (in combination with DSP Plug-in v2.1.3 for Winamp).

@DrO: Great job! And many thanks for the regularly updated documentation.

Can we expect a final release soon or are there still plans for some major changes to SC2 architecture?

[DrO]

lyov: that's very strange as it looks like there's a complete failure to access any of the sockets on the machine. might be an idea to make sure no other instances of the DNAS are running and send me a copy of your configuration file(s) please. also do you have anything in the ban and rip list files?

DigiBC: there might be some other changes made to the v2 protocol (which shouldn't affect current clients as only sc_trans and dsp_sc are using the newer v2 protocol). but otherwise it's just some minor bug fixes against the DNAS before it's moved to stable i believe.

-daz

[lyov]

Hello DrO I solve that problem it connected with server hostname. Thanks again and when will release new sc trans?

[DrO]

Originally Posted by lyov

when will release new sc trans?

when it's ready as development on the newer sc_trans is taking longer than i'd like.

-daz

[peppert]

i think somebody deserves a cookie!

[DrO]

not with the way my tummy has grown off late, heh

-daz

[MADxHAWK]

Hi, found another small bug?

I mentioned that the xmlpage sometimes throws an error like "Not well formed data" (translatet to english). This error appears when shoutcast received a metatag containig specialchars like the german ä, ö, ü, ß or frensch é or è for example.
This error might appear only on Metatags that doesnt support UTF-8 encoding (early ID3v2 for example)

Maybe thers a way to fix it, cause most statscripts to document the listenercount call their data from this xml file. The problem is caused by the songhistory in the xml, cause the xml throws that error, as long as the song is listed in the songhistory adn you dont get any data for your stats-script. Even firefox shows that error if you call the xml page.

Maybe you could add a search and replace function that replaces non utf-8 characters with utf-8 like str_replace on php?

greetings
MAD

[DrO]

hmm, those characters are covered by utf-8 encodings so there really shouldn't be an issue like that happening. i know there's some quirks with the Source DSP not converting things correctly which might be part of the cause (can't remember what source you're using, heh) that i've got fixed for whenever i make a new public version of it.

then again, the DNAS is generally working in utf8 for what is holding the xml output so there shouldn't be any issues happening. can you confirm which page actions it is that you're seeing the issue on so i can just target those pages please.

-daz

[MADxHAWK]

Hi Daz,

currently thers still running build 14. I didnt found the time to update to the latest version cause my station is back on air again

The page caused that error was ../admin.cgi?mode=viewxml&sid=1 and the metatag was
Mark Knopfler - Rüdiger
In the generated xml file the ü was displayed as something like this: »

It seems like not all metatags cause this error. Mybe it depends on the ID3 Tag version the file was tagged with?

-MAD

[DrO]

i've just changed a test file to have artist - title as 'Mark Knopfler - Rüdiger' and then using Winamp + Source DSP (both 2.1.3 and the dev version) and it's showing what i'd expect to see on that page.

i've done this all against build 19 and also my development version so unless it's something with the source file, it points more at the stream source. maybe you can send a small test file with a tag set like you're experiencing the issue with as my copy+paste may not be reflective of what you're seeing.

-daz

[MADxHAWK]

thx Daz, will try to find a small file where that error occures and will send you a downloadlink via pm when i have found one.

Greetings
MAD

[DrO]

if you can do that (preferably the sooner the better) then that'd be much appreciated

-daz

[MADxHAWK]

Hi,

i have changed a jingle of our station to reproduce the error.

XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: http://192.168.6.30:8000/admin.cgi?mode=viewxml&sid=1
Zeile Nr. 2, Spalte 2168:
.....<TITLE>........ Musikgeschichte ￿ � �</TITLE>
----------------------------------^

XML- Parsingerror: not wellformed address: http://.......

Sent you a download link via PM

-MAD