Thank You for your continued support and contributions!
The Insert C step should result in 12BC3A. "Insert" should always go immedialy after the most recently inserted song, when things are working right, while Insert Next should go immediatly after the currently playing song.
On the other hand, if "insert next" does not move the pointer, there is no way to go from1 2 B 3 A to 1 2 B C 3 A
So, if I were on song 2 of 1 2 3 4, and I wanted to create 1 2 A B 3 4, I would have to "Insert Next" B, then A? That is my only option for creating that playlist unless I removed 3 and 4 first? It seems limited now... At least in my mind it's counterintuitive to force a user to insert in inverse order.
I can't really think of ever wanting to use the first case, though I'll admit it's possible.
It also seems to me that the behaviour shouldn't be different (for insertion) depending on whether a playlist is Dynamic or Static.I mean, if I choose to "Insert" a folder, why should it behave any different than if I play a song in that folder with Shuffle enabled, and play selected song disabled?
A currently running playlist has three sections: first its original contents from the file, then the tracks added with "insert" in the order they were added, finally the tracks added with "insert last" in the order they were added. All three sections can have further tracks "inserted next" while they're playing.
(Oh, and Hardeep: What would your "reset insert position" option set the position to?)
If I'm alone in this, it's fine, but this seems like the most common style of insertion procedure I use, lining up several songs I've just decided I wanted to hear, and I don't feel it should be dependent upon me not having created the initial playlist by way of insertions.
Page created in 0.287 seconds with 25 queries.