sc_trans for linux. i still want to use it!

allezbrian · 18th March 2016, 01:59

Folks,

I understand sc_trans has long since been abandoned as far as a supported product, and liquidsoap seems to be the current solution.

That being said, I've been using variants of sc_trans for about 15 years, and I'd like to continue if I can.

Where can I at least find, and be comfortable with the fact that I do, in fact, have the latest release of sc_trans? (64 bit, for linux).

If I have to move to liquidsoap, I will, but sc_trans has served me well, and I'd like to know if anyone is still an enthusiast. Is anyone????

Thanks,

Brian

neralex · 18th March 2016, 11:12

Liquidsoap is a solution for very simple stations without fixed transmission times for different pre-recorded shows and without a user-management. I personally like the functionality of sc_trans. Liquidsoap has no option for an API-restart as you know it from sc_trans. If you created a new playlist in Liquidsoap and you would add it then you have to restart the whole instance of Liquidsoap and then you kick all listeners from the stream. Each stream-user needs a also own open port... etc. The list is long and these are the reasons why I'm still using sc_trans. For sure sc_trans is not perfect and it has some bugs but for me is it the best solution.

dopelabs · 18th March 2016, 21:31

Quote:

Originally Posted by neralex

Liquidsoap is a solution for very simple stations without fixed transmission times for different pre-recorded shows and without a user-management. I personally like the functionality of sc_trans. Liquidsoap has no option for an API-restart as you know it from sc_trans. If you created a new playlist in Liquidsoap and you would add it then you have to restart the whole instance of Liquidsoap and then you kick all listeners from the stream. Each stream-user needs a also own open port... etc. The list is long and these are the reasons why I'm still using sc_trans. For sure sc_trans is not perfect and it has some bugs but for me is it the best solution.

it should be possible to add a playlist to a running instance of liquidsoap.

please see: http://savonet.sourceforge.net/doc-svn/advanced.html

also you can configure sc_serv to not drop all your listeners when a source disconnects.

config file value:

code:


autodumpusers = 0

also please explain a little further about

Quote:

Each stream-user needs a also own open port

DJ-Garybaldy · 18th March 2016, 14:22

Old copies of SC Trans available on retired files.

allezbrian · 20th March 2016, 16:09

Quote:

Originally Posted by DJ-Garybaldy

Old copies of SC Trans available on retired files.

Thank you for the link.

neralex · 18th March 2016, 23:54

Hey dopelabs!

I contacted you with this question for a while ago but after you doesn't answer my questions I contacted the the developers of liquidsoap and I tested it by myself - this is not possible on this way it does sc_trans.

If a music-file with a length of 60mins (dj-set) is started at 19:50 o clock in the 24/7 playlist and you want add a pre-recorded show at 20:00 o clock (custom scheduled) then liquidsoap will start the pre-recorded only after the music-file is ended, which is started at 19:50 o clock. Because liquidsoap will only read new playlists after a restart of the whole instance. Exactly for this reason sc_trans has the API restart without a disconnect from the streaming-server. The only way in liquidsoap to do this is a restart of the whole instance.

"autodumpusers" will and can not solve it. You should better try it before you recommend it to other users as long you don't know how "autodumpusers" really works and for which cases it was created.

All stream users of sc_trans are using only one open port with their own username and password but in liquidsoap you must set for each stream-user a own open port. And if you want remove a stream-user in liquidsoap you have restart the whole instance again - in sc_trans you need only an API-restart.

I'm working with sc_trans since more than 4 years with a own web-interface which is working with some crontabs and a mysql database. I have tested many solutions but liquidsoap is only for simple configured 24/7 playlists with some live-djs which are using all the same stream-password to going live but not for stations which are using many different live-djs and also many pre-recoded shows which must be custom scheduled to different times on a single day and on different days of week.

It exist so many cases where you have to change the live-stream password after some djs leaved the team or they must removed after some trouble - this makes no sense for me when I have the chance to give each user a own username/password which I can remove without to share the new stream-password to all other live-djs.

With liquidsoap I would kick with each custom scheduled playlist all listeners from the stream. I have to manage many pre-recorded shows which they provided from their hosts on different days on a week or days of a month (weekly, biweekly, monthly). How should I do this in liquidsoap without a restart? It needs a automation and not that I have to connect via telnet manually or something strange things like this you mentioned.

At least we should don't forget to say that the worst thing on liquidsoap is the horrorble 'support'. The idea behind liquidsoap is really cool but its outdated and its not offical supported. Its like playing with toys but not with a professional solution.

dopelabs · 19th March 2016, 02:04

or maybe something from http://savonet.sourceforge.net/doc-s..._kube-dev.html can help.

http://savonet.sourceforge.net/doc-0...c_request.html
http://savonet.sourceforge.net/doc-0...h_generic.html
http://savonet.sourceforge.net/doc-0...ml#source_skip
http://savonet.sourceforge.net/doc-0...ack_basic.html
http://savonet.sourceforge.net/doc-0...playlist_parse
or maybe something from http://savonet.sourceforge.net/doc-s..._kube-dev.html can help.

