Improve "Stop After Current" functionality

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Improve "Stop After Current" functionality

Re: Improve "Stop After Current" functionality

by Slater » Mon Nov 26, 2018 11:42 am

This Media player would be a big competitor to "Onsong" if the option was added as a toggle on/off Stop after each song.

I am trying to find a better option for a tablet for playback and Lyrics.

Currently I can only use the "Now playing" option and choose 1 song at a time, otherwise the next song starts straight away.

The Android app is much better than Others I've used such as "Setlist helper" as you can search without interrupting the playback.

I think this is the biggest reason it is not used more by commercial bands.

Adding a few options of what happens in-between songs would make this media player awesome.

Thanks

Toggle on/off

Re: Improve "Stop After Current" functionality

by Mizery_Made » Tue Jan 04, 2011 4:51 am

Regarding the bug you point out, Rusty: I personally don't see anything wrong with the current implementation of "Shuffle." I also wonder why the Shuffle feature should be changed to function in a similar manner to that of a feature already available (Randomize). The current behavior of the Shuffle feature is pretty long standing, as I've been a user for around 5 years and from what I recall, it's always acted as it does today. I can only recall two (consistent) complaints regarding the Shuffle feature over the years, the most common having been that the "Back/Previous" button didn't go back to the track that was just played/skipped and the other one that comes up often being about the randomness of the feature.

When I turn the Shuffle feature on in MediaMonkey, I expect the player to jump it's way through the Now Playing list as it randomly plays tracks. Now it's been quite a while since I've used another player as I have been pretty loyal to MM over the past 5 years, but I seem to recall this being the way the other "big boys" of the media player game also handled the situation. So I expected it due in part to that, but also again, because that's how MM has worked for at least five years.

I can understand the need for other approaches... but... they're (for the most part) already provided. You've already supplied the Randomize list feature. There's also the Auto-DJ function which also functions pretty similar to some of the proposals for Shuffle changes (the big difference being that the playlist/filter seeds the tracks and not the Now Playing list).

As for the point you raise, peke, regarding the fact that "those two mins [s]are[/s] can be used to add/prepare next track," I honestly don't think "Stop after Current"+"Shuffle" would be the most ideal approach to this. As stated, Auto-DJ is there and provides similar functionality to that of Shuffle while also allowing you to easily "Play Next" a track. Even if you prefer the "Shuffle" feature, as I previously mentioned there is Zved's "Queue list" script which allows you to queue tracks to play after the current on finishes, again without the need to stop the track.

Even if you do stop the track after it plays, and then use the next two minutes to add the next track you want to play, what difference does it make whether it's added at position 301 (right after the track that just finished playing, which was 300), or if it went ahead to the next track and thus you dropped it at position 1,201 (right after track 1,200 which is where the player went after you "Stopped after Current")? I seem to recall this question being answered elsewhere on the forum at some point, but what happens to the "shuffle list" when the player is stopped? Doesn't it generate a fresh shuffle order when you begin playback again? If that is the case, then what would be the difference of clicking the Shuffle button off as opposed to enabling Stop after Current so that you may force a certain track to play next?

As I noted before, it really comes down to your interpretation of the word "after" in the feature's title. Currently, the song fully plays and then playback is stopped. This could be interpreted as "after," since it played the entire song. However again, hitting play would then play the song over which in my opinion, doesn't fall under the definition of "after." Whereas if it plays through entirely and then moves to the next track, then it definitely stopped playback "after" the "current" (at the time) track.

To me, the issues boils right down to the fact that if you "Stop after Current" and then hit play again (say you had to go to the bathroom, but wanted to wait until the track finished playing) or stopped playback for the night and then brought MM back up the next day... most people aren't going to expect to hear that track again when they hit play. I think that's obvious by the fact that it's often been asked why it doesn't move to the next track. I see this as a valid point regardless if shuffle is enabled or not.

It's all in the interpretation and personal opinion. I think it should work one way, Peke thinks it should work another and a third person is liable to suggest something entirely different. Perhaps it's due to perspective. I'm looking at it from that of someone who might need a bathroom break in the middle of an album, but don't like to pause in the middle of a track. Whereas Peke is looking at the issue from the standpoint of a DJ, someone who might want to stop playback to do... whatever.

Perhaps I need to just leave the issue alone, as after all, I've already stated my opinion on it. Stated it again for a second or third time (actually, what is this... the 12th for me? :oops: ) is unlikely to do anything that the first time didn't, you know?

