I have demoed Cubase several times and really like it but theres one thing I just cannot get used to. I use a magic mouse and if I am say in the mixer, and want to scroll across the mixer if I am anywhere near pan or sends etc I end up adjusting that parameter, same for up/down scrolling on faders. I do not have this problem in any other applications I use. Even close to a parameter for a split second and it is active, is there anyway to disable or adjust this setting, I would rather knob/fader scrolling only to be active after I have actually clicked on that particular parameter or when hovering over the actual knob/line etc or even not at all. The fader could be at the very bottom, I could be at the very top and right over the other side of the channel and it still moves the fader when scrolling.
Is there any preference settings or workarounds for this? I have messed around with the ‘controls’ in prefs but they didn’t help. Surely I am not the only person who dislikes this?
Thanks for you’re reply, I have tried changing the setting within that window of preferences with no luck.
An example of what I mean, If my mouse pointer is in the pan box (I have not clicked on the pan parameter) if I try and scroll the mixer the pan parameter changes. This means every time I want to scroll I have to position the mouse pointer somewhere where there is no parameters.
Ideally I would like to disable the mouse wheel on all knobs/sliders and faders like you can with volume and fade, or at least only make it adjust a parameter after clicking the parameter in question.
Yeah, it is stopping me purchasing it, I don’t think I could get used to it. Do you think it is something Steinberg will implement in the future?
I use Logic Pro X and Pro Tools at the moment, Cubase seems like it has the best of both these applications, so I guess I will have to watch this space.
I can only hope Steinberg will maybe this element optional/tweakable in the next release(s). No idea if they will. I use Cubase for most compositional work and idea demos and I love it for that. But I always mix in Pro Tools and it’s mainly because of this issue (plus the lack of mixer undo). I just can’t roll with the workflow… We will watch this space together.
There is a free app called ‘Better TouchTool’ that allows the user to do some
additional fine grained tweaking on your specific input device (mouse/trackpad etc).
+1
My biggest annoyance.
An annoyance that is exacerbated by the fact that CTRL-Z won’t undo whatever move you accidentally made.
It will undo something you did a few minutes earlier. Hopefully you realise and hit CTRL-SHIFT-Z, otherwise you just undid something you didn’t mean to.
You then need to try and workout which fader you moved and what it was set at before.
Use the mixer configurations assigned to key commands for scrolling horizontally. Scrolling the racks vertically can take a while to get used to. You can only really do it in the empty spaces and this becomes problematic on large, busy projects. I do not use the Channel Strip section in the mixer at all. I keep it closed at all times because of this. When I do use the channel strip, I only edit it in the edit channel window. This plus the broken “bring mixer to front” key command and the lack of info displayed without hovering almost had me switching daws. It has been years now…since Cubase 7/Nuendo 6.
One of the popular complaints about Cubase Pro 8 was that the scroll wheel on the mouse affects faders in the mixer when trying to move up to see inserts and such, and I wonder if that issue was fixed properly on the 8.0.20 version…
This may be a little off topic, but, at the Cubase Pro 8 seminar, the German developer said that the Mix-undo function is not going to happen any time soon. And there is a very good reason for that.
If and when that is implemented, it seems like it will take a lot more computing power to achieve that.
Which is bad news for people with lower-grade CPU/GPUs.
I am not a professional, so what I remember is him talking something about along the lines of “limited buffer size”(?).
And another guy in the audience asked if it’s in any way possible to follow the Adobe Photoshop Action History function (which is quite interesting), and the developer told us that it doesn’t work that way
Other DAWs seem to have worked out a way to provide mixer undo without taxing the CPU (at least not to any noticeable degree that impacts the user experience).
Granted the Cubase mixer is not the same as other DAW mixers, but it seems strange that other DAWs have no problems implementing mixer undo
This may be a little off topic, but, at the Cubase Pro 8 seminar, the German developer said that the Mix-undo function is not going to happen any time soon. And there is a very good reason for that.
If and when that is implemented, it seems like it will take a lot more computing power to achieve that.
I am sorry but this makes no sense.
No offense to you, absolutely not, but you may have misunderstood him, or he was not really a developer but maybe a sales person. If he was indeed a developer and you did not misunderstand, this is pure and simple BS.
The undo stack does not need to be computed but simply stored in the memory and then recalled on demand, that means it is not a process that needs to run in parallel with anything. The memory usage for undo may have been a concern 20 years ago when every kilobyte had to be wisely used, but the CPU processing has and never had anything to do with it.
For an application like Cubase the amount of RAM needed for the undo stack will be absolutely negligible given the fact that nowadays everybody has gigabytes of RAM installed, especially when we’re talking about the mixer and the fact that it’s mostly knobs and fader changes we would like to be able to undo/redo.
Most of the values that the mixer or a vst are changing are either booleans (the solo button for example = 8 bytes), integers ( transpose for example, which require 16 bytes memory space) or floats (faders and knobs = 32 bytes) . This means that 1 measly megabyte could store 125000 boolean solo on/off changes, 62500 transpose changes or 31250 fader value changes for the undo stack. Of course I am oversimplifying, but only a little.
Things like adding or removing a vst will obviously take a little more space in RAM, since Cubase will also have to remember the action triggered and the values of every non-default knob of the plugin that was manipulated, but still nothing to be worried about. Of course all this doubles up, because if the application can undo, it also needs to be able to redo a change.
Real computational and memory heavy applications like the 3D apps out there (Maya, Softimage etc) can undo/redo literally millions of changes. Should this ever become an issue, they do provide an undo limit, meaning that the undo stack gets trimmed when the limit is reached, accommodating this way only the latest < limit changes. If this is indeed a concern, I am sure everybody would be more than happy to set the limit to say a value 100-200 undo steps. Then again, if you have 8GB of RAM you will simply not run out of it because of undo. Firefox for example uses way more RAM than Cubase would for the mixer undo, just to give you a rough idea.
Again, RAM is one aspect, but the undo definitely has nothing to do with actual performance in this case, as it’s not a process that needs to run or even do any work.
I hope this sheds a little light on the matter.
Edit:
My guess is that the reason Cubase is one of the last dinosaurs that does not provide full undo is because this would never be a strong selling point for potential new users, therefore not worth the trouble. They would go “What? They did not have undo until now? What else is missing?” or “Whoop de doo, every application can and should be able to undo, big deal.”
Either this, or they would literally have to rewrite Cubase because of this, which apparently they’re doing once a year anyway, just for the fun of it.
It’s been said that the 6.5 mixer had to go because it was so outdated. Well, the ONLY thing that was outdated about it was the lack of undo.
Does the new fluffy and bloated mixer have undo capabilities? Nope, but it sure is pretty (to some) and big.
+1 for this feature!! I just accidentally screwed up my mix because I was trying to scroll to a different channel. I really cannot believe this functionality cannot be turned off!!! PLEASE STEIN BERG ADD THIS!! Is there a better way to let them know how important a feature this is through some sort of official channel, or is this it?
This should be in the next update and I’m not talking about cubase 9.No need for the mouse to change values. It’s like walking on shatter glass when mixing