sc_trans for linux. i still want to use it!

[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.

[dopelabs]

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

Each stream-user needs a also own open port