> okay. can you give me some example on how to use vumeter
> and where it puts the output?
It's very basic, but good enough for debugging. At the end of your script,
right after input=fallback(...) you can add the operator around
your main source, by adding:
input = vumeter(input)
Then, the vumeter will be displayed on stdout. Hence, you should not be
running liquidsoap in daemon mode -- and if you get some logging on stdout
and you find it messy, you can force set("log.stdout",false).
Also, I think it's a good idea to use the on_blank() operator as you
tried in your script. Also add at the same place the line:
input = on_blank(on_blank_handler,input)
So it will log when it's been silent for a long time.
The more information we get, the sooner we'll find out your problem. The only
risk is that sometimes bug disappear if the load gets higher, or lower..
here the blank detection and vumeter will consume a little bit of CPU.
> > The "strange behavior" is in fact normal: the transitions do not use
> > the estimated remaining time, so at the switch() level it does not know that
> > it's about to end. There is an experimental feature (the parameter "before")
> > for doing that, but it probably won't work for you. If you really want a
> > transition you can try something based on cross(), like smooth_add() in
> > utils.liq... that's another topic that we should discuss separately.
> got it. i'll try to use other methods
Yeah. Let's try to fix your current bug, and later discuss that in another
thread if you need.
> > Yes it should work. It's meant to support any reloading interval. But, make
> > sure that you also know request.queue() and request.dynamic() as they are
> > more typically used in interactions with external scheduling systems like
> > your planned PHP system.
> so, as i understood this operators can help to build a dynamic playlist
> inside a liquidsoap, instead of building it inside the PHP?
It gives you support for doing it, but it does not need to be built inside
liquidsoap: the function that you pass to request.dynamic() can call a (PHP)
script that gives the next track. You'll find more doc about that on our
website and in the mail archive.
> one more question:
> i redesigned my script a bit to see all elements with custom id's
> in the log, but i cannot find out what are
Good idea. It seems that you didn't miss any, so yes, the remaining src_XXX
are operators built internally, e.g. default transitions. We should give
them more explicit names (used to be better at some point in the past, then
it broke and I never cared enough to restore it).
Good luck with your bug,