Page 1 of 1

Tracks, place following playing song, skipped [#12315]

Posted: Thu Nov 06, 2014 4:30 am
by Morten242
Has happened consistently now since most recent update.

When playing a song, if I move any amount of songs in front of it in the playlist, then it will play the song which was originally supposed to be the next song before placing something between.

Steps:
1. Have a playlist with songs (mine is 183 tracks, might not matter) (at least 3 is needed (math))
2. Play one of the songs
3. Move a song in the *now playing list* between the currently playing song and the next song.

MediaMonkey Beta Android 1.1.0.0331 on Xperia Z running CyanogenMod 10.2.1-yuga (4.3.1) with privacy guard enabled for MM.

Re: Tracks, placed in front of currently playing song, skipp

Posted: Thu Nov 06, 2014 11:44 am
by rusty
I suspect that this is a usability issue rather than a bug. At step 3, if you moved a song in the playlist, then the Playlist was edited, but the Now Playing list was unchanged.

So if you want to change the order of the Now Playing list, you have to edit it directly. It's accessed by clicking the icon with 3 lines in the Now Playing Art view.

Does that clarify?

-Rusty

Edit: I suppose that an alternative ?easier to understand? approach could be to indicate the source from which tracks are being played, rather than always playing from the NP Queue. This isn't currently the approach taken in MediaMonkey for Windows either.

Re: Tracks, placed in front of currently playing song, skipp

Posted: Thu Nov 06, 2014 5:25 pm
by Morten242
Ah, sorry, I meant the now playing list, not the playlist. That wouldn't update the current playlist ("current" being the now playing list.)

I'll edit the top post to clarify that.

Re: Tracks, placed in front of currently playing song, skipp

Posted: Fri Nov 07, 2014 12:47 pm
by rusty
Thanks--I'm able to replicate. Tracked at http://www.ventismedia.com/mantis/view.php?id=12315

-Rusty

Re: Tracks, place following playing song, skipped [#12315]

Posted: Wed Nov 12, 2014 6:14 pm
by rusty
Fixed in build 338.

-Rusty