Request sus7 to be special-cased and interpreted as 7sus

• Jul 19, 2020 - 22:04
Reported version
3.x-dev
Priority
P3 - Low
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

Reproduce:

1) Create an empty store
2) Add a sus7 chord symbol, eg. Asus7
3) Start playback and/or right click on the chord symbol and choose "realize chord"

Expected:
A D E G

Actual result:
A D E G#

Workaround
Input Asusb7

OS: Windows 10 (10.0), Arch.: x86_64,
MuseScore version (64-bit): 3.5.0.12799,
revision: fb3c202

Comments

• Jul 20, 2020 - 05:28
Title chord playback: sus7 is performed and realized as susMaj7 ⇒ Request sus7 to be special-cased and interpreted as 7sus
Severity S3 - Major ⇒ S5 - Suggestion
Priority ⇒ P3 - Low

Indeed, MuseScore is more literal than a human musician would be - humans would probably barely notice the typo and realize you meant "7sus". Since "sus7" isn't really a thing, it's conceivable we could add a special case someday to correct the playback.

Reply

• Jul 20, 2020 - 09:05

I didn't realize that A7sus is more correctish. It's interesting that MS does not interpret it as an error and plays something even if it wasn't recognized, though.

EDIT: After seeing Ziya's comment I understand that MS "suspends" the seventh so it becomes Maj7. So you can either "Limit sus string interpretation to valid options" or "be patient for fluid-minded humans".

Reply