v4.0.0 #19
Moonbase59
announced in
Announcements
v4.0.0
#19
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
2024-06-14 - v4.0.0
New features
Even better transitions, using both "longtail" logic and the new "sustained endings" feature by @RM-FM, which we could even improve on, in a collaborative work. We are really happy with the results!
Combined with the existing blankskip handling (whose default is now 5.0 seconds instead of 2.5 s, to avoid false triggers), we are able to handle the greatest variety of possible song endings with great transitions. Be it a cold end, a long fade, a trick ending, an unexpected noise, chord, riff or vocal at the end — we catch them all. Pure listening enjoyment!
If you’re interested, here’s part of our testing set. Try it out for yourself!
Songs with difficult endings:
New "sanity check" that (also) checks if your external
cue_file
and the Liquidsoap code have matching versions (a suggestion by John Chewter (@JohnnyC1951)), and shuts down otherwise. After your settings, simply use this code:Recommendation
check_autocue_setup
function after your settings, in both standalone scripts and AzuraCast. It will not only check versions, but also set the crossfading duration to a correct value, based on your fade-out setting.Breaking changes
New informational boolean value
liq_sustained_ending
incue_file
result, file tags, and Liquidsoap metadata. It shows whether the "sustained endings" feature has been used to determine the "start next song" overlay point.Analysed timings shown on console, in case you manually tag a file or just want to check the results. This output don’t affect normal operation, it is done to
stderr
:This discussion was created from the release v4.0.0.
Beta Was this translation helpful? Give feedback.
All reactions