sc_trans relay ?!

[djavalon]

Hello,

We would like to have this configuration :

SAMCast (place1) -> SC_Trans (place 2 - one session) -> SHOUTCast (in a Windows' Service).

Everything work fine with the SHOUTCast because it use actually with 3 SAM Broadcaster.

We cannot connect SAMCast with SC_Trans and it is impossible to debugging it because there's no log between those two.

Here's our configuration :

code:
;Transcoder configuration file

;Made with the SHOUTcast 2 Configuration Builder



calendarfile=calendar/calendar.xml

calendarrewrite=0

streamtitle=....

streamurl=http://www.back2noize.com

genre=Techno

adminport=8080

adminpassword=....

adminuser=admin

inheritconfig=sc_serv.conf

unlockkeyname=....

unlockkeycode=....

logfile=sc_trans.log

;playlistfile=playlist.lst

shuffle=0



endpointname_1 = IP_PLACE2

serverip_1 = x.x.x.x

serverport_1 = 80

password_1 = ....

streamid_1 = 20

encoder_1=mp3

mp3quality_1=1

bitrate_1=128000

channels_1=20



serverip_2 = IP_PLACE2

serverport_2 = 80

password_2 = ....

streamid_2 = 21

encoder_2=mp3

mp3quality_2=1

bitrate_2=192000

channels_2=21



serverip_3 = IP_PLACE2

serverport_3 = 80

password_3 = ....

streamid_3 = 22

encoder_3=mp3

mp3quality_3=1

bitrate_3=256000

channels_3=22

code:
<?xml version="1.0" encoding="UTF-8" ?>

<eventlist>

 <event type="relay">

   <relay url="http://IP_PLACE1>

   <calendar/>

 </event>

</eventlist>

Is someone can help us on this one ? Because I do not understand why is it so complicate to active this service like that

Regards,
Avalon

[DrO]

my understanding is SAMCast is a source and not running as something like a DNAS (which is the only thing that relaying will be able to pull from) which most likely explains the issue (though i don't have the product so i don't know for certain).

for what you want to do, you'd need to be connecting SAMCast to sc_trans as a DJ connection and not a Relay connection (assuming it will allow you to do it as i know that with SAM Broadcaster there's been numerous issues getting sc_trans to connect to it as a DJ connection (generally involves connecting as a v1 source).

[djavalon]

Hello,

Thank you for your fast answer, this is exactly the information we have looked for ! We are using SAMCast because it provide a functionnaly called "HTTP Event Adaptor" that can change the metadata from HTTP requests. Like that we can :

1. Change metadatas in one source
2. Changing metadatas when we want with a little Java's GUI program that just send the right request through HTTP.

I think SAMCast 2013.2 use the same core's functionnality as SAM Broadcaster 2013.2, so I will test in V.1 mode and if it work, I will perhaps test in V.2 mode -> if there's issues, I will stay in V.1.

I will keep you updated here with the tests, It can perhaps help someone one day

Thanks again & regards,
Avalon

--------------------------------------------------

Hello again,

I've got a second question. If I create a SAMCast encoder, I can specify a password but no username. How SHOUTcast transcoder will know that username ?

Regards,
Avalon

[DrO]

connecting as a v1 DJ means you set dj:Password (where dj is the DJ id and password is the DJ password) as the password in the source (as long as it doesn't mangle things).

if it is based on Broadcaster, then maybe http://support.spacialaudio.com/foru...p?f=20&t=38155 is going to be applicable.