Bug / Inconsistent behavior of the Stop command (X)

[tomimatko]

I often use X (Insert Stop command) + N (next) during live broadcasting, especially when I want to speak after a song.

I've noticed a few inconsistencies:

1. Inserting a Stop command (X)
Pressing X correctly inserts the Stop command after the selected track. However, if no track is selected, the Stop command is inserted at the end of the playlist instead of immediately after the currently playing track. It would make more sense to insert it after the currently playing track, since placing a Stop command at the end of the playlist serves no practical purpose.

2. Next (N) after a Stop command
With "Remove stop commands after execution" enabled, everything works correctly: pressing N starts the next track.
If "Remove stop commands after execution" is disabled, N starts always the first track if Repeat Playlist is enabled, or does nothing in normal playing mode.

 

[djsoft]

if no track is selected, the Stop command is inserted at the end of the playlist instead of immediately after the currently playing track. It would make more sense to insert it after the currently playing track, since placing a Stop command at the end of the playlist serves no practical purpose.

Yes, it would be more logical to have it inserted after the playing track. However if nothing is playing and nothing is selected, inserting at the end is OK as any other position may not be what is expected.

If "Remove stop commands after execution" is disabled, N starts always the first track if Repeat Playlist is enabled, or does nothing in normal playing mode.

This may be because of how the next track is evaluated. I can't tell if it'll be fixed, it depends on how much next track evaluation needs to be changed for this.