-
Thx @thinktink for the jnetlib libraries.
Adding zlib.dll in Shared folder fix the issue for meLeave a comment:
-
Hi,
Same issue for me.
KO : Winamp 5.9.0 build 9999 / Shoutcast Source DSP 2.4.1 build 444 / Shoutcast server 2.6.1.777
OK : Winamp 5.666 build 3516 / Shoutcast Source DSP 2.4.1 build 444 / Shoutcast server 2.6.1.777
It seems to be a global connection issue as I didn’t see any TCP connection out of winamp.exe (5.9.0) when tried to connect to Shoutcast server (tried localhost, 127.0.0.1, 192.168.x.x)
Same when I click on "check for updates" in DSP plugin "about…" tab : no TCP connection out of winamp.exe (5.9.0). button keep locked indefinitelyLeave a comment:
-
I've tried the DSP once more with a standard config, then again with all kinds of debugging added to the config (conf file attached).
This didn't seem to make any difference, it seems Shoutcast server doesn't receive anything from the DSP. I've also attached the DSP log.
I've added another screengrab that shows something else that cought my eye. When I check for any available upgrades from the DSP, it never completes the action. I therefore currently think DSP is not able to connect over the network for some reason.Leave a comment:
-
Gratifying to know that AterKast works but that was not my intention. It would be good to know what's causing the official DSP to not connect so that it can be looked at by the developers and given an opportunity to correct it.Originally Posted by davidvankemenade View PostLeave a comment:
-
I've just tried Afterkast and that worked straight away! I think I'll just stay with this, it does the job!
Many thanks for your help.Leave a comment:
-
Forgot to ask, did you enable logging in the DSP? If you can, attach the logs.Leave a comment:
-
I double checked your reported version numbers and by your report you are using the latest versions.
This is a bit baffling.
What changes, if any, did you make to the DNAS configuration file? Double check your listen bindings.
Try populating all of the "Output Configuration" details, even the fields that contain defaults, except for the DJ field. Change "Connect using:" from [Automatic mode] to the v2 mode.
As an experiment, try using AterKast instead of the official SHOUTcast DSP.Leave a comment:
-
Hi thinktink, thanks for looking into this. I'm using a physical machine, not a VM. You're right I used VNC for the screengrab, but this doesn't seem to influence the behavior.
I've tried to replace "localhost" with 127.0.0.1, the local hostname and my public IP address (with firewall switched off for a moment) but none of this helps.
I'm particularly puzzled that telnet sessions from the machine itself or from another one are logged by Shoutcast server, but the DSP plugin seems to do nothing in terms of connecting...Leave a comment:
-
From the screenshot I see you are using VNC, have the server and the DSP on the same port, and have not filled in the localhost IP address.
Are you running this on a remote virtual machine? If so, does the localhost virtual adapter exist or is it only getting a inter/intra-net adapter?
Try connecting using the other IP address.Leave a comment:
-
DSP plugin cannot connect to Shoutcast server
Hi all, I've just upgraded to
- Winamp 5.9.0 build 9999
- Shoutcast Source DSP 2.4.1 build 444
- Shoutcast server 2.6.1.777
I can't get the Source DSP to the server. All three reside on the same machine.
The Source DSP keeps trying to reconnect, but never succeeds. If I put in an imaginary server name or another password, it reacts in the same way.
The Shoutcast server doesn't seem to receive anything from the Source DSP. If I telnet locally to port 8000 and enter the password, I get connected straight away.
Does anyone have an idea what I'm missing? Many thanks in advance!
David
Leave a comment: