What is the expected result:
Jukebox always have a song available from the selected playlist and will play continuously.
What can prevent this:
Small playlists with few different albums or artists, and with uniqueness parameter set on albums or artists. In this case, jukebox will starve quickly as it only have a few songs to select from.
This situation normally doesn't occurs from a smart user setting, but using the timers can make the playlist switch without user interaction.
User case scenario:
Wanting a timer to play a user playlist, but having the program set most of the time on database setting with uniqueness enforced.
Ideas for solution:
set the uniqueness parameters with a timer. Also set a playlist with the stop option as the jukebox will stay with the small playlist during normal operation if the user doesn't create a 5 minute timer to reset the list
do not respect uniqueness parameter if the resulting playlist is less than 1 (or less than the "keep queue length" parameter on the jukebox)
myMPD v5.6.0 gets a new easy scripting capability that supports all myMPD API calls. The user can create this scripts with an easy interface. Scripts can be called like the system commands in the main menu and by timers.
Disabling the uniqueness parameters on demand is a good idea.
In the v5.6.0 branch the jukebox disables the unique parameters temporarily if unique parameters can't be fulfilled. Changing any jukebox parameter resets this temporary parameter.
Hello,
As discussed in this issue https://github.com/jcorporation/myMPD/issues/269#issuecomment-636253231, there might be an issue with playlists drying off if uniqueness parameter is set.
What is the expected result: Jukebox always have a song available from the selected playlist and will play continuously.
What can prevent this: Small playlists with few different albums or artists, and with uniqueness parameter set on albums or artists. In this case, jukebox will starve quickly as it only have a few songs to select from. This situation normally doesn't occurs from a smart user setting, but using the timers can make the playlist switch without user interaction.
User case scenario: Wanting a timer to play a user playlist, but having the program set most of the time on database setting with uniqueness enforced.
Ideas for solution:
set the uniqueness parameters with a timer. Also set a playlist with the stop option as the jukebox will stay with the small playlist during normal operation if the user doesn't create a 5 minute timer to reset the list
do not respect uniqueness parameter if the resulting playlist is less than 1 (or less than the "keep queue length" parameter on the jukebox)