Dear Marcin,

This is "far away from professionalism" because working on Liquidsoap is
the profession of none of us. Apart from a few beers, none of the
developers has made money from Liquidsoap and it will stay the same in
the foreseeable future. This software is the place where we can
experiment new ideas and have fun. This is our "truth". Of course, it is
nice too to have users and -- when we have free time -- we have done our
possible to fix bugs and fulfill user's requests.

We have always been pleased to accept contributions and if you want
professional support for Liquidsoap you are more than welcome to hire
someone to work on the code. For example, the alsa problem shouldn't be
hard to fix, but alsa is a very low-level API and we can't test it on
every soundcard. You should either give us more details than "it doesn't
work!" or better, pay someone to make it work on your soundcard. More
generally, we won't do intensive testing of Liquidsoap because we don't
have time nor resources to do this, but again any kind of help regarding
this would be welcome.

A few more technical comments:

- dynamic reloading: this is a feature that has been asked many times
but we did not implement it because it is incredibly complicated to do
this right. I wish you good luck doing this with your homebrew tool and
I would be interested in what result you have. Moreover, with an icecast
fallback it's not that much of a problem to restart liquidsoap from time
to time to change the script...

- cross-fading http: there is no way to know in advance when the stream
will end since we are almost realtime. It might be possible to think of
a buffering operator which could do the trick though.

- modern high-level API: I would really like to know what you do mean by
this. There is no other programming language for webradios that I am
aware of and is as high-level as liquidsoap. What do you have in mind???

Have fun with your own solution...

Cheers,

Samuel.


Marcin Lewandowski wrote:
> I wonder how many users will use that feature.
> 
> I work in a FM radio station, we create huge automation system. Liquidsoap
> was considered as being heart of one, and it performs now that function,
> but temporarily. We had made a decision to switch to our own solution,
> based propably on GStreamer, after a few disappointments. 
> 
> Basically, I use liquidsoap for last +/- 3 years, and there were at least a
> few moments that officialy released package wasn't stable or suffered from
> regressions. To mention only one of them, not more that a few months ago,
> ALSA output just stopped working after upgrade. Radio systems are realtime,
> critical systems, they MUST WORK, and I think you had already forgot that
> truth. The next big design change, that you had mentioned in your mail, is
> just a next opportunity to make new bugs. And please tell me, who uses now
> MIDI in the TV or radio? I've already stopped relying on liquidsoap, but
> that is the final argument to switch.
> 
> If you want to have it used in professional environments, concentrate at
> stability, good testing, integration with high-level interfaces to
> interoperate with rest of the system, and dynamic configuration reloading.
> 
> Currently if I need to do anything dynamically I have to feed liquidsoap
> via e.g. annotate, using dozens of custom scripts that are hard to
> maintain, there's no modern high-level API. And using that I still cannot
> e.g. add dynamically new input.http for transmission from one time event.
> Needless to say that I cannot do fadeout after switching from input.http.
> Of course, I can use PulseAudio or JACK for mixing that cases but it gives
> me a next scripts to mantain. etc. etc.
> 
> I know that it's more fun in designing such fancy things as content-type,
> but in my opinion it's far away from professionalism.
> 
> m.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to