Cubase 13 - Changing values with mouse wheel

Interesting point. Or maybe if they don’t want to have to reinvent the wheel themselves, they could ink a deal with Logi or someone to make a super DAW-optimized mouse and sell it for like $200 or something. I’d pay that if it meant never having a value jump on any click & drag operation ever, personally!

Personally, I also don’t like this. I would also expect, the preference to enable/disable all controllers equally without any exceptions. But the current specification is like this. Therefore we cannot call it a bug and we have to request a new feature.

At what point does a “specification” cross the border into “bug”? This reasoning is diluting the terminology. With that logic you can take anything that is malfunctioning, print it in the manual and call it “by design”.

We’re not requesting a new feature, we’re requesting a fix for the feature that doesn’t work and/or is not done, printed in specs or not.


Someone at Steinberg (a Product Owner) creates the specification. He/she says, how should Cubase behave. This behaviour is written in the manual.

If Cubase doesn’t act according the specification, then it’s a bug.

If Cubase behaves according to the specification, but a user doesn’t like it, he/she can make a feature request and ask for a change of the specification.

I used to work in software development as well and that is a tricky topic indeed. Since there is no universal law for what is right or wrong, Martin’s reasoning is correct: If it behaves as defined, it’s considered to be correct.

Therefore, we are not dealing with a bug but with a very odd definition of the functionality. I wonder how the user story for this feature looked like…“As a user I want to be able to screw up all my fader values by just using the mouse wheel”. :face_with_hand_over_mouth: Please excuse the irony…




Of course the use case is simple: I want to edit any parameter value by using mouse scroll wheel.

But then, once you start to use it in the real word, you find out, the Faders don’t work for you in this case. So you have to make an exception. Then you realise, it’s dificult to remember this exception, because you have to remember lots of exceptions accross the whole application and it’s not consistent. So you set a new rule: consistency. Therefore you remove the exception and the Faders are controlled by the scroll wheel again. Then you realise, you would need an exception for the fader, then you realise it’s not consistent… :slight_smile:

1 Like

That sums up the dilemma of software development in a very accurate way. :laughing: So maybe it would be good to take a step back and define two usecases. Either I want to edit any parameter value by using the mouse scroll wheel or I don’t want to edit any parameter value by using the mouse wheel and use the mouse wheel exclusively for scrolling in the mixer window and implement that as two options. The current implementation tries to combine both approaches and creates a bit of a mess, so it might be worth rethinking it.


I also work in software (game) development, and it’s not that I don’t understand the reasoning behind your argument @Martin.Jirsak, it’s just that the logic behind this “feature” narrows it all down to two options:

a) There is some really odd technical limitation that makes it impossible to exclude the scroll wheel from interaction with faders/panning, which I don’t believe, or:

b) the specification was written after the feature was half-done and/or the bug was left in and the specs were changed due to budget restrictions/ending of dev scope.

The third option:
c) …someone thought this was a good idea,

… is simply so insensible I just can’t believe anyone in their right mind would come up with the idea. Even less likely the idea was approved by others. And when this was in testing stage, even less likely that no QA or beta tester would report the flaws in this design choice.


This user sums things up perfectly. It would be great if anyone from the development or design team could take a look at this and reassess the current behaviour.

@Martin.Jirsak is there any chance that you could forward this post to the right people?

1 Like

It’s a sad irony because it’s true.

1 Like

Another irony: it’s called SCROLL wheel. In 99% of other software it’s used for scrolling - not changing values. Even if only for the enormous heritage of existing software, forcibly using the mouse wheel for other activities besides scrolling doesn’t make any sense in my opinion. It’s not even good for that because depending on the mouse it can be too imprecise.

Just imagine if “scrolling” in Excel could also change the cell values if you’re not careful.


Push and hold scrollwheel : you can vertical scroll from every mouse position

You can typically set the scroll speed in your OS and/or your proprietary mouse software if it came with any. In addition to that, you can press and hold the Shift key to get finer control of values with the mouse wheel.

But in some cases it is not. CAD software use the mouse wheel for zooming e.g. In Windows OS you can use the mouse wheel to change the audio level in the Volume Mixer. Using the mouse wheel to change volume is actually quite common in several user interfaces.
I’m of the opinion that you should learn the tool at hand. Using the mouse wheel to change values is an immensely powerful feature once you master it. It greatly increases productivity by speeding up editing in several areas of the program.

Setting the scroll speed is, therefore, dependent on the OS/platform/mouse/mouse software used. It might work worse or better, which is not good.

Zooming and changing volume is not a destructive action in terms of the work you are performing. Also, I’m not offended, but please don’t patronise me assuming that I don’t know how to use the tool. I DO know how to use it and in my opinion it sucks and I constantly get errors in my work because of it since my workflow, in order to be fast, depends on scrolling in the mixer without having to be careful and point the mouse to a tiny strip of screen.

Also, I don’t want the featured removed since you and others seem to like it. I just want an option to turn it off COMPLETELY.

I’m sure it’s not the case, but at this point it seems like stubbornness from the designers.

1 Like

Exactly what @OFS says. If @mlib is one of the few users who actually like the current implementation - so be it. Make it an option and everybody‘s happy. But I strongly disagree with the statement „Learn the tool“. That makes sense if the tool makes sense. But it doesn‘t. At least to me and apparently many others.

Absolutely agree.