Old 20th January 2011, 14:37   #1
DrO
 
Join Date: Sep 2003
Posts: 27,873
SHOUTcast DNAS 2 Beta (Build 14) 01/25/2011

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
  • Linux
  • Linux 64-bit (*)
  • Mac OS X (Intel)
  • BSD 8.x
* These are newly supported versions of the DNAS v2 as of this release.


Downloads

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

Build 14 (01/25/2011):
  • Improved handling of the mimetype reported by legacy mp3 sources to improve usage of v1 sources (maps more mimetypes to audio/mpeg as applicable)
  • Added /nextsongs?sid=# to show the next coming songs in an xml form (if known) when using a compatible v2 stream source
  • Added 'admincssfile' option to allow for using v1 DNAS / SHOUTcast 2 / custom css styling of the index.html and the admin pages (check documentation for usage)
  • Changed 'admin.cgi?mode=reload&sid=#' to also update 'password' and 'requirestreamconfigs'
  • Changed 'configrewrite=1' to not output 'include' on exit
  • Fixed Windows version logfile path generation if none or an invalid configuration file is passed (relates to change of default logfile path to %temp%\sc_serv.log in previous build)
  • Fixed Windows service not running and being identified as sc_trans in the system event logs
  • Updated some of the example configurations to resolve issues with platform specific path handling
  • Updated Configuration Builder to latest version

Build 13 (01/20/2011):
  • Added 'streammaxuser' to the stream configuration group options to allow for a per stream limit with 'maxuser' still ensuring a maximum client limit on the server
  • Added support for wildcards via the 'include' feature e.g. 'include=stream/*.conf' to allow for a specific file for each stream configuration on the server
  • Added a new 'admin.cgi?mode=reload&sid=#' mode to the administation support which will make the server reload its stream configurations by adding / removing / updating any streams on the fly where it can (unless '&force=1' is also passed) otherwise it will kick sources and clients as applicable
  • Added YP connection status on the 'Server Status' message on index.html and the admin page to make it easier to see if a YP connection on a public server exists
  • Added more information to the log generated to indicate if a YP connection has worked or not without having to enable debugging in the configuration file or completely cryptic messages
  • Added &page=5 additional param handling to the admin.cgi?mode=viewxml stats action to provide the currently held metadata of the playing song (amount of information depends on the source and what metadata it provides)
  • Added &page=6 additional param handling to the admin.cgi?mode=viewxml stats action to provide the currently known stream configurations (amount of information depends on the number of stream configurations specified)
  • Added Configuration Builder (see config_builder folder) as a graphical way of making working configuration files (in combination with forum user thinktink)
  • Now ships in linux 64-bit - is identified as 'posix(linux x64)' with the 32-bit version now identified as 'posix(linux x86)'
  • Changed YP2 connection failures to be reported more clearly instead of an obscure /yp/resp/updatefreq missing error or requiring 'yp2debug=1' to be enabled
  • Changed default location of the log file on Windows installs to %temp%\sc_serv.log instead of c:\sc_serv.log (resolves some issues on Windows Vista / 7 and write permissions)
  • Changed pvt_update(..) to not spam the logs when 'yp2debug=1' is enabled in the configuration file if a connection attempt to the YP2 fails
  • Changed http header checks to allow empty values from a 'key:value' pair to resolve some client connection issues
  • Changed the 'Server Status' message on the index.html and the admin pages to show 'There is no source connected or no stream is configured for stream #X' when the stream is not active or there is no source connected
  • Changed the reported configuration file on the index.html and the admin pages to be the base file loaded instead of the last included file if 'include' is used in the configuration files
  • Changed handling of v1 sources to autofill the aim, irc and icq entries with N/A or 0 as appropriate if not set in what the source sends to the server e.g. Nicecast on Mac
  • Fixed an api dependency issue preventing this from running on Windows 2000
  • Fixed /nextsong?sid=# to show the unescaped version of the <soon/> metadata tag if received from the source
  • Fixed clients trying to connect via Ultravox 2.0 (e.g. Winamp 5.5x and older versions) not being able to connect or causing non-Windows versions of the server to terminate incorrectly
  • Fixed logging not working when passing certain invalid configuration files
  • Fixed admin.cgi?mode=resetxml not working - now will reset <peaklisteners> and <streamhits> fields to mimick v1 DNAS handling
  • Disabled the <webdata/> block in the admin.cgi?mode=viewxml stats (as well as via the &page=2 additional param) for the time being
  • Disabled some of the admin.cgi?mode=viewxml stats entries not currently being filled in just to cut down on unnecessary bandwidth usage - better use use the &page=# option to get specific sets of stats instead of all in one go to keep bandwidth usage down
  • Updated documentation based on user feedback and related changes, added sc_serv_simple.conf as an ultra simple configuration example, minor other issues & changes made


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)
  • The /listen.pls action does not form a valid url if dstip is not specified leading to http://0.0.0.0:8000/ as the stream address which will not work
  • 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
