Mixer: size issues
Reported version
3.0
Priority
P2 - Medium
Type
Graphical (UI)
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4095, revision: 5859662
There are a number of problems with the mixer:
- It is too wide. 7¼" on a 1680 x 1050 screen—that's more than a third the width of the program window even when maximised. By comparison the mixer in 2.x is usable at a width of 3¾".
- The width is the same no matter how few or many instruments. The user needs full control of the width. The MIDI section should be collapsible.
- It is too high. 7" on a 1680 x 1050 screen—more than half the height of the program window even when maximised).
- The controls are too large. Could they be scaled down?
- The old vertical mixer had the advantages of small width and ability to view a large number of instruments at once.
Comments
In reply to (No subject) by Marc Sabatella
Sounds more like a suggestion than a bug to me.
And perhaps the option of a vertical or horizontal mixer layout?
It also automatically reverts to default if you Show detail. You should be able to resize it with the details showing, but only the section with the sliders become smaller like when the details are hidden.
See https://musescore.org/en/node/289790 for a proposed new Mixer design based primarily on accessibility requirements.
Had to bypass this problem with the settings on Windows 10:
Window properties:Scaling 150% (recommended)
Screen size 1920x1080 (recommended)
MuseScore Edit/Preferences/
- General tab: icon width/height 16px and 16px
- Font face:Arial Narrow size 9.
Or settings file: %APPDATA%\MuseScore\MuseScore3.ini
Section:[ui] (settings might affect other calculated values in the ini file, so if it does not work then change with the User interface.)
Still after this some windows have to be adjusted by size dragging. For example the Mixer View/Mixer will always overflow when you expand the lower part. So you will need to resize it every time to get it into view.
Hope this helps. Please fill in if you have a better solution.
If I'm not mistaken the "reported version" field refers to the version the issue was first reported for.
indeed