The global influence of Loop Playback
MuseScore 3.6.2
Never occurred to me that MuseScore's Loop Playback is a global setting (in v3.6.2.) I guess I'd never switched documents with Loop Playback toggled ON.
But today I switched documents after toggling Loop Playback ON, and in all open open scores I saw Loop Playback's blue triangular Loop flags a) surrounding any exisiting selection (notes or measures) or b) surrounding the entire document in scores where no selection existed.*
Sure seems that users would trip on the global session effect when working with multiple windows open.
I have a difficult time imagining or describing a plausible use case in support of a global Loop Playback setting. A score setting makes far more sense to me—then scorist could use Loop Playback and switch to playback selections in other documents without needing to toggle it off.
* Case b) is rather benign, but suggests that a portion of the Loop code makes it look as if the entire document is selected, when if fact it isn't. Perhaps that was the simplest way to deal with the issue.
scorster
Comments
Works this way already in MU4, since different scores are in different windows and run as different program instances.
In reply to Works this way already in… by Marc Sabatella
Excellent!
I hope the new non-global behavior follows suit for certain other toolbar cast members.
In reply to Excellent! I hope this… by scorster
It’s pretty much two completely separate programs running at once, so, yes. Not sure it will stay that way forever, but now, everything is independent.
In reply to Excellent! I hope this… by scorster
I don't see that as excellent at all, rather a big regression !
In a rehearsal session with musescore I need to set these options for all the scores at once and musescore 3 does exactly what I expect.
In reply to I don't see that as… by frfancha
I'd support an option for such settings operating, at the user's preference, as document settings or global settings.
scorster
In reply to I'd support an option for… by scorster
If they are separate processes, there's really no way for changes made in one to be seen by another. But, if you do want to enable loop in each score, it's one extra click per session - hardly a "big regression".
In reply to If they are separate… by Marc Sabatella
"If they are separate princesses, there's really no way for changes made in one to be seen by another"
https://doc.qt.io/qt-6/ipc.html
In reply to "If they are separate… by frfancha
OK, indeed, it's technically possible. But definitely not straightforward, and also desirable most of the time. While I can understand in your special situation you might want to have loop enabled for every score, itś certainly not the norm. But once 4.0 is released and a process is set up for making feature requests, certainly it could suggested for eventual inclusion.
In reply to I don't see that as… by frfancha
These things are best configured as a preference, surely, not having to be one way or the other.