Improper behaviour of Ambitus (Octave, Positioning etc.)

• Jul 11, 2018 - 16:09
Reported version
3.0
Type
Graphical (UI)
Frequency
Few
Severity
S3 - Major
Status
active
Regression
No
Workaround
No
Project

Please refer to the video. It is hard to explain in a few words.
Same behaviour in MuseScore 2.1 and 2.2. (2.3.1 ends in crash.)
Video recording version:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (32-bit): 3.0.0, revision: 206532b

The file is "double-compressed" — by using zip it will exceed the 4 MB limit, but here does not accept rar file. So an rar file is put inside a zip file.

Sorry for bad English, and too many issues created in a short period. I just want to report bugs.

Attachment Size
MuseScore3.zip 3.48 MB

Comments

Frequency Many
Regression No
Workaround No

It still happens in 3.0 stable version.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4785, revision: c1a5e4c

Severity S4 - Minor S3 - Major

I see. If you try to manually adjust the octave of the notes by entering a number, the number usually changes to a lower number. Seldom it will keep the entered octaves. The top octave seems to change to 1 octave below what is entered and the bottom octave doesn't like to be within 1 octave of the top, it will lower the octave 1. I did manage to make both octaves 1 though.

I set the ambitus range to C1 through E1 (using notes on the staff and the Update Range button) and can't even select the ambitus any more. I then got the clef on the time signature as in the picture.