Hi Davi,
thanks for your answering my long mail and for ticket raising service.
I'm been busy during the week so I did not find time to write them myself until
now,
but I have added a comment on LS-447.
You are right: using a single playlist for all types would make it hard
to define source-type-specific fallbacks. I fully understand you concerns
regarding smartness vs. confusion and utility vs. complexity.
I did not raise a ticket for 4), since we basically need a mechanism, that
works for endless streams. Since I understood that requests and playlists do
not work with endless streams,
this idea would be eventually fine for other users, but I know that your
resources are limited.
For the same reason my other questions regarding playlists are not priorized
high to me at the moment.
> Coming back to your problem,
What I am currently interested in are reconfigurable sources for endless
streams that you mentioned in your response.
> Could it work with a fallback of a re-configurable input.http (this might be
> already possible) and a normal playlist?
This would be a great solution!
Did I understand you right, that source.dynamic could be used for this? But I
did not find any URL parameter to change the URL of a http input source.
So how could I dynamically change the URL of an existing input.http source?
Do you have any example for updating the URL of a configured input.http source?
Unfortunately I did not find any matching function at the API reference.
If this works, my final setup could look like
radio= switch (track-sensitive=false,
[
({sound_active==1} , input.alsa(...)),
({files_active==1} , file_A/B_queue),
({stream1_active==1} , stream1),
({stream2_active==1} , stream2),
({true} , scheduler_error)
]
)
where stream1 is
fallback(track_sensitive=false,
[
stream1,
stream1_fallback,
stream1_fallback_file
]
)
and stream2 is
fallback(track_sensitive=false,
[
stream2,
stream2_fallback
stream2_fallback_file
]
)
and stream1, stream1_fallback, stream2 and stream2_fallback are reconfigurable
input.http sources.
With help of some server register commands,
this would allow to dynamically update inactive sources and switch between
different sources
without having any breaks at ouput.
BR, Peter
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
