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

lyov · 2nd May 2011, 11:58

1. now I can only stream to sc_tras use v1 mode.
2. I can't find that line in my sc_tras conf (I don't know what mode use sc_tras)

DrO · 2nd May 2011, 12:20

to use v2 mode to sc_trans you need to specify djport2 -> http://wiki.winamp.com/wiki/SHOUTcas...r_2#DJ_Support which once enabled then needs to be entered into the DSP and then it will allow connections to work ok and will be using the utf-8 encoded xml to sc_trans which should resolve the title issue. using v1 mode and trying to send utf-8 / unicode titles will never work nicely as the v1 specs never really catered for such things i.e. if it worked then it was more luck than by design (which the v2 specs resolve).

to enable v2 support from sc_trans to sc_serv, you need to set outprotocol on the encoder configuration to 3 as per -> http://wiki.winamp.com/wiki/SHOUTcas...etwork_Options (the sooner i get the sc_trans inherit mode sorted out and released then the better i guess).

so if using the v2 tools then it all needs to be working in v2 mode at all stages otherwise you will get the title and other issues that you've been seeing - it just doesn't help that the defaults in sc_trans aren't setup for v2 usage since it predates the release of the v2 DNAS *shrugs*

-daz

lyov · 2nd May 2011, 12:35

Now when I use djport2 for streaming to sc_trans when I stream utf-8 metadata sc_tras go down give this error

2011-05-02 17:32:01 E msg:[DJPROTOCOLUVOX] Message had invalid terminator, tossing and retrying
2011-05-02 17:32:02 E msg:[DJPROTOCOLUVOX] Message had invalid terminator, tossing and retrying
Segmentation fault

DrO · 2nd May 2011, 12:49

can send me copies of all of your configuration files please (including dsp_sc.ini for DSP) and i'll try to find sometime over the next few days to see what is going on).

-daz

lyov · 2nd May 2011, 13:00

ok! thanks.

mixx941 · 7th May 2011, 10:11

Hi, we're seeing a few issues with DNAS 2:

1) While testing DNAS 2 I missed that 7.html isn't available anymore, so when we switched over yesterday some of our scripts and monitors no longer work properly. I see that there is a replacement of /stats?sid=#, however that doesn't seem to be working and instead just gives the actual stream data.

2) Could I ask why accessing 7.html outputs the stream now instead of a static page either indicating the server is down or noting that 7.html was removed? I didn't realize this until it was too late, but after hours of scripts running every minute trying to access this page and getting stream data instead of stats it basically brought an entire server to its knees with tons of processes built up. I understand that the script is also to blame here, but I was under the impression that DNAS 2 was able to be backwards compatible and getting a never ending stream of data instead of a static page was unexpected.

3) I'm guessing this is related to the known issue mentioned in the first post, but sc_serv can't connect to YP:

Quote:

msg:[YP1] Connecting to yp.shoutcast.com
msg:[YP1] /addsrv error for stream 1. nak Cannot see your station/computer (URL: http://ip.ip.ip.ip:80) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache. retrying msg:[YP1] Connecting to yp.shoutcast.com
msg:[YP1] Request [http://yp.shoutcast.com:80/addsrv] failed. Retries exceeded.
msg:[YP1] Connecting to yp.shoutcast.com
msg:[YP1] /tchsrv error for stream 1. nak Generic error retrying

The IP that it shows there is the main server IP and not the one sc_serv is listening on. The srcip/dstip is an alias on the primary interface in FreeBSD. There is no NAT/firewall/etc, and the server seems to work fine other than the YP issue.

If it is the known issue of not working on IPs other than the primary, is there any ETA on when that might be fixed so YP will work?

4) Reloading the config file does not seem to be working as expected. If I change "maxuser" and reload (which is confirmed as reloaded in the log), the max listeners does not actually get updated in the running process.

5) This is a minor one, but when starting sc_serv with "daemon", the full path to the config file must be used. "./sc_serv daemon file.conf" gives

Quote:

