Highlighting Actual / Nominal Bar Duration
I see that Bars/Measures where the Actual vs Nominal Bar Durations are different MuseScore alerts to this with a small grey + or - sign. I gather that this sign will not print so I am wondering if this sign could be in a bright red colour or bright purple so it is easier to see.
I have imported a number of scanned to xml files where the import seems to regularly make the Actual bar duration for example 7/8 where the nominal duration is 4/4 and should in fact be 4/4.
Highlighting this break from the norm is useful and I like the way it is currently done in MuseScore but i would find it easier for editing purposes if the error mark was easier to see.
Is there a preference/setting I could alter to bring this about or would this have to be a feature request?
Please note that the score mark to which I refer is at the end of the straight line in this image but is partially obscured by the selection boundary line.
Attachment | Size |
---|---|
Screenshot from 2023-02-09 15-00-06.png | 86.43 KB |
Comments
Mcl1552 wrote> I have imported a number of scanned to xml files where the import seems to regularly make the Actual bar duration for example 7/8 where the nominal duration is 4/4 and should in fact be 4/4.
I get this sort of error sometimes when importing MusicXML of Encore or Overture provenance. Thanks to the advice of Doug Kerr and discussions with Leon Vinken I've been guided to some good workarounds ... but they're not always reliable. Plus Leon improved the EML import to account for Encore and Overture MusicXML coding.
That said, when MusicXML problems persist— in MuseScore3.6.2, post import—I can fix each measure individually by changing Measure Properties>Nominal (as in Mc1555's example) from 7/8 to 4/4.
scorster
In reply to Mcl1552 wrote> I have… by scorster
Following up on the previous post, there's something awkward and limiting afoot with the Measure Propereties dialog:
When I select a range of measures, MuseScore 3's Measure Propereties menu item is enabled, allowing me into Measure Propereties dialog, but any property changes apply only to the last measure in the selection! Bummer, as this would be an easy way to correct this type of meter corruption.
Interestingly in MuseScore 4, on opening the Measure Properties dialog, MuseScore changes the selection to the last measure of the user's range selection—as if a coder realized the problem without fully addressing it.
I'd venture that it's bad UI to change the user's selection spuriously and without warning.
I don't see what the conflict is with setting Measure Properties on a range of measures. If MuseScore want to restrict that facility for certain properties, why not disable them in the dialog?
Scorster
In reply to Mcl1552 wrote> I have… by scorster
For 3.6.2 you can use the Time Signature Enforcer Plugin to automate that specific task.
In reply to For 3.6.2 you can use the… by jeetee
Thanks jeetee! I got your "Time Signature Enforcer" plugin working on selected measures, so that will be quite helpful at times. I'll try it the next time I encounter metric corruption where the notated measure content "looks" fine, and the Actual Meter is correct, but the Nominal meter differs and/or isn't a proper fit.
That said, the plugin's instructions are rather terse. In total:
• Clip or Expand measures to fit their current time signature.
• The plugin runs either on measures within a range selection or on the full score if no range is selected.
The second line speaks for itself.
However, regarding Clip or Expand measures to fit their current time signature—does that mean that the plug-in sets the Nominal time signature to the Actual time signature?
• If so, perhaps a word of caution is in order when the score or the selected passage includes pickup bars.
• If not, what does the plugin actually do?
Lastly, do you think the MuseScore v3 & v4 Measure Properties behavior is oddly and needlessly restrictive?
In reply to Thanks jeetee! I got the… by scorster
>> "does that mean that the plug-in sets the Nominal time signature to the Actual time signature?"
The other way around. The plugin will alter the measure duration so that the actual time signature of it will match the nominal set for it.
If you have an anacrusis/pickup included in the selection on which it runs, it'll lengthen that measure to match the time signature as there is no difference internally between an anacrusis or any other shortened measure.
In reply to Thanks jeetee! I got the… by scorster
As for the measure properties dialog being restrictive; it's one of those "hysteric raisins". It just was never developed with multi-measure selection in mind. To that end I prefer that it currently alters the selection to make it visible that that is the case.
But yes, there is no reason for it to not be redesigned and/or consolidated into the properties panel in MS4 to allow for more multi-measure settings to be easier changed.
In reply to As for the measure… by jeetee
See https://github.com/musescore/MuseScore/issues/13678 fir a similar request to allow invisible score elements to be displayed in different colours.
From its status "Done in [MU4.0 interface]" it seems like it should be ready for implementation. However, it's not clear how/when/if that will happen as I can't find a pull request for it. In fact I see no PRs at all in that Git Hub Project
In reply to See https://github.com… by SteveBlower
Some clarification on the how/when/if question here https://github.com/orgs/musescore/discussions/16289