and for me autodumpusers works as described in the documentation.

and they recently released a version of liquidsoap.

neralex · 19th March 2016, 10:05

Nice try but it will not work on the way as it does sc_trans ...

18th March 2016, 01:59	#1
allezbrian Junior Member Join Date: Dec 2014 Posts: 4	sc_trans for linux. i still want to use it! Folks, I understand sc_trans has long since been abandoned as far as a supported product, and liquidsoap seems to be the current solution. That being said, I've been using variants of sc_trans for about 15 years, and I'd like to continue if I can. Where can I at least find, and be comfortable with the fact that I do, in fact, have the latest release of sc_trans? (64 bit, for linux). If I have to move to liquidsoap, I will, but sc_trans has served me well, and I'd like to know if anyone is still an enthusiast. Is anyone???? Thanks, Brian

18th March 2016, 14:22	#4
DJ-Garybaldy Forum King Join Date: Sep 2003 Location: Harpurhey, Manchester UK Posts: 3,944	Old copies of SC Trans available on retired files. RadioDJ - Winamp - SAMBC

19th March 2016, 10:05	#8
neralex Major Dude Join Date: Mar 2011 Posts: 576	Nice try but it will not work on the way as it does sc_trans ... Last edited by neralex; 19th March 2016 at 12:51.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

18th March 2016, 11:12	#2
neralex Major Dude Join Date: Mar 2011 Posts: 576	Liquidsoap is a solution for very simple stations without fixed transmission times for different pre-recorded shows and without a user-management. I personally like the functionality of sc_trans. Liquidsoap has no option for an API-restart as you know it from sc_trans. If you created a new playlist in Liquidsoap and you would add it then you have to restart the whole instance of Liquidsoap and then you kick all listeners from the stream. Each stream-user needs a also own open port... etc. The list is long and these are the reasons why I'm still using sc_trans. For sure sc_trans is not perfect and it has some bugs but for me is it the best solution.

18th March 2016, 23:54	#6
neralex Major Dude Join Date: Mar 2011 Posts: 576	Hey dopelabs! I contacted you with this question for a while ago but after you doesn't answer my questions I contacted the the developers of liquidsoap and I tested it by myself - this is not possible on this way it does sc_trans. If a music-file with a length of 60mins (dj-set) is started at 19:50 o clock in the 24/7 playlist and you want add a pre-recorded show at 20:00 o clock (custom scheduled) then liquidsoap will start the pre-recorded only after the music-file is ended, which is started at 19:50 o clock. Because liquidsoap will only read new playlists after a restart of the whole instance. Exactly for this reason sc_trans has the API restart without a disconnect from the streaming-server. The only way in liquidsoap to do this is a restart of the whole instance. "autodumpusers" will and can not solve it. You should better try it before you recommend it to other users as long you don't know how "autodumpusers" really works and for which cases it was created. All stream users of sc_trans are using only one open port with their own username and password but in liquidsoap you must set for each stream-user a own open port. And if you want remove a stream-user in liquidsoap you have restart the whole instance again - in sc_trans you need only an API-restart. I'm working with sc_trans since more than 4 years with a own web-interface which is working with some crontabs and a mysql database. I have tested many solutions but liquidsoap is only for simple configured 24/7 playlists with some live-djs which are using all the same stream-password to going live but not for stations which are using many different live-djs and also many pre-recoded shows which must be custom scheduled to different times on a single day and on different days of week. It exist so many cases where you have to change the live-stream password after some djs leaved the team or they must removed after some trouble - this makes no sense for me when I have the chance to give each user a own username/password which I can remove without to share the new stream-password to all other live-djs. With liquidsoap I would kick with each custom scheduled playlist all listeners from the stream. I have to manage many pre-recorded shows which they provided from their hosts on different days on a week or days of a month (weekly, biweekly, monthly). How should I do this in liquidsoap without a restart? It needs a automation and not that I have to connect via telnet manually or something strange things like this you mentioned. At least we should don't forget to say that the worst thing on liquidsoap is the horrorble 'support'. The idea behind liquidsoap is really cool but its outdated and its not offical supported. Its like playing with toys but not with a professional solution.

19th March 2016, 02:04	#7
dopelabs Major Dude Join Date: Oct 2006 Location: Silicon Valley Posts: 536	or maybe something from http://savonet.sourceforge.net/doc-s..._kube-dev.html can help. http://savonet.sourceforge.net/doc-0...c_request.html http://savonet.sourceforge.net/doc-0...h_generic.html http://savonet.sourceforge.net/doc-0...ml#source_skip http://savonet.sourceforge.net/doc-0...ack_basic.html http://savonet.sourceforge.net/doc-0...playlist_parse or maybe something from http://savonet.sourceforge.net/doc-s..._kube-dev.html can help. and for me autodumpusers works as described in the documentation. and they recently released a version of liquidsoap.