PS -- Peke, you suggested I(?) try out your plug-in, but... the only thing I found was something from 6-7 years ago(?) and was labeled "beta," so I didn't know if it's suppose to still work or... whatever, so I didn't mess with it. Though honestly, I doubt it would change my perspective much on the matter.

Re: Improve "Stop After Current" functionality

by rusty » Tue Jan 04, 2011 1:07 am

Have a look at http://www.ventismedia.com/mantis/view.php?id=23 . I think that some of the changes discussed there might resolve the issues raised by Peke re. the 'Stop at Next' approach.

-Rusty

Re: Improve "Stop After Current" functionality

by Peke » Mon Jan 03, 2011 9:18 am

Yeah, that is the logical assumption Joe.

Long live and prosper. 8) :lol: :D :roll: :wink:

Re: Improve "Stop After Current" functionality

by JoePublic » Mon Jan 03, 2011 1:58 am

Mizery_Made wrote:Also, if someone has Shuffle on and is looking to play the song directly under the one that is play, turning off Shuffle seems like a more logical reaction than using Stop after Current. <snip> If someone uses Stop after Current, and then hits play a minute or two later, I don't think they're going to expect to hear the track that just played, shuffle or not.
Excellent point, mizery_made. Also, thanks to peke for explaining the Shuffle situation better.

This discussion shows why good software design isn't as easy as it looks from the outside. While wearing my analyst hat, here are a few things I try to keep in mind.
1- Don't break something that works.
2- Don't change the status quo unless there is a really good reason to do so.
3- Don't be quirky. Do be intuitive.
4- KISS - Keep it simple, stupid.

Right now, we seem to have a situation with SaC where it doesn't work intuitively for most people, but the status quo functionality likely has some adherents, at least in some situations. So, there seems to be conflicting requirements, and that's a design problem. The proposed solution "behave one way with Shuffle off, another way with Shuffle on" is at least a little quirky and I think violates KISS. And I don't mean to be presumptuous, but I'm not convinced that it [the proposed solution] best satisfies all users' reasonable needs. I'm thinking more and more that the better solution is either make SaC behavior optionable OR leave SaC alone and create a new Stop at Next function as I described in an earlier post.

Re: Improve "Stop After Current" functionality

by Peke » Sat Jan 01, 2011 9:09 pm

Remember that those two mins are used to add/prepare next track I would rather leave it on played that jump 3000 tracks in list. Also I would want to leave Shuffle on. It is the most when DJ-s work or when you work on radio stations where you put commercials/jingles in between two tracks. That is why I asked you to test my plugin.

Re: Improve "Stop After Current" functionality

by Mizery_Made » Sat Jan 01, 2011 7:37 pm

I don't think "Do Nothing" is an option, as it has been often asked why it doesn't move to the next track, and requested that it does. Also, if someone has Shuffle on and is looking to play the song directly under the one that is play, turning off Shuffle seems like a more logical reaction than using Stop after Current. Even then, there is always Zved's Queue List script which would allow you to insert a track while the current song is even playing. If someone uses Stop after Current, and then hits play a minute or two later, I don't think they're going to expect to hear the track that just played, shuffle or not.

Re: Improve "Stop After Current" functionality

by Peke » Sat Jan 01, 2011 7:37 pm

Hmm, good review Joe.

One correction still regarding shuffle.

Load 4000 Tracks in Now playing and Enable shuffle. If SaC goes to next than it could go from #311 to #3011 and stop :( If I'm on Live performance and would want to continue playback from #312 I added as Play Next I would be losing valuable seconds to scroll thrum Now playing to get back to #312. But in case of No Shuffle issue would be opposite as #312 would be set and I would only need to press play on Keyboard to continue show.

Re: Improve "Stop After Current" functionality

by JoePublic » Sat Jan 01, 2011 2:32 pm

Mizery_Made wrote:Hm, seems that you're right. However, maybe it's not been closed yet because it's not been fully implemented according to the proposal by Peke. It does move on to the next track after the current one finishes... however it does that regardless if Shuffle is on or off (the proposal by Peke has the behavior remain as it was when Shuffle is on).
I've been thinking about this some more & now believe Peke is on to something when he proposes that the Stop After Current functionality remain as it is now when Shuffle is on. In fact, I would now go farther because I think his point is valid even when Shuffle is not on. For example: Shuffle is off. You have a bunch of songs in Now Playing. You use Stop After Current and the song stops. Something non-MM happens (the DJ talks, a wedding cake is cut, whatever). The user decides he wants to select a new song to play next instead of the song already set as next in NP. If SaC is changed to advance to the next song before stopping, it will be a lot more difficult to insert a new song to play next and also maintain the rest of the original NP queue in its original sequence. I think this is just the point Peke was making.

So, some users might prefer the current functionality to remain as is, and I think they have a legitimate reason for their preference. For these users, changing SaC would "break" the function, and that would be a bad thing.

So now, here is my new proposal in descending order of preference. Choose one of:

#1 - Make SaC behavior globally optionable. The user can select if he wants SaC to always advance to the next song before stopping or not.

#2 - Keep SaC as is regarding its behavior of not advancing to the next song before stopping. Create a NEW Stop At Next toggle function that will do the new behavior. If either SaC or SaN function is toggled on, it would "dim out" the other function, so the user couldn't apply both functions to the same song. Or make SaC a three-way "toggle": Click once=Current behavior, Click twice=New behavior, Click thrice=Back to the Off condition.

#3 - Do nothing. The way SaC works now isn't so bad, and it could be made worse. Also, some people might rely on the current behavior and would be unhappy it if went away.

I'm thinking that the current idea to have SaC behave one way when Shuffle is on and another way when Shuffle is off is somewhat confusing. It's certainly more complicated, and one could argue that it is illogical. "Why should the Shuffle function have anything to do with the behavior of Stop after Current?" the casual MM user might ask. "Shuffle and Stop after Current are unrelated controls."

So, even though I initially wanted SaC to change, this discussion has been very helpful & has changed my point of view in this matter.

Re: Improve "Stop After Current" functionality

by Peke » Thu Dec 30, 2010 7:48 pm

I added reference to this post. Have you tried My plugin to see behavior I'm talking about?

Re: Improve "Stop After Current" functionality

by Mizery_Made » Thu Dec 30, 2010 6:43 pm

It may be a good idea though, to post a reply to the bug entry drawing attention to the fact. At least get some confirmation from one of the developers (Ludek specifically, since it's assigned to him) as to whether it's only been partially implemented or if it's how they intend it but just forgot to close the bug.

Re: Improve "Stop After Current" functionality

by nohitter151 » Thu Dec 30, 2010 6:24 pm

Mizery_Made wrote:Hm, seems that you're right. However, maybe it's not been closed yet because it's not been fully implemented according to the proposal by Peke. It does move on to the next track after the current one finishes... however it does that regardless if Shuffle is on or off (the proposal by Peke has the behavior remain as it was when Shuffle is on).
Good point, I think you're right.

Re: Improve "Stop After Current" functionality

by Mizery_Made » Thu Dec 30, 2010 1:01 pm

Hm, seems that you're right. However, maybe it's not been closed yet because it's not been fully implemented according to the proposal by Peke. It does move on to the next track after the current one finishes... however it does that regardless if Shuffle is on or off (the proposal by Peke has the behavior remain as it was when Shuffle is on).

Re: Improve "Stop After Current" functionality

by nohitter151 » Thu Dec 30, 2010 11:36 am

Mizery_Made wrote:
EDIT: Regarding #3, here's the bug entry: 6543: Stop After Current behavior. It hasn't been added yet, but it has been assigned a target version of 4.0, so it should make it in at some point along the development cycle (unless it's deferred to a later release).
I know that the bug in the tracker isn't marked as resolved, but doesn't MM4 already have this implemented? Based on my limited use I'm pretty sure I noticed that specific feature already being implemented.

Re: Improve "Stop After Current" functionality

by Mizery_Made » Thu Dec 30, 2010 2:39 am

JoePublic wrote:
Mizery_Made wrote:#1 - Some of the MM4 skins now have a Stop After Current button on the player, would this suffice?
I probably don't want to use a custom skin just to get this feature, but that's good to know about that option. Thanks for your other comments as well. Now I'm really looking forward to MM4.
Well they aren't exactly "custom skins." Two of the four default skins in MM4 (Pulse and Vitreous) have this button present on the player. However, I must confess that somehow I mixed up what you were saying regarding #1 or... something. I think when I was answering it, I had it in my head that the first point was asking for a button to set it in the NP window or something. However, if my bug report about the button goes through, then it would actually apply to your first point. Currently, it doesn't indicate the state of the "setting," which I feel is incorrect (evident by my report of said "bug")

EDIT: Regarding #3, here's the bug entry: 6543: Stop After Current behavior. It hasn't been added yet, but it has been assigned a target version of 4.0, so it should make it in at some point along the development cycle (unless it's deferred to a later release).

Top