Play next when shuffle is on

[laurensi1]

Hello

Almost all the time when I'm playing music with MediaMonkey I just shuffle all my music. When I stumble upon a song in my library that I want to listen to after the current song however, I can't just use the play next feature in the context menu because the shuffle is on. So first I have to switch off shuffle and when the other song starts I need to switch it back on. That isn't very convenient.
So my wish is: whenever I use the play next button (even with shuffle on), I woould like that it plays the song I chose.
It isn't a big feature I guess, however I would appreciate it a lot.

Thanks

[Dreadlau]

Hello.

It is possible thanks to ZvezdanD and his "Queue List" script.
See: http://www.mediamonkey.com/forum/viewto ... ue#p255655

Would be nice if this function was integrated in Mediamonkey IMO.

[Mizery_Made]

I don't think it necessarily needs to be integrated, but it would be nice of some improvements were made to allow the script to work more flawlessly (as currently, it randomly starts playing another track before switching to the queued track. It surely interrupts the shuffle list as well, leading to something you had just listened to possibly playing not long after, etc) Though I guess if it were integrated, these issues wouldn't be present anyway.

[Dreadlau]

I, myself don't use the shuffle. I use auto-Dj instead.

I suggest tho that the enqueue function gets integrated because:

.it's very handy.

.Not having it is probably a turn-off for users coming from programs such as winamp.

[ZvezdanD]

it would be nice of some improvements were made to allow the script to work more flawlessly (as currently, it randomly starts playing another track before switching to the queued track. It surely interrupts the shuffle list as well, leading to something you had just listened to possibly playing not long after, etc)

I don't understand, are you talking about Queue List add-on? Are you sure about those flawlessness? I put a lot of attention on it to assure that the originally played random list is regained and it should not play tracks that are already played. Also, switching to the queued tracks is done only after the currently played track finish with its reproduction since the same behavior has WinAmp.

By the way, I would appreciate if you report such inconsistencies into add-on thread.

[Lowlander]

You can also use Randomize on the Now Playing and then insert tracks to play next.

There have been requests to enable Play Next in Shuffle mode as well as have multiple Play Next queue one after the other instead replace the next track to play. I think both would be welcome options despite the alternative methods available.

[Mizery_Made]

I don't understand, are you talking about Queue List add-on? Are you sure about those flawlessness? I put a lot of attention on it to assure that the originally played random list is regained and it should not play tracks that are already played. Also, switching to the queued tracks is done only after the currently played track finish with its reproduction since the same behavior has WinAmp.

I was referring to the Queue List add-on in my statement. The one about it messing up the "shuffle list" was honestly just an assumption (as I had never actually paid attention as to whether it turned shuffle off or not, like the old Play Next script did, and my NP list always has thousands of tracks so it wouldn't be easy to notice if it really did reset the 'shuffle list'). As for the other thing, after it finishes playing the currently playing track, it then moves to another track chosen at random (as would normally happen when shuffle is on and nothing is queued) and play a few seconds of it before switching to the queued track. I've never used the feature in WinAmp (last used WinAmp like five years ago, so even if I had, I probably wouldn't remember) so I don't know if it does the same thing (plays a track at random, before switching to the chosen next track) but I would assume it doesn't.

By the way, I would appreciate if you report such inconsistencies into add-on thread.

I never bothered reporting anything in the scripts' thread because the "finish current track, play couple seconds of next random track, switch to chosen next track" thing is something the old "Play Next" script did as well, so I chalked it up to a limitation by MM and not the script itself, and the other thing like mentioned was an assumption I made that didn't even really come to mind until I was typing the previous reply.

[ZvezdanD]

The one about it messing up the "shuffle list" was honestly just an assumption ... As for the other thing, after it finishes playing the currently playing track, it then moves to another track chosen at random ... and play a few seconds of it before switching to the queued track.

OK, I see that your first mentioned issue is actually just assumption. As I said, I put a lot of effort to retain the original shuffle list, so that none track from it is played twice or skipped. I assure you, if you have 100 tracks in NP, you would get played exactly 100 tracks (with the addition of tracks from the queue list, of course).

About your second mentioned issue, you are partly right - when the current track finish with its reproduction, the program will try to play the next track from its shuffle list and in that moment the add-on would force it to play tracks from the queue list instead. However, this should happen almost immediately after the finish of the currently played track, without any noticeable interruption. At least I am getting such response on my computers. I don't know how you got those "few seconds" in reproduction of the next track from the shuffle list since such thing never happened to me. Unfortunately, MM script programing interface is as it is, like it or not, and I cannot do anything better with it then how it is now. There are just few available events which I could intercept: OnTrackEnd, OnPlaybackEnd and OnPlay. I tried all of them and concluded that the current implementation is the best possible. You see, I cannot force the program to play tracks from the queue list inside of OnTrackEnd and OnPlaybackEnd events because the program would skip the first track from that list. So, I could use only OnPlay event and in that moment the program is already started with the reproduction of the next track from its shuffle list. However, as I said, this transition should happen without any noticeable delay. Maybe you have installed some another add-on which is messing with the OnPlay event introducing that delay?

[Mizery_Made]

Perhaps you have a faster and/or multiple processors than I, more memory, or some other factor which might explain why yours can jump to the queued track quicker than mine. However, I'll test out the script theory and see what happens. Deleting everything in my Scripts folder aside from the Queue List vbs, results in the same behavior for me, which is the 1-2 seconds of a random track prior to the queued track interrupting. I think that may point back to the hardware thing (I only have a 1.86GHz processor in this computer and 2GB memory with Vista Home Premium)

It's not that big of an annoyance, as like mentioned it's only a second or two before the switch and I don't tend to use the script often. I've always chalked it up to scripting limitations (which you seem to confirm to some degree) and was actually what I was trying to get at in my "doesn't need to be implemented, if made to run task via script smoother" argument. Thus meaning, the inclusion of some function that would allow you to actually insert the song(s) after the previous song finishes but before the next one actually begins (thus, something between On...End and OnPlay or something to that effect).

PS -- Does anyone have an idea as to why on my computer, MediaMonkey launches (if it isn't running) whenever I go into the MediaMonkey folder under Programs (and I seem to recall it happening with the AppData folder as well)? It's quite annoying to close out the program to do something (like delete the scripts folder), only to have the program re-launch when you get to the folder. I remember this occurring on my old Desktop, but didn't occur at first on here though now it does. Sorry for the hijack, but always meant to ask that but never bothered to actually create a thread for it... had it happen, and figured would slip it in here.