-daz
DrO is offline  
Old 21st January 2011, 16:59   #2
thinktink
Forum King
 
thinktink's Avatar
 
Join Date: May 2009
Location: On the streets of Kings County, CA.
Posts: 2,947
Send a message via Skype™ to thinktink
Quote:
Added 'streammaxuser'...
WH00T!
thinktink is offline  
Old 22nd January 2011, 17:46   #3
maksimilian
Junior Member
 
Join Date: Jan 2011
Posts: 9
sometimes Current song: and Next song: just empty, how fix it? Use latest versions of shoutcast2 and sc_trans2. And how make it display full song name in Current/Next song (Artist - Title, not like now only Title).

Big Thx.
Sorry for bad english =(
maksimilian is offline  
Old 22nd January 2011, 18:52   #4
DrO
 
Join Date: Sep 2003
Posts: 27,873
thinktink: indeed

maksimilian: if the source doesn't provide the title information then the server will not show anything on the admin pages for those aspects - not something that can really be changed. however i know there are some issues with sc_trans not relaying on the information from sources i.e. if a DJ connects to it via the Winamp+Source DSP combination but that will hopefully be resolved with the next drop of sc_trans (hopefully before the end of the month).

as for the title, it currently uses what is passed as the title from the source (usually in the TIT2 xml metadata field if using a v2 source) though i suppose it could be expanded with an extra parameter on the current/nextsong url query to try to create a title which is more like what the clients connecting to the server will generate i.e.Artist - Title - Album (as Winamp 5.60x will do and fallback gracefully for what isn't passed / available from the source metadata). will have a think and see about doing that (as need to account for the handling of legacy sources for something like that).

-daz
DrO is offline  
Old 23rd January 2011, 09:19   #5
DigiBC
Junior Member
 
Join Date: Dec 2007
Location: Europe
Posts: 28
Private pages drop outs

There seems to be an issue with the private pages (so far I've only tested the Windows 32-bit version):

Unfortunately theses pages aren't available continuously, there are some short interruptions.
The following string is called by an ASP webpage, so that it leads to an error sometimes:

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


Btw: I'm glad that the special character issue in "NEXTTITLE" has been fixed!
DigiBC is offline  
Old 23rd January 2011, 10:26   #6
DrO
 
Join Date: Sep 2003
Posts: 27,873
DigiBC: maybe the page is being queried too fast or the DNAS is busy at the time and so by the time it gets around to responding the ASP aspect has timed out. if you look at the server logs, it should indicate (might need to enable some debugging options of web connections) if the page request was received and if it succeeded or not.

-daz
DrO is offline  
Old 23rd January 2011, 11:30   #7
DigiBC
Junior Member
 
Join Date: Dec 2007
Location: Europe
Posts: 28
Quote:
Originally Posted by DrO View Post
DigiBC: maybe the page is being queried too fast or the DNAS is busy at the time and so by the time it gets around to responding the ASP aspect has timed out. if you look at the server logs, it should indicate (might need to enable some debugging options of web connections) if the page request was received and if it succeeded or not.
Frankly speaking I don't think it's an ASP problem, because these interruptions do last for much more than a few milliseconds. (I've never had similar problems with earlier DNAS versions.)
When I open the above mentioned link in my browser I can reproduce the problem by simply refreshing the page. After several tries the browser will display an error: "XML Page Cannot Be Displayed".
DigiBC is offline  
Old 23rd January 2011, 16:08   #8
DrO
 
Join Date: Sep 2003
Posts: 27,873
with what i know i changed in the handling of that action (which was to remove information not filled) there's no reason for it to be acting that much differently between it and drop 10.

i've just spent the last 5 minutes manually accessing the page in Firefox and IE and i've not been able to see any failures occur (or when i've been using it for testing the state of things in the server as part of the drop 13 development). so i'm not too sure what to say at the moment though looking at the logs is about the only thing i can think off which might help to give an idea of what is or isn't going on.

-daz
DrO is offline  
Old 23rd January 2011, 19:15   #9
DigiBC
Junior Member
 
Join Date: Dec 2007
Location: Europe
Posts: 28
I've done another test with Windows 7 x64, but no private page problems (interruptions) occurred there...


Anyway, I've discovered a new problem:
On both operating systems - Windows XP (DNAS 32-bit) and Windows 7 x64 (DNAS 64-bit) - after installing as a Windows service it fails to run as a service.
The only error I can find in the Event Log:
code:
sc_trans msg:<***> logger could not open console
I've never used "sc_trans"...
DigiBC is offline  
Old 23rd January 2011, 19:27   #10
DrO
 
Join Date: Sep 2003
Posts: 27,873
i'll double-check the service handling though i did find something yesterday which had 'sc_trans' as the string so it's probably the same thing (is from sc_serv having parts derived from sc_trans).

-daz
DrO is offline  
Old 24th January 2011, 17:59   #11
DrO
 
Join Date: Sep 2003
Posts: 27,873
DigiBC: the service issue is from the change made to make the server work on Windows 2000 - same issue also affects sc_trans. as well the string which i had changed was related to this so should be sorted for the next sc_serv2 drop.

-daz
DrO is offline  
Old 25th January 2011, 05:15   #12
TiggaStyle
Junior Member
 
Join Date: Oct 2010
Posts: 23
Added a new 'admin.cgi?mode=reload&sid=#' yes yes

Thanks for that.
TiggaStyle is offline  
Old 25th January 2011, 21:06   #13
DrO
 
Join Date: Sep 2003
Posts: 27,873
Updated first post with changes and links to build 14

As well. i'll post a copy of the SC2 style css file soon (though anyone using Firebug or something similar can work it out anyway ).

-daz
DrO is offline  
Old 25th January 2011, 22:24   #14
DigiBC
Junior Member
 
Join Date: Dec 2007
Location: Europe
Posts: 28
Another big step ahead! Thanks a lot!

It's great to find additional metadata, but there's a little inconsistency in 'adminadmin.cgi?mode=viewxml&sid=#' now:
SONGTITLE and SONGHISTORY don't include the artist anymore, whereas NEXTTITLE still includes artist - songtitle.

Frankly speaking I would be prefer the old type of view including the artist (also for compatibility reasons).
DigiBC is offline  
Old 25th January 2011, 22:34   #15
DrO
 
Join Date: Sep 2003
Posts: 27,873
Quote:
Originally Posted by DigiBC View Post
It's great to find additional metadata, but there's a little inconsistency in 'adminadmin.cgi?mode=viewxml&sid=#' now:
SONGTITLE and SONGHISTORY don't include the artist anymore, whereas NEXTTITLE still includes artist - songtitle.
it's usually down to the source and how they provide things as i'm trying to standardise them. though if you use admin.cgi?sid=#&mode=viewxml&page=5 then you can get the raw data and form titles as needed that way.

generally the currentsong is just using the title (TIT2 field if working with a v2 source) whereas the nexttitle can vary as you're seeing - like the DSP will just grab the next title from Winamp in a pre-formatted method whereas i've made v2.1.3 provide the required metadata which leads to just the TIT2 value showing.

i've still to work out the best approach on what to do though i think it should all just be the equivalent of the TIT2 field for the next tracks as well but having a 'full' mode which tries to form the title as a client will get it (like was raised in maksimilian's post) though that then has issues with the next track support so i'm undecided.

it also doesn't help that v1 sources do it a different way but am sure will get something sorted in the end.

-daz
DrO is offline  
Old 26th January 2011, 16:50   #16
DigiBC
Junior Member
 
Join Date: Dec 2007
Location: Europe
Posts: 28
I got your point.
Nevertheless I would like to suggest not to drop features from the standard "viewxml" that have always been there.

Until now I had been able to use my old ASP page. And I was quite happy when the new feature NEXTTITLE was added, because only a simple modification was necessary. All required information was provided by the standard "viewxml".
Now I would need a new solution...

I guess it would be much better to implement changed types of metadata only with new "viewxml" pages (page=7 and so on) or in addition to previous types.
DigiBC is offline  
Old 26th January 2011, 17:01   #17
DrO
 
Join Date: Sep 2003
Posts: 27,873
Quote:
Originally Posted by DigiBC View Post
I would like to suggest not to drop features from the standard "viewxml" that have always been there.
nothing has been changed in the DNAS with the handling of the titles, it's the sources where the differences have happened and always existed when looking back at the older DSP and sc_trans handling in v2 mode. as such i'm working with what was previously set in place so as the DSP has been updated to pass on the metadata, you now just see the title and not a formatted song title as was the case (since the DSP just grabbed the title and never got the full metadata - which i think is better that it's providing that now).

however i will look to change the DNAS in the next drop so that it reports a fuller title for the currentsong based on the metadata it receives from the v2 source (so if that skips things then it'll just show what it can) so it's sort of consistent with what is shown for v1 sources and the next title aspect. additionally i've got to tweak sc_trans as that doesn't do the nexttitles consistently either. and that's not accounting for the Winamp ATF string having been altered which will mess up the nexttitles coming from there.

so it's not quite as simple as being down to the DNAS which is basically relaying the information coming from the sources which can do it in a number of ways. either way i'll look to standardise things at least with the official tools (can't do much about 3rd party solutions).

welcome to beta development

-daz
DrO is offline  
Old 26th January 2011, 23:18   #18
maksimilian
Junior Member
 
Join Date: Jan 2011
Posts: 9
can i hide the admin page? left access for some ip addresses only
maksimilian is offline  
Old 27th January 2011, 01:00   #19
jaromanda
Forum King
 
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,289
Quote:
Originally Posted by maksimilian View Post
can i hide the admin page? left access for some ip addresses only
admin page needs password - what's the problem?

Is it just me or are shoutcast users getting dumber?
jaromanda is offline  
Old 27th January 2011, 08:36   #20
DrO
 
Join Date: Sep 2003
Posts: 27,873
there isn't a way to disable the admin pages and i'm not going to change the behaviour for that. like jaromanda says, there's a password so as long as that is set to something hard to break then there shouldn't be a problem. or are you experiencing something specific which is why you've asked this?

-daz
DrO is offline  
Old 27th January 2011, 09:03   #21
maksimilian
Junior Member
 
Join Date: Jan 2011
Posts: 9
just didn't want show number of listeners
maksimilian is offline  
Old 27th January 2011, 10:02   #22
DrO
 
Join Date: Sep 2003
Posts: 27,873
as that page is what has been shown going way back, i'm not going to block access to it and also if your station is listed on the YP, it'll have knowledge of the number of listeners (as reported in the listen.pls) so the system is inherently setup to display such information.

-daz
DrO is offline  
Old 31st January 2011, 12:15   #23
Mixelito
Junior Member
 
Join Date: Jan 2011
Posts: 1
I would not update when connected to the data from Stream Title, Genre Stream, Stream URL listings in the 'My Station'. It has some setting that I can keep the connection data of the speaker?

Do not know if I'm posting my question in the right place.

Sorry for bad English.

Thanks.
Mixelito is offline  
Old 31st January 2011, 12:29   #24
DrO
 
Join Date: Sep 2003
Posts: 27,873
i'm sorry but i'm not entirely sure what you're trying to say. all i can guess at is something to do with the metadata from a source connected to the server not showing? if you can explain / show what you're trying to say then that might make it easier to understand.

-daz
DrO is offline  
Old 3rd February 2011, 08:10   #25
BornKillaz
Senior Member
 
BornKillaz's Avatar
 
Join Date: Jan 2010
Location: My Place
Posts: 109
OK, I cannot get this running on my server. In fact, I was only able to only get the first ShoutCast 2 build running and working. This one it does not work.

I always get:
Quote:
ICY 401 Service Unavailable
icy-notice1:<BR>SHOUTcast Distributed Network Audio Server/posix(linux x86) vJan 25 2011<BR>
icy-notice2:The resource requested is currently unavailable<BR>

And same goes for previous build:
Quote:
ICY 401 Service Unavailable icy-notice1:
SHOUTcast Distributed Network Audio Server/posix(linux) vDec 13 2010
icy-notice2:The resource requested is currently unavailable

And yes, I even disabled the firewall, but it still doesn't work.

I'm on CentOS. How am I supposed to use the new features and the latest builds without running in this issues? Any idea?

Thanks in advance.
Attached Files
File Type: txt log.txt (13.7 KB, 547 views)

<?php echo str_rot13("FUBHGpnfg QANF Ehyrf!"); ?>
BornKillaz is offline  
Old 3rd February 2011, 08:16   #26
jaromanda
Forum King
 
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,289
Quote:
Invalid authorization hash
there's your clue

Is it just me or are shoutcast users getting dumber?
jaromanda is offline  
Old 3rd February 2011, 08:39   #27
BornKillaz
Senior Member
 
BornKillaz's Avatar
 
Join Date: Jan 2010
Location: My Place
Posts: 109
Ups... I have to register somewhere, right?

<?php echo str_rot13("FUBHGpnfg QANF Ehyrf!"); ?>
BornKillaz is offline  
Old 3rd February 2011, 08:43   #28
jaromanda
Forum King
 
Join Date: Jun 2007
Location: Under the bridge
Posts: 2,289
Quote:
Originally Posted by BornKillaz View Post
Ups... I have to register somewhere, right?
or go private (I think)

Is it just me or are shoutcast users getting dumber?
jaromanda is offline  
Old 3rd February 2011, 08:49   #29
BornKillaz
Senior Member
 
BornKillaz's Avatar
 
Join Date: Jan 2010
Location: My Place
Posts: 109
Oh Ok! I'm reading the docs now!

Sorry to ask without reading them, but I was used to SC 1 and 2 has changed a lot.

Thank you.

<?php echo str_rot13("FUBHGpnfg QANF Ehyrf!"); ?>
BornKillaz is offline  
Old 3rd February 2011, 09:08   #30
DrO
 
Join Date: Sep 2003
Posts: 27,873
it's really not that much different over v1 - the main thing is the need for an auth key to registeron the YP if using YP2 mode (default behaviour). plus its not like the error messages aren't clear on what is going on.

also i'm somewhat confused why the log you've posted (which would have been better as an attachment as i've now changed it to) is back-to-front somehow).

-daz
DrO is offline  
Old 3rd February 2011, 09:15   #31
BornKillaz
Senior Member
 
BornKillaz's Avatar
 
Join Date: Jan 2010
Location: My Place
Posts: 109
Well, I'll complete all steps and hopefully will work... :S

In shoutcast transcoder endpoint I need to change it to Shoutcast 2 protocol right?

Thanks.

<?php echo str_rot13("FUBHGpnfg QANF Ehyrf!"); ?>
BornKillaz is offline  
Old 3rd February 2011, 09:19   #32
DrO
 
Join Date: Sep 2003
Posts: 27,873
it's best to do that just so everything is running in the same mode. the next drop of sc_trans is being changed so it can work that out automatically using a new 'inherit' mode where you can specify the sc_serv configuration file (still need to get it implemented but am hoping that will make it a bit easier to get a sc_serv2 + sc_trans configuration paired together).

-daz
DrO is offline  
Old 8th February 2011, 08:17   #33
TiggaStyle
Junior Member
 
Join Date: Oct 2010
Posts: 23
Next Question: On the end of ipV4, will Shoutcast be ipV6 capable ?
TiggaStyle is offline  
Old 8th February 2011, 21:51   #34
DrO
 
Join Date: Sep 2003
Posts: 27,873
Quote:
Originally Posted by DrO View Post
however i will look to change the DNAS in the next drop so that it reports a fuller title for the currentsong based on the metadata it receives from the v2 source (so if that skips things then it'll just show what it can) so it's sort of consistent with what is shown for v1 sources and the next title aspect.
have changed things for the next drop now so for v2 sources the DNAS will show 'artist - title' (if possible to work out from the received source metadata) for the currentsong.

is that ok or should it be 'artist - album - title' as is done with v1 client connections to a v2 stream? since as far as connecting clients go, they're not concerned with what is shown on the admin pages / xml report.

personally i prefer 'artist - title' as that matches my Winamp install and so the next track style will also match the style of the currentsong but am giving the option between one or the other.

-daz
DrO is offline  
Old 8th February 2011, 21:55   #35
DrO
 
Join Date: Sep 2003
Posts: 27,873
Quote:
Originally Posted by TiggaStyle View Post
On the end of ipV4, will Shoutcast be ipV6 capable?
no idea at the moment (not without looking into things properly) though i don't think it's as big an issue as is currently being made out of it all (but that's just my personal view).

-daz
DrO is offline  
Old 9th February 2011, 00:22   #36
Smelter
Major Dude
 
Smelter's Avatar
 
Join Date: Jan 2004
Posts: 1,141
Quote:
Originally Posted by DrO View Post
artist - title
perfect. db song by artist not album anyway.

Any word on copying the socket server process code to the sc_serv?
Smelter is offline  
Old 9th February 2011, 03:31   #37
zetaf
Member
 
Join Date: Jul 2007
Posts: 67
yeah my djs also prefer artist - title on current song
but can you also add feature to show current live DJ?
and despite applying those settings it wont show it on the radio page, the stream url
zetaf is offline  
Old 9th February 2011, 08:43   #38
DrO
 
Join Date: Sep 2003
Posts: 27,873
artist - title it is then

Quote:
Originally Posted by Smelter View Post
Any word on copying the socket server process code to the sc_serv?
at the moment it's unlikely to be for the next drop - have a load of changes i'm trying to get into the DNAS at the moment. when i've got something i'll pm you some test builds as i'd prefer to ensure it works before rolling out anything publically for it.

Quote:
Originally Posted by zetaf View Post
can you also add feature to show current live DJ?
if they're connecting through sc_trans then it's a known issue that it doesn't pass on the DJ metadata - i hope that's what you're referring to otherwise can you provide some more details.

-daz
DrO is offline  
Old 9th February 2011, 10:04   #39
zetaf
Member
 
Join Date: Jul 2007
Posts: 67
actaully refer to the winamp dsp plugin
zetaf is offline  
Old 9th February 2011, 10:16   #40
DrO
 
Join Date: Sep 2003
Posts: 27,873
you're going to have to explain things a bit more as usng the DSP will send the title information from Winamp or what has been set and sent via the 'Send Update' action in the track title options which to my knowledge is working correctly (with the current and with the next version of the DSP i've got to finish off).

or are you looking for something else as the SC system just uses titles so unless that is provided in what the source (DSP, sc_trans, etc) is sending then it won't appear.

-daz
DrO is offline  
Closed Thread
Go Back   Winamp & SHOUTcast Forums > SHOUTcast > SHOUTcast Discussions

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump