I seem to be in a minority in this thread, but I have absolutely no problem with the current behavior and I love that I can change every parameter with the mouse wheel. And I know where to put the mouse pointer if I want to scroll through the mixer horizontally, so that is no problem either.
So from my point of view: please don’t change too much! I agree that using shift+scroll for horizontal movement would make it more consistent with the behavior in the arrangement or editor windows, so that is something to consider, but moving fine tune to Ctrl+wheel would be of course a breaking change that would bother a lot of people who have shift+wheel in their muscle memory…
The question is: is it Okay to let us relearn a single key command in order to render Cubase more consistent and to speed up workflow?
I would say: absolutely yes.
I’m very curious about this, but couldn’t figure out what you meant. Can you please explain in more detail, or maybe post a screen shot of where to find this option? Thanks!
So, I was well aware of mouse movement can cause parameter value changes on ‘CONSOLE’ window and here, I am not talking about 'console window ←
I strictly am talking about the main view, so lets say,
I am on track 100: String (reverb send) print wav, then I want to solo monitor my track 1 piano track…
So I move way up by scrolling right?
So on track view LEFT panel, there used to be volume value appearing for tracks and groups for my case, but now I hid it.
It is no longer there and I can always just adjust on ‘console’.
MAIN window, bottom:
‘OPEN TRACK CONTROLS SETTING DIALOGUE’ <— click this,
you can adjust many features including writing letter numbers upto like 14.
So, now everything is the same, just, volume parameter option is now gone for me because,
I scroll up down so quick that I cannot even double check when I am mixing… so hope I made myself clear.
So, console <— mouse scrolling <— has not been fixed yet I believe. and I am only talking about the main window
Ah, thanks, that explains it, and I know what you mean now!
1 Like
Also, one thing I realised was,
My issue was not solely due to Cubase but also Magic Mouse too because, finger touching sense lags and sustains a bit, so that was the reason why Cubase thought it wanted to move…? I am sure with other mouse, it would not be an issue… but um… I enjoy using Magic Mouse so, I shall just find my way around… 
‘BetterTouchTool’ ← also another great tool on mac to customize with your whatever mouse u have
Maybe in the minority, but not alone! 
I utterly love how you can change any value in Cubase using your mouse wheel. It’s consistent and brilliant imho.
That said, I don’t scroll around too much in the Mixer window though. Instead, I utilize multiple Mixer Consoles as well as Channel Visibility Configurations to narrow down the channel count.
I don’t think you are in a minority. We ALL (I hope!) love to use the wheel to change values. The problem is when we think we’re scrolling, which is for me an “unattended” process (I’m fully relaxed and not alert at all when scrolling), but instead we’re changing important values. Just by using Shift+wheel for scrolling and leaving fine parameter change alone, we could ease the problem by a factor of 10, since we wouldn’t be making BIG unintended changes, but FINE ones instead. Of course, the problem would remain, but wouldn’t be as bad.
Changing Shift to Ctrl for fine parameter change, I won’t lie, I’m very used to using Shift too. But for project safety, I would be willing to relearn that. Plus, we could then “CONTROL value” literally. 
For everyone that likes the current behaviour, once again guys, I’m talking about a preference. If it’s disabled by default the current behaviour should be exactly the same so that it doesn’t throw people off, but for those of us who don’t like it (I REALLY hate it) it’s there for us to change.
2 Likes
Today an idea for a workaround came to mind:
Do any of you guys who are on Windows, use Autohotkey?
I use it for everything inside of Cubase, where there is no easy integrated function.
It should easily be possible to make a script like this:
- If MixConsole is the active Window and
- If CTRL+Mousewheel is used (you can use your preferred key+mousewheel of course, SHIFT or ALT i.e.)
- Then move mouse directly to the scrollbar position at the bottom of the window and scroll
- After scrolling reposition mouse where it was before
Like this, you could scroll fast and easy everywhere in the mixconsole, without changing any value accidentally and without sacrificing any of your mousewheel functions.
I might make a script myself, just hit me up if you’re interested.
2 Likes
AHK is good, and you can do much with it, but in the end it requires maintenance as everything else (checking if the scripts still work with each version if you use imagesearch or any raw mouse coordinates). I was using it much on my laptop (mostly keyboard shortcuts because I am very trackpad-challenged) but nowadays I’m mostly on my desktop so it doesn’t offer much to justify the effort.
If you manage to build something good, please post it!
Edit: Since the idea excited me, here’s a quick test using Caps Lock.
Note: Anyone interested will have to replace 1911 with their own number. Use the window spy included with AHK to check what’s the height at the center of the scrollbar. Try 1070. ish. If you’re on 1920x1080.
Warning: If window focus is in the mixconsole but your cursor wanders over to the project window, the script will still work and teleport your cursor to the bottom when you keep Caps Lock down.
Hey, it’s fun! Didn’t think it would be so easy!
2 Likes
Glad to see it worked!
Yeah, you basically have to rework all parts where you have mouse positions in it. You could automate it somehow, where you check first what your DPI is and your resolution and implement that, but since I am always on a 4k screen with 150% DPI, I’m fine with it!
Instead of Mousemove, xpos, 1911 you could have calculated the height and length of the window, its position and then go from there, but still. Well done!
I’ve written some scripts now as well, feel free to use them if you want. I included 3 variants for you which work when Mixconsole is maximized. This will react directly to SHIFT or ALT or CTRL+MOUSEWHEEL and blocks at the same time all other inputs, so you don’t have to fear, that by moving the mouse accidentally, there will be changed something.
This will not change any mousewheel behaviour in other windows, like the project window. And if you choose CTRL+MOUSEWHEEL or ALT+MOUSEWHEEL it will not interfere with any mousewheel actions in the mixconsole either (I only added SHIFT+MOUSEWHEEL, because there might be some people who prefer to use it for horizontal scrolling like in the project window, thats about the only case where fine tuning volume/PAN would not work anymore).
The only thing you would have to do is to change the Y value like in the scripts from @ggmanestraki
Here is the full script in text, just copy it in your AHK file. If the scrolling is to slow for you, just add another line of send {WheelDown} or send {WheelUp} underneath the existing one and scroll speed will be increased.
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
;^ stands for CTRL
;! stands for ALT and
;+ stands for SHIFT
#IfWinActive MixConsole
^WheelDown::
CoordMode, Mouse, Screen
Mousegetpos, StartX, StartY
BlockInput, ON
;Change the 2064 value below to match your display setting
MouseMove, StartX, 2064
send {WheelDown}
MouseMove, StartX, StartY
BlockInput, OFF
return
;^ stands for CTRL
;! stands for ALT and
;+ stands for SHIFT
#IfWinActive MixConsole
^WheelUp::
CoordMode, Mouse, Screen
Mousegetpos, StartX, StartY
BlockInput, ON
;Change the 2064 value below to match your display setting
MouseMove, StartX, 2064
send {WheelUp}
MouseMove, StartX, StartY
BlockInput, OFF
return
Hope that helps!
PS: I always run these scripts as admin.
2 Likes
Since where already here I also made a version, which works also when the Mixconsole Window is not maximized, basically everytime. I made a little video to show what it does (to demonstrate I wildly scrolled up and down holding CTRL over different positions in the Mixconsole). Below the video you will find the script.
Again if you want to increase the scroll speed, add another line of send {WheelDown} or send {WheelUp} underneath the existing one.
You only might have to edit the -25 value if it does not work, more info below the script:
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
;^ stands for CTRL
;! stands for ALT and
;+ stands for SHIFT
#IfWinActive MixConsole
^WheelDown::
WinGetActiveStats, Title , Width2, Height2, X2, Y2
CoordMode, Mouse, Screen
Mousegetpos, StartX, StartY
BlockInput, ON
;you might have to edit -25 to fit your display setting
MouseMove, X2 + Width2/2, Y2 + Height2 -25
send {WheelDown}
MouseMove, StartX, StartY
BlockInput, OFF
return
;^ stands for CTRL
;! stands for ALT and
;+ stands for SHIFT
#IfWinActive MixConsole
^WheelUp::
WinGetActiveStats, Title , Width2, Height2, X2, Y2
CoordMode, Mouse, Screen
Mousegetpos, StartX, StartY
BlockInput, ON
;you might have to edit -25 to fit your display setting
MouseMove, X2 + Width2/2, Y2 + Height2 -25
send {WheelUp}
MouseMove, StartX, StartY
BlockInput, OFF
return
In this script I calculate the position and the size of the MixConsole window by using
WinGetActiveStats, Title , Width2, Height2, X2, Y2
X2 represents the X coordinate of the upper left corner of the window, Y2 the Y coordinate of the same corner.
If you add the height of the window to the Y2 coordinate, you basically have the bottom corner Y coordinate. From there I do -25 (Pixel) to move the mouse up to the scroll bar.
Now if you have a 1080P screen and DPI set to 150% or a 8k screen with 100% DPI it might be, that you need to use a much different value to reach the scroll bar from the bottom up, as the scroll bars will have different sizes in that scenarios ( I would try values from -15 to -40 if it does not work).
I hope I explained it well, have fun!
4 Likes
All these scripts are cool but I’m on Mac so, no dice…
Yeah, for MAC users these scripts obviously won’t work, but most users seem to be on Windows here, so for them this can be a good workaround. I heard about Hammerspoon for MAC to do similar things, but I don’t have any experience with that. Might be worth a read:
Wow, thanks man, I’ll check this out!
Yes you can
Studio One also does this. I can’t stand it… Reaper has it on by default, but you can (of course) turn it off
I’ve been seriously demoing Cubase for the last few weeks with a strong leaning towards buying it and making it my main DAW. It has SO much cool stuff and it’s a pretty complete DAW in my opinion. However, I gave up on the idea based on small stuff like the one being discussed in this thread. When I found out that folders aren’t reflected in the mix console, I realised my big mixing template is a total nightmare to move around in the mix console with so many tracks, especially if using the bottom screen mix console instead of the main mix console window. Having to go to that small, thin section of the console to move around left and right, which I do a lot is just infuriating and a big workflow killer for me.
Evaluating DAW’s is very tricky for me because you can have an amazing piece of software like Cubase feel like crap while using it because of such small details like these.
I’d just like to give my final 2 cents regarding these issues with the mouse wheel. In 99% of all software the mouse wheel is a tool for navigating around the apps. It’s like this for browsers, word processors, spreadsheets, OS file managers, you name it. For better or for worse, historically, that’s what software has us expecting from the mouse wheel. Subverting the expected use of this device to suddenly change parameter values in a very niche class of software applications like some DAW’s (and even in DAW’s it’s not all of them that do it, Logic and PT don’t have this “feature”) is, in my opinion, a crass usability mistake, if only for the expected typical use of the mouse wheel ingrained in us by the vast majority of other types of software applications. The people that had this idea got it the wrong way around. Mouse wheels are for scrolling, that’s how God intended them 
. Having them do a secondary function such as changing values can be useful and a good idea, but NEVER should it be considered it’s primary purpose or default behaviour.
Anyway, I’ll keep checking Cubase regularly to see if any of these issues are addressed, but meanwhile I really, really regret I can’t make it my daily driver, it’s just too frustrating.
3 Likes