This issue is definitely not entirely hardware related. I’m not even convinced that it’s partially hardware related because those claiming so haven’t really provided good evidence.
As I explained in another thread, this issue is at least partially (likely entirely) caused by the cursor position moving while clicking in regions with click-and-drag functionality without a movement/time threshold.
Users with high mouse sensitivity are more likely to be affected than users with trackpads or low mouse sensitivity because if a box lacks a movement/time threshold, the cursor position needs to be identical during press and release for a normal click to be registered. If the position differs by a single pixel, a click-and-drag will be registered instead. A movement/time threshold simply prevents a click-and-drag to be registered unless the cursor has moved by a certain amount of pixels (movement threshold) or if the click duration exceeds a certain amount of time (time threshold).
It seems that at some point in version 15, Steinberg added movement and/or time thresholds for input boxes but only those activated via double click (like the upper section of the mix console), single click boxes still suffer from this issue.
To those claiming this is hardware related, please do the following test in the latest versions of Cubase 15 or 16:
- Click + drag up or down on the send level field in the mixer. Notice how the value only starts changing after roughly a second or if the cursor moves a lot. You should clearly see the outline of the box changing color to indicate click-and-drag is now active (see video).
- Click + drag up or down on the channel volume field in the mixer. The value should change immediately as you mouse the cursor because it doesn’t have a movement/time threshold (see video).
If you’re experiencing exactly the same behavior, then it’s very likely not hardware related. The Steinberg team is probably confused because people are claiming that it only affects double clicking, or that it’s hardware related (while also claiming the behavior changes depending on the area of the interface), so please do the test and clarify if that’s not the case.