msg:[CONFIG] Could not find `file.conf' - will now prompt for a config file to load

Whereas "./sc_serv daemon /home/user/shoutcast/file.conf" works fine.

We're running 0.2.0.0 0.0.19.0/posix(bsd) in yp2=0 mode on FreeBSD 8.2 amd64. There is no source client connecting; just relayserver/relayport to pull the stream.

Thanks very much in advance,

-Mark

DrO · 9th May 2011, 09:25

mixx941: #1 and #2 - the replacement of 7.html isn't in any of the publically available versions of the v2 DNAS and i was a bit premature in putting the documentation online (though was needed for some other things at the time). so that is why it's trying to provide a stream instead as that's the bahaviour where it'll try to provide the first stream configuration on unhandled pages.

#3 - i'm not sure but it probably is both of the known issues from the first post as you're using the v1 mode with the DNAS (i'm guessing to work around the relaying issues in v2 mode) and the YP is explicitly coded to check the IP of the DNAS matches the external IP of the connection being made. there is no eta on any of that being changed, etc.

#4 - there are some issues with the config reloading with the public build which have already been resolved in the development version i believe. so will have to see if the issue persists once a new version is released.

#5 - that shouldn't be showing that message for the daemon instance and should instead be closing immediately. i can't remember if i've already fixed that from some other config loading changes i've made to the dev version.

-daz

mixx941 · 9th May 2011, 10:47

Hi and thanks for the reply.

On the YP issue, if the DNAS is listening for clients on dstip is there a reason why the YP connection couldn't be made from that instead of the primary IP on the interface? The IP I was getting in the log when YP failed was not the IP that the DNAS is listening on, and as far as I remember this worked fine in 1.9.8.

The stats not being in the current public version without warning was unfortunate; I fought for quite a while trying to figure out what was happening with that

. Thanks for the info though.

Initially we were planning on continuing to use 1.9.8, however we migrated to a new server and the FreeBSD 5.x binary does not run on FreeBSD 8 even with the 5.x compat port installed. Actually, I should have tried it before but I just tried the binary for FreeBSD 4.x and it seems to work, so I guess that could be a fallback if v2 doesn't work out for us.

The main feature we're wanting is a working YP. The extras in v2 like mountpoints, YP2, and the much anticipated ability to reload the config are nice, but overall it doesn't seem to be production ready as of now?

Thanks again,

-Mark

MADxHAWK · 10th May 2011, 12:56

Hey Doc, i feel pain what should i do?

[ironic]What the hell we shoud do with all those infos you provide? [/ironic]

You didnt provide any information about possible errormessages, logfiles or your configuration. Should we start to guess what you already tryed?

-MAD

lyov · 17th May 2011, 13:42

Hello DrO,
Do U have some news about my problem ??

DrO · 17th May 2011, 14:11

lyov: sorry not had the chance with trying to get the authhash system back up and running. will let you know my findings when i get a chance.

-daz

salvation.tower · 18th May 2011, 01:21

Hi There,

I've been Running DNAS 1.9.8 for the last year or so, and finally decided to have a look at DNAS v2, I've upgraded the sc_serv and the
and couldn't find a specific fix, and am aware i also need to get a YP2 key to publish on shoutcast,

can you suggest any fixes and what i need to do to get a YP2 key???

msg:[SRC 127.0.0.1:4224 sid=1] XML parser error: no element found at line 1
msg:XML parser error: no element found at line 1

i can't figure out where is the xml file it is trying to read?? as from basic google search it is missing something from the file.

It is all running thru Windows Server 2003 R2 (Service Pack 2), Winamp 5.61, DSP Plug 2.2.1, and SC_Serv 2.0 build 19. I use the AAC+ encoder to stream as all of my music is from my iTunes Library in m4a format)

DrO · 18th May 2011, 10:16

salvation.tower: see http://forums.winamp.com/showpost.ph...0&postcount=48 for how to get an authhash.

as for the error, that doesn't have to be from a real xml file and can be related to an xml response from the source or when trying to output information from the YP responses. basically once you've got an authhash then we can look into seeing if the issue persists and / or if it's a bug in the build of the DNAS you're using, etc.

-daz

salvation.tower · 19th May 2011, 00:40

Thanks for the authhash DrO

the Station is now showing up on Shoutcast Directory, in V1 legacy Mode, (however it still wont broadcast in V2 Mode. and is also not passing thru the track info... )

What debug settings should i turn on (in the sc_serv.conf file) to try and figure out why it is not connecting in v2 mode??

some notes in the sc_serv.log are shown below (maybe i need to open another port??)

W msg:[YP2] Timeout waiting for data retrying

there are some UTF error codes but these are from Song titles with Accents in them e.g.

E msg:Bad UTF-8 code (69) at position 45
E msg:Failure converting filename to metadata Bad UTF-8 code (69) at position b
E msg:Failure converting filename to metadata Bad UTF-8 code (69) at position b

XML error

E msg:XML parser error: not well-formed (invalid token) at line 3
I msg:[DST 60.241.9.5:49316 sid=1] SHOUTcast 2 client connection closed (807 seconds) [Bytes: 5140666] Agent: `WinampMPEG/5.61, Ultravox/2.1'
E msg:XML parser error: not well-formed (invalid token) at line 3

Also how can we change the display name or tags for the station??? (or is this done in the backend now the yp registration on shoutcast went awol??

)

Thanks in Advance
Dave

DrO · 19th May 2011, 10:39

ok, you're going to need a newer v2 DNAS - i should have remembered the title handling issues with non-latin characters being able to cause xml failures.

though that doesn't explain why you're not getting things to work in v2 mode - have you changed the DSP to run in non-legacy mode when trying to connect to the DNAS when in v2 mode?

as for the changing of the station details, at the moment that would something for me to change for you like (like with the initial setup of the authhash).

alas i'm in the middle of some dnas changes so it'll be a day or two before i can give you something stable to try out.

-daz

salvation.tower · 19th May 2011, 11:52

thanks Dro,

i have to tick the v1 legacy mode in dsp to get it to connect, if it is untick (to make it run in v2 dnas) it disconnects all the time... and you get the errors i posted above...

I eagerly await the next build...

Dhol · 20th May 2011, 04:52

hi dro i have problem with dnas 2 i setup as you said in pm with key as well but when i connect winamp with edcast it say connected at 32 kbps etc but when i visit myserver.com:8000 it gives me error
"ICY 401 Service Unavailable icy-notice1:
SHOUTcast Distributed Network Audio Server/posix(linux x64) vFeb 25 2011
icy-notice2:The resource requested is currently unavailable" etc

can any one help me please ? i use winamp with edcast also lame mp3 etc thanks

thinktink · 20th May 2011, 06:18

Quote:

Originally Posted by Dhol

hi dro i have problem with dnas 2 i setup as you said in pm with key as well but when i connect winamp with edcast it say connected at 32 kbps etc but when i visit myserver.com:8000 it gives me error
"ICY 401 Service Unavailable icy-notice1:
SHOUTcast Distributed Network Audio Server/posix(linux x64) vFeb 25 2011
icy-notice2:The resource requested is currently unavailable" etc

can any one help me please ? i use winamp with edcast also lame mp3 etc thanks

I'm not entirely sure but I don't think edcast supports the new uvox/2.0 version SHOUTcast protocol (yet.)

DrO · 20th May 2011, 22:15

i thought edcast was removed / just source code / whatever jaromanda is doing with it though i'm only aware off two sources using the v2 protocol unless it's 3 if edcast does...

-daz

JatondaRadio · 23rd May 2011, 14:29

ok the yp2=0 doesn't work for me, it just crashed when I try to load the conf with that switch. But if I don't put it in I receive the 400 generic error. DNAS 2 is a total mess right now. The beta as is now should only be used for testing or development purposes, it is not stable enough to run a station smoothly, too bad I find out the hard way. Back to 1.9.8 for me

DrO · 23rd May 2011, 14:36

well that's a really useful error report in that you've not provided any useful information or example configuration or relevant log file contents (as is asked for in the first post of this thread with the request to provide all relevant information).

just setting yp2=0 if you've got things configured for yp2 mode will usually make the DNAS abort loading and will leave a note in the log file for that run explaining why it is doing it.

as for the 400 error, the log file would give a bit more information on what might be going on. if there is a legitimate issue in the DNAS then now is the time to fix the issue rather than waiting for it to come out of beta and then complain it's not working. so help me to help you please with the required information.

