Changing Measure Properties>Actual value doesn't affect all "range selected" measures. -//- Metric issue when importing Encore MuiscXML

• May 29, 2022 - 22:28

I still run into issues with Encore to MusicXML to MuseScore.

Presently, after MusicXML import, I have a score where every measure is set to 4/4 meter (i.e. Measure Properties>Actual). The original and intended meter (Measure Properties>Nominal) is 3/4 throughout. Notationally there are three beats of notation followed by a beat of rest. The question here is not how this came to be, but how to fix this in a few steps.

An "obvious" easy fix for the metric conundrum would be:

• select all in MuseScore
• open Measure Properties
• set Measure Duration>Actual = 3 (changed from the erroneous value of 4)

Interestingly, with all measures selected, MuseScore allows access to the Measure Properties dialog and the two Actual property fields are enabled, so the venture seems promising ... but, on OK, the impact affects only the last measure of the selection.

Is this by design? The last measure is perfectly corrected because the extra time was at the end 3/4 worth of notation (i.e. all the notation is preserved; just the empty time is removed by correcting Actual to 3. It would be great if there was a way to apply the change of the Actual property to the entire selection.

I'll upload scores later, but this behavior is easily reproducible:

• Enter four measures
• fill each measure with four quarter notes
• select the four measures
• open measure properties
• set Measure Duration>Actual = 5 (or 3)

Note that the result only affects the last measure of the selection.



In reply to by jeetee

Thanks for your input jeetee.

jeetee wrote >> Yes, it is by design ...

I'm curious about the reasoning for that design:

• First, as mentioned, it's interesting that MuseScore applies the result only to the last measure of the range of selected measures. How's a user to know? Trial and error?

• Second, when an action cannot be applied to an entire selection I'm accustomed to "access block" by a disabled menu item ... or a disabled field or button in the dialog.

jeetee wrote >> ...notice the small buttons on the bottom of the dialog to change the affected measure.

I had not noticed the nearly hidden pair of arrows in the lower left corner! The online manual states:

"You can use the Previous/Next buttons ← →, at the bottom left of the dialog, to navigate to the previous or next measure."

indeed, they serve the purpose as described by the Handbook, but I don't see how that affords a significant advantage, other that not needing to close and reopen the dialog. Maybe somebody got in a similar situation and devised a half hatched "solution"?

A large Apply to Selected Range button would be a perfect companion to those little arrows. But as you know, I think "apply to selected range" should be the default behavior. You're saying there's a specific design reason that it's not?


In reply to by scorster

I tested a couple of other properties (in Measure Properties) to see if they impact the entire selection. And the answer is no.

With four measures selected, I open Measure Properties and toggled Stemless. With the same selection I tried again toggling Exclude from Measure Count. In both cases, on OK, I find MuseScore applies the result only to measure 4—the last measure of the selection.

Interestingly, I couldn't devise a circumstance where the Invisible checkbox is enabled. If that option is not "enablable" it shouldn't be in the dialog.

Am I missing something? All this behavior is by design? If so, what's the wisdom therein?

Seems like a faulty and needlessly restrictive dialog to me. If there's agreement on this I'll gladly post a request in the Issue Tracker.


In reply to by jeetee

jeetee wrote >> The "design" part is that that dialog is only intended to work for a single measure selection.

I have a difficult time understanding the rationale for restricting the impact to a single measure. A problem with the undo stack?

Measure Stretch seems innocuous, and we can apply it to multiple measures via keystrokes. So why is the dialog guarded against applying Measure Stretch to a selection of multiple measures? A misguided case of "Not in my backyard"?

jeetee wrote >> The UX bug is that it can be opened when you have a bigger range selected.

Noted. Alternately the "UX problem" goes away if the rationale is dethroned and the dialog is allowed to affect the selected range of measures.

Granted this is all moot if v4.0 has remedied the problem. Do you know? (For various reasons I don't have access to the v4 nightlies.)


In reply to by scorster

To my knowledge it was simply never designed to work for multiple measures. Is that a good design? Probably not. Should/Can it be changed? Almost certainly.

I have no real hands-on experience with the nightlies yet and can't recall a specific change to stand out about this.

Do you still have an unanswered question? Please log in first to post your question.