This method works too you know :P http://www.makeuseof.com/tag/how-to-...our-usb-drive/
Announcement
Collapse
No announcement yet.
Shoutcast DSP Plug-in v2.3.5 for Winamp 5.6 & v2.4.0 for Winamp 5.9
Collapse
This is a sticky topic.
X
X
-
*If you have issues with Winamp, ensure you have the currently latest version Winamp v5.666 build 3516 & its patches that fix several issues
*To remove the currently dead Winamp online stuff, see here: removing online stuff
*If you miss the Autotag feature: Gracenote CDDB Autotag alternatives
-
-
Really? I was actually unaware that any version past 3.x could be installed to a portable device, and actually run. All of the setup and/or Registry integration actually prevented me from running Winamp on any comp that didn't already have it installed somewhere.
Thanks!--=> the SASS Man <=--
--> King of the Rock <--
Comment
-
-
Im not all too sure if it wont mess with an installed Winamp's settings or not though :|
I suppose it always might have to be opened from the .cmd file to force it to use the portable way, DrO might be able to weigh in on this, since if Winamp can use an ini folder then it does have some form of portable functionality in it already..*If you have issues with Winamp, ensure you have the currently latest version Winamp v5.666 build 3516 & its patches that fix several issues
*To remove the currently dead Winamp online stuff, see here: removing online stuff
*If you miss the Autotag feature: Gracenote CDDB Autotag alternatives
Comment
-
-
and these posts have what to do with the Source DSP...?
Winamp has been able to run without the need to use the registry for years, with more formal support added in 5.1x to run in an effective portable mode (as a number of the 2.x releases used the registry for information fyi).
the winamp.ini option to add/set is no_registry=1 in the main [Winamp] section which will then prevent registry writing and all that. and you can edit the paths.ini in the same folder as winamp.exe to have that able to control how / where Winamp will store its settings (subject to plug-in support i.e. a lot of old 3rd party plug-ins don't follow the API added in 2.9x to allow for this to work - even ones from the last few years!).
it's probably something which should be better supported than requiring people to find config options to manually set, etc such as via some sort of preference page or something like that.
Comment
-
-
I dont seem to be getting the Winamp Source DSP Plug-in (dsp_sc.dll) that looks like is supposed to be in the sc_serv2_win32_09_09_2014.exe that I got from http://www.shoutcast.com/BroadcastNow.
Winamp Options/Preferences/PlugIns/DSP doesnt see the plug-in, nor does the file (dsp_sc.dll) exist anywhere on my machine.
Comment
-
-
what Winamp version? as it only works with 5.6 and newer (and was mainly tested against the Winamp version in my signature).
Comment
-
-
you're not by chance running Winamp in its 'safe-mode'? if so then you'll need to disable that.
if it not, then you'll need to provide an info tool report for your Winamp install -> http://forums.winamp.com/showthread....161361#plugins and attach the generated zip to a reply.
Comment
-
-
Originally Posted by MGarber View PostI dont seem to be getting the Winamp Source DSP Plug-in (dsp_sc.dll) that looks like is supposed to be in the sc_serv2_win32_09_09_2014.exe that I got from http://www.shoutcast.com/BroadcastNow.
Winamp Options/Preferences/PlugIns/DSP doesnt see the plug-in, nor does the file (dsp_sc.dll) exist anywhere on my machine.
Comment
-
-
Doh indeed, had completely not twigged that was the DNAS link.
Comment
-
-
Just downloaded the latest version and so far I've not had any issues with it, even with WebJockey installed kludging the track info for stop set files. Certain file titles leak but at least now it's consistently sending the primary track metadata (the previous version did not except with manual title updates.) Seems like a very nice improvement.
Comment
-
-
not that i'm aware off (and if that changes or not i do not know either).
why are you "screwed" ? as all 2.x setups will accept a 1.x based source client (not preferred but it works) unless you're relating to a service which has been configured to only allow for 2.x source clients...? (as multiple 1.x source client support on DNAS 2.2 and newer does work apart from a lack of title update support on anything other stream #1)
Comment
-
Comment