Fretwizard Hi Peter, just noticed that the UI not updated when toggling autoplay with footswitch in playlist view too. Thanks.
That's intentional. Because when you press the pedal, it will change the autoplay status of your queue. No matter in which view you are. The autoplay setting in the playlist view is only stored in the playlist and will be used once you load the playlist into the queue. So remote controlling this switch does not make sense.
JDSMUSIC Dont know if this build covers this but I was importing a rather large list and while it was running I went to reply to a text message. When I returned to ST3 it was frozen. Could not even Cancel. Had to restart ST and redo the import.
I guess this might be covered with the next update. I have received some screenshots about database issues and these fixes might also take care of your problem.
danielrodgers85 I have noticed that if you modify a songs properties to start at a certain position eg 4 seconds
And the option to restart song from beginning after pausing enabled
The song goes back to start, and not the 4 second mark
Good find. This is a bug and I will fix it in the next version.
danielrodgers85 When you remove a song from the library, it is also removed from all playlists
It would be handy if it could be replaced with a placeholder in the playlists
I don't think that would be a good idea. If you remove a song and it would be converted to a placeholder, you would still see the placeholder in the songlist. This doesn't seem like a good way to keep your library clean. And what happens when you reimport the song? You would have two songs with identical names with the only difference that one of them does not have a song duration displayed. I gues that could cause confusion.
JDSMUSIC if I double tap to move it to the top, shouldn't the queue list reposition to top? I had to scroll to see that it was set to play next?
This was fixed in one of the last updates. Are you sure you are running version 3554?
musicadi The problem with your suggestion is that the queue is not aware from where a song has been added. It does not know the song on position 1 was added from playlist A and song on position 2 from the song list. So to make the queue aware I would need to change the database structure again. I won't do that at this point for version 3.0.
But I will monitor user feedback for version 3.0 closely. If there is a significant amount of users that have problems using the queue, I guess I will come back to think about your suggestion. But I really struggle with seing the advantage of limiting the queue to 2 positions. I guess in that case it would in fact no longer make sense to have a tab for the queue in the UI? It would really change the behavior of the app and I'm not sure it is a good idea to make the app behave completely different on the switch of some settings.