-daz

misha_fm · 23rd May 2011, 23:22

hi all
I've got a problem with track titles updating. I'm sorry if the problem was already discussed but I didn't find the answer on the forum..

I use DSP 2.2.1 [Build 099]. When I connect to DNAS 2.1.19 and the option "use winamp" for updating titles is checked - everything's ok, the title updates when next track begins. But when I uncheck this option, enter "some_title" in the field "now" and click "send update", the server recieves the XML-data with "some_title", that I've entered, but Winamp (and other programs) don't show my "some_title" and show the title of track that is being played in winamp.

Though, using DNAS 1.9.8, there's no such problem - the title updates in Winamp in both cases correctly, so when "use winamp" is not checked, it shows my "some_title".

DrO · 24th May 2011, 08:04

misha_fm: i've not seen that happening using that version of the DSP though it was developed against a newer version of the v2 DNAS so i've probably fixed things already for the next release.

-daz

daejin4u · 15th June 2011, 02:27

hi~

what(): XML parser error: no element found at line 1

help me...PLZ.. ^^

ubuntu 10.04 x64 + sc_serv2_linux_x64_02_25_2011.tar.gz
XP SP3 + shoutcast-dsp-2-2-1-windows.exe

==================================================================
cast@rush79:~/prog/local/sc_serv2$ ./sc_serv
2011-06-15 11:22:46 I msg:<***> Logger startup
2011-06-15 11:22:46 I msg:<***> version 0.2.0.0 build 0.0.19.0
2011-06-15 11:22:46 D msg:<***>
2011-06-15 11:22:46 I msg:*******************************************************************************
2011-06-15 11:22:46 I msg:** SHOUTcast Distributed Network Audio Server (DNAS)
2011-06-15 11:22:46 I msg:** Copyright (C) 1999-2011 Nullsoft, Inc. All Rights Reserved.
2011-06-15 11:22:46 I msg:** Use "sc_serv filename.conf" to specify a config file.
2011-06-15 11:22:46 I msg:*******************************************************************************
2011-06-15 11:22:46 I msg:[SHOUTcast] DNAS/posix(linux x64) v 0.2.0.0 b 0.0.19.0 (Feb 25 2011) starting up...
2011-06-15 11:22:46 I msg:[MAIN] PID: 2739
2011-06-15 11:22:46 I msg:
2011-06-15 11:22:46 I msg:[CONFIG] Choose one of the detected config file(s) to load or enter `x' to abort this instance:
2011-06-15 11:22:46 I msg:[CONFIG] Note: Press `Enter' after choosing the config file desired.
2011-06-15 11:22:46 I msg:
2011-06-15 11:22:46 I msg:[CONFIG] [0] : sc_serv_basic.conf
2011-06-15 11:22:46 I msg:[CONFIG] [1] : sc_serv_simple.conf
2011-06-15 11:22:46 I msg:[CONFIG] [2] : sc_serv.conf
2011-06-15 11:22:46 I msg:[CONFIG] [3] : sc_serv_relay.conf
2011-06-15 11:22:46 I msg:[CONFIG] [4] : sc_serv_debug.conf
2011-06-15 11:22:46 I msg:[CONFIG] [5] : sc_serv_public.conf
2011-06-15 11:22:46 I msg:
2
2011-06-15 11:22:48 I msg:[MAIN] Loaded config from ./sc_serv.conf
2011-06-15 11:22:48 I msg:[MAIN] Calculated CPU count is 4
2011-06-15 11:22:48 I msg:[MAIN] Starting 4 network threads
2011-06-15 11:22:48 I msg:[MICROSERVER] Listening for connection on port 8001
2011-06-15 11:22:48 I msg:[MICROSERVER] Listening for connection on port 8000
2011-06-15 11:23:07 I msg:[SRC 10.101.10.11:4292] SHOUTcast 2 source connection.
2011-06-15 11:23:07 I msg:[SRC 10.101.10.11:4292] password accepted. Stream id is 1
2011-06-15 11:23:07 I msg:[SRC 10.101.10.11:4292 sid=1] stream configuration complete. [
type=SHOUTcast 2
mimeType=audio/mpeg
maxPayloadSize=16377
avgBitrate=128000
maxBitrate=128000
desiredBufferSize=320
minimumBufferSize=0
icyName=KPOP RUSH
icyGenre=pop
icyURL=http://rush79.com
icyPub=1
]
2011-06-15 11:23:08 I msg:[SRC 10.101.10.11:4292 sid=1] Got complete metadata message type=14594 id=77 span=1 content=
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<TIT2>Year Mandala</TIT2>
<TPE1>Ralf Bach</TPE1>
<TENC>SHOUTcast Source DSP Plug-in v2.2.1 099</TENC>
<TRSN>KPOP RUSH</TRSN>
<WORS>http://www.shoutcast.com</WORS>
<extension>
<title seq="1">Ralf Bach - Year Mandala</title>
<title seq="2">Delerium feat Joanna Stevens - Myth</title>
<soon>Delerium feat Joanna Stevens - Myth</soon>
</extension>
</metadata>

terminate called after throwing an instance of 'std::runtime_error'
what(): XML parser error: no element found at line 1
Aborted
cast@rush79:~/prog/local/sc_serv2$
===============================================================

XML parser error: no element found at line 1

cast@rush79:~/prog/local/sc_serv2$ cat sc_serv.conf
;DNAS configuration file built with the SHOUTcast 2 Configuration Builder

password=ilove7
adminpassword=ilove77
portbase=8000
requirestreamconfigs=1
yp2=1
log=1
screenlog=1
logclients=1
logfile=sc_serv.log
w3cenable=1
w3clog=sc_w3c.log
publicserver=never
banfile=sc_serv.ban
ripfile=sc_serv.rip
riponly=0
savebanlistonexit=1
saveriplistonexit=1
maxuser=32
listenertime=0

streamid=1
streampath=/listen1

streamauthhash=12345

radiocatholic · 15th June 2011, 03:51

Javascript Alert

The SHOUTcast2 Configuration was unable to locate or load
the help database.

This message I recieved when I open the crome html document. (cinfig_builder)

DrO · 16th June 2011, 09:33

daejin4u: i've replied to your pm's though you're going to need a newer v2 DNAS build to try out as there's some issues with the title handling in the current version of the v2 DNAS against certain characters.

radiocatholic: That generally happens if there's an issue with the config builder getting access to load local files via AJAX. as i've a feeling Chrome is far stricter in its handling of things than FF or IE, you might want to try the online version provided at http://bogproghome.hopto.org/config_...g_builder.html

-daz

lyov · 23rd June 2011, 21:13

Hello DrO,
Do U have some news about my problem ??

DrO · 23rd June 2011, 21:17

lyov: sorry i'd completely forgotten about it with everything else that's been going on. will try to find out the files you sent within the next few days (am a bit busy doing a few more important things for pending releases).

-daz

SugarD-x · 8th July 2011, 06:41

Quote:

Originally Posted by DrO

lyov: sorry i'd completely forgotten about it with everything else that's been going on. will try to find out the files you sent within the next few days (am a bit busy doing a few more important things for pending releases).

-daz

I'm running into the same issue with the Transcoder, so anything you can provide when you figure out what's going on with his would be immensely useful

DrO · 8th July 2011, 09:40

well now i've got the new Transcoder out and i know what i'm actually working against i'm going through the files which were sent at this moment so will see what comes off that (based against the current dev build of the DNAS which is effectively an RC for a public build).

i assume from what you've said that you've not necessarily tried it out with the new Transcoder yet?

-daz

SugarD-x · 8th July 2011, 09:49

I actually have myself. To be honest I think someone needs to update the config builder because I'm finding nothing but issues with it. The first error I got was the one I mentioned in my last post after modifying the default configs, now I'm getting another one in this topic after using the config builder, and it seems to be causing only legacy mode to work when DJ'ing on sc_serv2, which in itself is horribly bugged and doesn't always work. The sc_trans itself is just a mess, even with default configs. I'm guessing my error, and the poster's, are all caused by a lack of simple config documentation examples of a full config. The default ones work, but not very well, and with the builder causing bugs, I'd recommend a new builder be made. Even using the examples in the documentation doesn't seem to help much, and it takes a lot of searching in both the text documents and the wiki just to come up with anything helpful unless you REALLY know what you are doing. The config system already isn't very user-friendly...and that's coming from a guy who used sc_serv version 1.9.8 for years. Maybe an example of a config for sc_serv2 and sc_trans listing every option (even if turned off or disabled) with default values in one file would be a good idea since there's some obvious confusion between the various documentations

DrO · 8th July 2011, 10:05

the config builder was updated for this release to move things around to make it simpler to get to certain parts that were otherwise down the bottom of the page. the main aim of the default config builder setup is to make DNAS setup simpler with eventually (as time allows for me) to get the Transcoder setup experience improved (hence some aspects like auto-filling of playlist and dj names in the event's option which i just didn't have the time to finish off which i think should alleviate some of the pain of adding events with the config builder.

however, this is one of the main reasons for the new 'inheritconfig' mode which was introduced with the new Transcoder build as it removes the need for specifying most of the config options in the Transcoder that people have been having i.e. what password or setting goes with what (which does make it easier to move between testing with a v1 and v2 DNAS as needed without having to have different main config files for the Transcoder).

i admit it doesn't help that the Transcoder is confusing (which is agreed on internally as well) and that's something on my todo list to try to improve in order to make it simpler to setup. one thing that is planned is in the auto-filling of the calendar.xml with playlist / dj / relay events from the main configuration file if not explicitly set (as a large number of people do forgot / don't know that needs to be done) which i think should alleviate a large number of the issues with trying to setup the Transcoder. but it's more a matter of time to get things changed and whether to drop features or completely change them and mess around with people's existing configurations which having the beta mo****r sort of allows for though in most cases, i don't think it's needed other than changing _0 to _1 for the multi-config options, it's just more of making the Transcoder work things out itself that is the biggest pain with it.

Quote:

Maybe an example of a config for sc_serv2 and sc_trans listing every option (even if turned off or disabled) with default values in one file would be a good idea since there's some obvious confusion between the various documentations

i need examples of what parts you mean if there's errors though i've tried to do my best to ensure that things between on and the other do match up. providing one massive config file is not what was wanted as part of the push for the complete documentation for the v2 tools unlike with the v1 files. the aim was (and is still being worked on) is to provide all information and then to have a simplified guide to get going with via reasonable configuration examples. as such the getting started guide is going to be re-done soon to improve that as well as going over the config examples again and ensuring they are more appropriate to what has been coming back from feedback (i love constructive feedback and being told what exactly is wrong with parts of the docs / examples). i guess it doesn't help that i set the level of what i thought people wanting to use SHOUTcast at too high a level.

so i guess i've failed completely in that aspect of trying to make it easier to use the v2 tools

-daz

SugarD-x · 8th July 2011, 10:31

You didn't fail man, and I understand, things are still in beta. Don't get me wrong, everything looks great, and the new options are amazing. You guys have great documentation, it's just finding it that is difficult for a user that isn't so concerned with specific features as much as just getting up and running. After making my above post, I actually somewhat found a list of what I was suggesting on your wiki. Seems someone updated it quite a bit compared to the SC2 included documentation: http://wiki.winamp.com/wiki/SHOUTcast_DNAS_Server_2

As for the config builder, I've noticed that on multiple computers I run into a few issues with using it locally sometimes. It doesn't mess up configs...I just notice that some things don't function correctly. Local issue, I know, but quite annoying. Maybe an executable GUI builder with a walkthrough setup would be more useful. Then users could run that if unsure on how to set things up, and anything extra they want to add after would just be a matter of editing the conf file like they do now. That would prevent a lot of confusion regarding existing or missing settings to get them started.

Another suggestion, I noticed you added a nice feature at some point that lets you pick your config file. Great feature, but why not make sc_serv2 and sc_trans into one application and just have it decide which features to run based on a config file? That would probably prevent quite a bit of confusion since the user would just need to pick a sc_serv2 or sc_trans file to load the features they want, similar to how the system already works for them separately.

DrO · 8th July 2011, 17:52

Quote: