So basically a couple of sytax errors caused these problems. At last I looked at the virgin config file, and realized I had added a 1 to djport. I tried different ports and did port scans and realized that the legacy ports I selected were Closed, while the v2 port was open. It turns out that the sc_trans_dj.conf file uses the default ports: Then, I was able to connect a Shoutcast v2 source as a DJ, but not a v1 using SAM Broadcaster which has been discussed here. Changing it to id1=1 allowed sc_trans to connect to sc_serv and work. Simple config file errors: The default stream id in sc-Trans_nf is streamid_2=2 or something like that, which for my setup was wrong.
#Install dsp plugin for sam broadcaster 4.2.2 windows#
I was finally able to get sc_trans on windows working with sc_serv running on the same machine. I don't think sc_trans or SAM are at fault here, just some odd combination of "tech voodoo." Thanks again to all who are testing this. If I had physical access to the computer in Denmark I might find something that could cause the connection problem, however that's not going to happen so I have to work with what I've got. The server is physically located in Denmark if that makes any difference, while me and my FreeBSD server (working perfectly) are in the US. I have complete access to it, but not physical access, or I would blow up windows and put a "real" server OS on it! It's running WinXP SP3 with the firewall turned off. As other people have apparently had no problem using SAM with sc_trans on windows, it must be something specific to this particular machine. In my tests I tried 4.2.2, 4.9.0, and an older one (forgot which exactly.) None worked with the windows sc_trans, but on FreeBSD it's all fine. The issue with SAM is that most of the DJs have older (like 4.2.2 or below) versions of SAM, so I have to be able to accommodate them.
Thanks Daz and Thinktink for your research into this. Not much to go on, but I have no problem using Winamp so I know it works.
0 kommentar(er)
