Getting sam broadcaster to work for DJs

[ridz]

Good day!

I have a streaming linux server where the shoutcast server and sc_trans is located. My default playlist is running on the server. I also have Dj accounts setup in the server.

Now i wish to connect to sc_trans from my local pc using sam broadcaster. My dj accounts doesn't work and it always say invalid password.

Connecting to sc_trans via winamp DSP works but in sam it doesn't.

I wish to have the default playlist in my server and dj login only if there is a live broadcast using sam broadcaster. How do i go about this? Please help. Thanks in advance.

[thinktink]

Change the DJ configs in the Transcoder configuration to the following:

djport=5000
djport2=5002

Then set SAM to the Legacy (v1) SHOUTcast encoding and connect to the v1 DJ port.

All v2 DSP broadcasters will change their port number to 5002.

There is no such thing as a "djport1" configuration option. And your DJ v2 port number is too close to and subsequently overlaps the DJ v1 port.

http://forums.winamp.com/showthread....60#post2856160

[ridz]

Great! It works! thank you very much thinkthink.

I still have one problem though, using sam broadcaster the "next song" in the current sam playlist is not updated in the server.

My site is using the xml from http://x.x.x.x:8000/admin.cgi?sid=1&mode=viewxml url to retrieve the next song to display it in my website. Checked the xml url the nextsong is not updated. How can i make sam to push or update the next song in the server? is that possible or i'm losing that feature if i'm broadcasting live?

Regards,
Ridz

[DrO]

a v1 source connection does not support the 'nextsong' value - that is specific to the v2 specifications. other than using a different source which supports all aspects of the v2 specification, the only other thing is to pester Spacial to add a user/name value to SAM so it can be used for DJ logins.


also where did the 'djport1' option come from as that is not in any of the documentation to my knowledge and is not supported in _any_ way.

-daz

[metal4radio]

I actually did "pester" them about it and had someone on the support run some tests. Outcome:
- SAM "supports v2" as in it would connect to the DNAS v2 (which doesn't need djname and password
- You can use v1 mode using dj and password in the password field like this -> djassword
- The issue has been forwarded to the developers and hopefully one of the next versions will support full transcoder v2 support

I got the feeling they weren't that aware of the difference between the DNAS and the transcoder. So let's wait and hope now

[DrO]

had thought we'd mentioned it but cannot find anything in my records. at least the v1 mode is known to work but does defeat the purpose of running with v2 based tools but seems like it'll be added at some point then - nothing works like customer interest to drive things being added

-daz

[eagleone99e]

This thread is quite old, BUT - I do have an answer for Ridz

There is a way to use SAM running in Shoutcast V2 mode on the encoder to talk to sc_trans. It has been a secret for some reason, and i have been all over Spacial to get it fully V2 compliant.

Here is what you do:

1. set up SAM encoder for Shoutcast V2 and make sure you have djport2 set up in sc_trans.conf
2. in sc_trans.conf set up the dj username as "encoder"

For some god awful reason the developers set the username of the encoder for V2 to pass ONLY the username "encoder".

So with that setup you can log into the dj port of sc_trans in full Shoutcast V2 mode.

hope this helps anyone who needs it.

[DrO]

it very much seems like it's only the 'pro' version (or whatever the top version is) that allows for connecting to sc_trans as a DJ when using SAM, everything below it seems to have been purposefully crippled (going on what people have been saying).

-daz