|
|
#1 |
|
Junior Member
Join Date: May 2012
Posts: 4
|
Shoutcast DNAS - Metadata Issue
I am having problems with metadata coming through to my Shoutcast DNAS server.
I am using a AudioTX Webstream encoder that supports Shoutcast V1 - it connects to the server absolutely fine and listeners can connect but I get no current song metadata being regsietered. I did get this to work once but seem now to be unable to get the correct config. Am i missing something in my config file (copied below!) password=***** adminpassword=***** yp2=0 srcip=********** dstip=********** portbase=8000 requirestreamconfigs=1 logfile=s:\\shoutcast\strongroom\sc_serv_MP3.log w3clog=s:\\shoutcast\strongroom\w3c\sc_w3c_mp3.log W3CEnable=Yes banfile=sc_serv.ban ripfile=sc_serv.rip maxuser=512 streamid=1 |
|
|
|
|
|
#2 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
where are you determining there is no metadata coming through?
also you appear to have set yp2=0 - is there a specific reason you've set the v2 DNAS to run in v1 mode (which i can say does have issues since it's not the main mode of the v2 DNAS). and thirdly is this meant to be a publically listed stream i.e. shoutcast.com or it is private? -daz |
|
|
|
|
|
#3 |
|
Junior Member
Join Date: May 2012
Posts: 4
|
Hi Daz,
I am looking at the webpage running on port 8000, also tried through VLC or winamp - it doesn't show the current song or station name information which is being put into the stream via the encoder. It has worked before so I am sure it is something I have got wrong in the config!! I was just trying with YP2=0 as the encoder only supports v1. This is currently a private stream but will become publically listed in the future. |
|
|
|
|
|
#4 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
are there title updates being reported in the DNAS's log file? as a lack of anything on the summary pages generally points to nothing coming through from the source. as there is nothing otherwise in the config which will have any effect on how titles are handled.
yp2=0 isn't needed even if you are using a v1 source as it will just connect on stream #1 which is the only way v1 sources are able to connect. -daz |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: May 2012
Posts: 4
|
There is nothing in the log files - but if I look back there was some time ago. The encoder end hasn't changed which is why I thought I had done something wrong in the config.
There is no ports or anything silly that needs to be open in order for this to work? |
|
|
|
|
|
#6 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
if the source is already able to connect then there's no other ports which need to be opened, etc.
as there's nothing showing in the log for title updates, all i can suggest is double-checking the source or see if they have any known issues with title updates failing after a specific time, etc. -daz |
|
|
|
|
|
#7 |
|
Junior Member
Join Date: May 2012
Posts: 4
|
Does this error help?
2012-05-28 15:28:40 E msg:[SRC 89.16.***.***:47574 sid=1] Remote socket closed while waiting for stream data |
|
|
|
|
|
#8 |
|
-
Join Date: Sep 2003
Location: UK
Posts: 22,278
|
not really as i've no context for it. it might be easier if you pm me a copy / link to your log and will see if anything jumps out.
-daz |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|