I have seen this discussed with contradicting answers. I think I know when it happens which might help to explain why.
1) Select a bunch of tracks or a whole playlist to "Play Now"
2) This puts everthing on the right hand "Playing" menu with numbers
3) You can randomize the list, you can play in order, you can shuffle
4) If you select a track to "play next" that happens to be above the one that is playing, it will place it right after the one that is now playing and indeed play it next BUT it gives it a new number and adds a duplicate track to the "now playing" menu....the number of files increases by one
5) If you select a track below the one that is playing and "play next" it does not add a duplicate track, it just moves the selected track up to be under the one playing and the total number of tracks in "Playing" does not change
6) Note this seems to only happen when you manipulate tracks under the "Playing" menu
I think having an actual queue would be a great add-on. A conventional queue where you add from where ever you want (whether from the main library, or from the "now playing" list) and you can change order of the queue at will without adding duplicates.
"Play next" adds a duplicate [#18927]
Moderator: Gurus
Re: "Play next" adds a duplicate
Tracked this inconsistent behavior as: https://www.ventismedia.com/mantis/view.php?id=18927
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: "Play next" adds a duplicate [#18927]
I think that in most cases the current behavior is the most desirable behavior as it retains play history (prior to the current track) & prevents duplicates in upcoming tracks.
BUT, I can see why it might be confusing. Any thoughts as to what the desired behavior should be ? i.e.
a) always duplicate tracks in the Playing list
b) always move tracks in the Playing list
I I had to choose either of these approaches, I lean towards a) but prefer the current behavior.
-Rusty
BUT, I can see why it might be confusing. Any thoughts as to what the desired behavior should be ? i.e.
a) always duplicate tracks in the Playing list
b) always move tracks in the Playing list
I I had to choose either of these approaches, I lean towards a) but prefer the current behavior.
-Rusty
Re: "Play next" adds a duplicate [#18927]
The current behavior only makes sense if there is no shuffle mode, because nothing works as expected in shuffle mode.
Based on the assumption that the now playing always displays the actual order to be played, it opens up possibilities.
Would it be too much to have the options:
- Play next - copy
- Play next - move
- Play now - copy
- Play now - move
This would be clear in all cases.
The latter two could even be left out in favor of using play next, and then using "Next Track" in the player to advance to it.
If that seems to complex, then how about :
If I am selecting play now or play next before or after within the now playing list - it seems likely that I want the current play order/location changed
If I am selecting play now or play next within the main window, it seems more likely I want to add the current selection to the now playing list, and retain any existing copies in their original order.
Based on the assumption that the now playing always displays the actual order to be played, it opens up possibilities.
Would it be too much to have the options:
- Play next - copy
- Play next - move
- Play now - copy
- Play now - move
This would be clear in all cases.
The latter two could even be left out in favor of using play next, and then using "Next Track" in the player to advance to it.
If that seems to complex, then how about :
If I am selecting play now or play next before or after within the now playing list - it seems likely that I want the current play order/location changed
If I am selecting play now or play next within the main window, it seems more likely I want to add the current selection to the now playing list, and retain any existing copies in their original order.
Using V2024 LATEST alpha or beta build on Windows 11, HP laptop, managing 13k tracks