Asking for help: Can’t get news switch to work #4004
-
|
For playing the news at full and half hour, I would like to
I came up with the following code, because the commented-out For some reason, I can’t get it to work. I hear a very brief loudness drop, but no news play. The news file itself is requested, autocued, ready and all. # News
thread.when(predicate.activates({ 59m45s or 29m45s }), fun() -> playlist_nachrichten.reload())
#radio = smooth_add(duration=2., p=0., normal=radio, special=switch(id="news_switch", [(predicate.once({ 0m0s or 30m0s }), sequence([blank(duration=2.), playlist_nachrichten]))]))
radio = switch(
id="news_switch",
track_sensitive=false,
[
(predicate.activates({ 0m0s or 30m0s }), playlist_nachrichten),
({ true }, radio)
]
)If I use Anyone out there who can tell me what I’m doing wrong, and how I can achieve the desired result? Here is a typical part of the log (I’m using AzuraCast): |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 8 replies
-
|
Here, it's a job for radio = fallback(track_sensitive=false,[
switch(id="news_switch",[(predicate.activates({ 0m0s or 30m0s }), playlist_nachrichten)]),
radio
])Should work with radio = fallback(track_sensitive=false,[
switch(id="news_switch",[(predicate.once({ 0m0s or 30m0s }), playlist_nachrichten)]),
radio
]) |
Beta Was this translation helpful? Give feedback.
-
|
So apart from the fact that with thread.when(predicate.activates({ 0m03s or 30m03 }), fun() -> source.skip(radio))
radio = fallback(track_sensitive=false,[
switch(id="news_switch",[(predicate.once({ 0m0s or 30m0s }), playlist_nachrichten)]),
radio
])While our fallback to news plays - we skip radio source (old one, before fallback) and after Don't know how "orthodox" this is but it seems to work nicely) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion, will try. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure it will work this way. But worth a try. |
Beta Was this translation helpful? Give feedback.
-
|
Hm. Wanted to look up |
Beta Was this translation helpful? Give feedback.
-
|
Phew. After searching and finding the LS docs not helpful at all, I found a hint in a 2013 AirTime forum post, and after only a few hours of frustrating experiments came up with this: Seems to work well. AzuraCast users: Third input box in Edit Liquidsoap Config. ;-) And do your |
Beta Was this translation helpful? Give feedback.
-
|
What exactly does the "playlist_nachrichten" look like (settings)? One or two playlists? Is "news" correct in the script? Should it perhaps be "playlist_nachrichten"? Thanks for the answer. |
Beta Was this translation helpful? Give feedback.
-
|
You can name your playlist whatever you want. Here is minimal reproduction script to make it clear: radio = playlist("/path/to/music")
playlist_news = playlist("/path/to/playlist_file.m3u")
# Reload the news playlist shortly before playing,
# to get latest news and not old queued ones
thread.when(predicate.activates({ 59m45s or 29m45s }), fun() -> playlist_news.reload())
# Make a News source that is only active at certain times
# Hourly news at 06:00-18:00 and 20:00, 16s past the hour
# to leave room for the TOTH time & station announcement
news = fallback(
track_sensitive=false,
[
switch(
id="news_switch",
[(predicate.once({ (6h00-18h00 or 20h00) and 0m16s }), playlist_news)]
)
]
)
# When news source becomes active:
# Skip current track, play news, continue with new track
radio = fallback.skip(news, fallback=radio)
radio =mksafe(radio)
output(radio) |
Beta Was this translation helpful? Give feedback.
-
|
It's surprising that such a very common requirement for a radio is so complicated to implement. |
Beta Was this translation helpful? Give feedback.
-
|
I understand. There are underlying issues with automation that are inherently hard. Typically, making sure that there is a file that has been checked to be decodable and ready to be played at the exact time intended. This can included downloading a file, etc. We can make our best to make it as simple as possible but we also have to be careful not to hide those complexities otherwise we run into other issues, typically users not understanding why their scheduled track did not fire at the right time etc. As for code, I wrote something about it here: https://www.liquidsoap.info/blog/2023-03-25-precise-scheduling-of-tracks/ |
Beta Was this translation helpful? Give feedback.
-
|
But, yes, we definitely want to improve this. One thing we've been discussing with @smimram is how to improve the current We're definitely open to help with this and the doc if there are any interested people here! |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I didn't mean to sound impertinent. |
Beta Was this translation helpful? Give feedback.
-
|
You didn't! |
Beta Was this translation helpful? Give feedback.
Phew. After searching and finding the LS docs not helpful at all, I found a hint in a 2013 AirTime forum post, and after only a few hours of frustrating experiments came up with this: