You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FPP Version and Hardware:
5.x-master-644-g467e93f1 on docker
Describe the bug and Steps to reproduce:
Setup simple playlist with 1 item
Setup simple scheduled with 1 sequence (or 1 playlist, behavior seems to be same), being active at time of test.
Send MQTT set/playlists/ALLPLAYLISTS/stop/now
Sometimes output fully stops
Sometimes auto-restarted immediately; from logs it seems like by scheduler.
Expected behavior:
Output fully stops.
Or at least the same thing every time.
Not sure if "playlists stop now" is supposed to affect scheduled stuff?
But in any case, if I start it with playlist/${PLAYLISTNAME}/start and then Stop as above, I also get same behavior.
If using Stop Now button in UI, it seems to stop fine every time.
Additional context:
Example of stop behavior (1 scheduled sequence, not playlist):
This is happening because Playlist::MQTTHandler() calls Playlist::StopNow() instead of Player::StopNow() so the Player instance doesn't know that the playlist was force stopped. For now, we may need to bubble up the Playlist::* functions up to call Player::* instead. The long-term plan would be to allow multiple playing playlists, but that is a huge change.
Please answer the following:
FPP Version and Hardware:
5.x-master-644-g467e93f1 on docker
Describe the bug and Steps to reproduce:
Expected behavior:
Output fully stops.
Or at least the same thing every time.
Not sure if "playlists stop now" is supposed to affect scheduled stuff?
But in any case, if I start it with
playlist/${PLAYLISTNAME}/start
and then Stop as above, I also get same behavior.If using Stop Now button in UI, it seems to stop fine every time.
Additional context:
Example of stop behavior (1 scheduled sequence, not playlist):
Example of restarting behavior (same config, 1 scheduled sequence, not playlist):
The text was updated successfully, but these errors were encountered: