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
Last played song unknown (when using random playback)
Suppose the following scenario:
I have a very long playlist with over a hundred entries playing at random
Now I notice a particular song piking my interest, but I can not abort my current occupation of drilling a hole into a wooden plank to mount it to a box as that would jeopardize my efforts of the past 15 minutes.
10 minutes later I run to the player to look up what song played. But it's already two songs further! - there is no reasonable way for me to look up the song that played 10 minutes ago.
User is sad
Suggestions:
A.) Have some kind of 'event log'. Which registers a separate event whenever a new song is being played. --> Each action could be event based, thus also making a remote control feature more easily possible (so we can perhaps implement another feature more easily: synch multiple devices)
B.) Make the random order somehow visible in the playlist. (Maybe with numbering: '+1', '+2' for the next tracks and '-1', '-2' etc. for the previously played tracks.
C.) Add some 'forward' and 'backward' buttons to the player.
The text was updated successfully, but these errors were encountered:
Last played song unknown (when using random playback)
Suppose the following scenario:
Suggestions:
A.) Have some kind of 'event log'. Which registers a separate event whenever a new song is being played. --> Each action could be event based, thus also making a remote control feature more easily possible (so we can perhaps implement another feature more easily: synch multiple devices)
B.) Make the random order somehow visible in the playlist. (Maybe with numbering: '+1', '+2' for the next tracks and '-1', '-2' etc. for the previously played tracks.
C.) Add some 'forward' and 'backward' buttons to the player.
The text was updated successfully, but these errors were encountered: