3.0 Beta - Mixer Volume Slider does not move with mouse

• Dec 2, 2018 - 03:08
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project

When operating the Mixer Volume Slider for individual instruments, it does not move with the mouse and sometimes goes in the wrong direction.


Comments

Severity S4 - Minor S3 - Major

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

I can confirm. Any attempt to move the volume slider causes it to shoot up to 100%. It can only be freed by closing and reopening the program.

Status duplicate active
Priority P1 - High

Sounds like you are saying the channel sliders don't track the mouse well. I can confirm this is still an issue. i am not sure if any of the other reported issues or pending fixes will turn out to be related or not. Let's keep this open until we can verify for sure.

In reply to by Anatoly-os

Running nightly 39501b5 macOS and it is better than previously observed but still not ideal.

Using the mouse to slide the slider the knob jitters, it goes up initially when sliding down and vice versa it takes a lot of movement with mouse to get it to go in direction you want. Using mouse scroll to adjust setting is 100% reliable. Channel focus highlight doesn't shift when selected Beta version is similar but jitter is worse

Priority P0 - Critical P1 - High

It looks a ton better to me. I think what I'm seeing left is the result of rounding of values to integer. Like, if I drag from 54 down a little past what would be 53, the numeric value gets rounded to 53, and thus the slider is pushed back up. And yet this doesn't happen dragging up. Is this what you mean? If so, let's leave this at P1 and deal with as we can.

In reply to by Marc Sabatella

It is a work in progress in a more useable direction and I agree it is a lot better. Using the scroll button on the mouse is an easy work around.

MIDI port and channel selection / editing the responsiveness to selecting a volume channel highlight is also flaky and probably all interrelated.

Plenty of things causing crashes to get off the hit list.

The progress in the build is something for the team to be proud of.