Option to highlight chords that are uninterpretable

• Mar 13, 2021 - 15:20
Reported version
3.6
Type
Graphical (UI)
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Tags

MuseScore highlights a chord in red if (and only if) the root makes no sense to it. For instsnce “Dn” and “E???”are not highlighted. “Xb7” is highlighted.

Highlighting is transient, appearing only while the chord is being edited.

It would be helpful if there was an option to highlight chords that have any element that isn't interpretable.

This would help reduce errors and make proofing a piece of music faster.

(This could possibly be done by a call to the playback engine when exiting from editing the chord and setting an error flag in the chord object, and then showing all chords with errors in red.). Alternatively it could be limited to flagging any chord that doesn’t begin with a valid note name or has a character/string in it other than m b # dim aug or a positive integer bewtween 2 and 13(?). (This is probably a subset of the valid characters, but certainly are the 95%common ones.). Users who regulalry write chords that are incorrectly flagged could turn the option off.


Comments

Workaround No Yes

One hint that MusyeScore can't interpret them is playback, it plays only the base note or nothing at all, not any chord
Andother is 'Realize harmony' not doing anything useful on these

Tags View Changes

Should be simple for anyone who wants to implement this to give it a shot, would make a good initial PR for a prospective GSoC student. No need to get the playback engine involved, it's just working from the data structure that is already built when parsing the chord.