I’ve just booted up Cubase 12 and the double-click works perfectly with the Magic Mouse
…then moved on to Cubase 13 and that’s where the fun and games starts!
Yeah I mentioned V13 being the start of the problems in one of my first post above. Maybe its to do with the move to silicon.
OK so I did some testing after what @MarkDaw found out.
The problem is with the Apple Magic Mouse as he says. A wired USB Apple Mouse works perfectly. And my Intel Mac laptop with a trackpad works perfectly as well.
It is boxes that require a single click to highlight the text that mostly fail - ones that use a double click are all OK (why do we have this weird behaviour - shouldn’t they all be the same???)
Cubase 12 is where we start getting problems - for me it is just the tempo box in the transport panel that fails.
After C12 it all starts going wrong -
The faders get a smaller value box and now require a single click rather than a double click - so these now fail.
In the Inspector panel, volume, pan, track delay, midi modifiers etc all fail.
There are some exceptions though - the time signature box in the transport is single click and still works, as do the LR markers and loop locators in that panel.
All double click text boxes are all good as well - anything to do with EQ for example.
Post C12 is also where we start to see problems with Snap Type, Grid Type and Quantise Presets - they are a bit laggy.
When you are working quickly you select say "Events’ as the Snap Type, but as you move your mouse away on to your next task, that selection is slow to stick and ends up choosing something else such as ‘Grid + Cursor’ instead.
Only Cubase has this problem with the Magic Mouse - no other software I use has issues.
All pass this on to support but it would be interesting to see how many others have these problems.
To continue this.. has anyone found an alternative to the Apple Magic Mouse? I’ve looked at a few options this morning online but they all seem to be clunky ones with a physical scroll wheel.. I’d be happy to buy a generic non-Apple one if it had the same functionality, it would be worth it to get rid of this issue
Well, the question is why other software works with it ![]()
Including Wavelab and Dorico and Spectralayers…
I don’t buy this as an excuse.
I used a bluetooth Magic Mouse with Cubase prior to C12 with no problems whatsoever.
All the problems have stemmed from changed text boxes and fonts. And Silicon?
I absolutely agree with everything said so far. What is compounding this for me is that the Warp tool doesn’t work properly in Cubase 16 either. I’m having to abandon 16 altogether; I wish there was some way I could get a refund as it’s been a complete waste of money
You can request a refund here within 14 days after the purchase.
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.
I think this makes the point
You’re right - this definitely isn’t hardware related, and I’m not suggesting it is. These problems have all developed post C12 and have gotten more prevalent as more changes have appeared in the UI.
Regarding your tests - I see exactly this behaviour.
However, my biggest issue is with not being able to highlight text boxes. The ones that are a problem are single click boxes - most double click boxes work fine. And MarkDaw spotted that the text box issue only happens with Apples bluetooth Magic Mouse and NOT with a wired USB one. No one has yet posted about other brands (and I only have various Apple ones to try) but I’m guessing the issue is bluetooth based not brand based.
It is totally frustrating not being able to enter a tempo, a fixed fader level or a track delay time, as these don’t work that well via click dragging.
I do wonder if due to the cross platform nature of Cubendo and its age, it may not be using Apples mouse API’s as it should - same way as it doesn’t use the window scrolling? There used to be a double click speed control in OSX, that’s now gone…
That’s exactly the issue I’m experiencing. Again, the Cubase UI lacks universal movement/time thresholds which means normal clicks are accidently registered as click-and-drags if the cursor has unintentionally moved between press and release (which is more likely to happen with sensitive cursors). If a click-and-drag is registered instead of normal click, input boxes will not be highlighted.
Technically, the issue is hardware and system dependent because it depends on cursor sensitivity (which depends on hardware and settings). Personally I began experiencing it a lot more often when I increased my mouse sensitivity. However, it doesn’t mean that the hardware or system itself is causing the issue, which is what you and MarkDaw seem to be assuming.
It is possible that the magic mouse has Bluetooth issues and Cubase doesn’t register regular clicks even when the cursor isn’t moving at all (which is what Steinberg support is assuming). But you haven’t actually provided good evidence for that. To the contrary, you’ve confirmed that it only occurs with single click boxes (you would expect a Bluetooth issue to affect the entire UI).
You need to clarify what you mean when you say the issue disappears with the wired mouse, do you mean:
- Clicking works as expected. This doesn’t help because it could be that the magic mouse is more sensitive than your wired mouse (sensitivity doesn’t just depend on the sensitivity setting but the actual hardware and connection).
- Clicking with the magic mouse doesn’t work even when the cursor isn’t moving at all. For that, you need to do a proper test and make sure that the pointer isn’t moving by a single pixel in between press and release. Nobody so far has confirmed this, every video posted shows the cursor moving all over the place.
- Clicking with the wired mouse works as expected and Cubase doesn’t register a click-and-drag on single click boxes even when the pointer has moved between press and release.
This is the reason why every professional software I’ve ever used (except Cubase) features movement/time thresholds. It’s not just because it’s a very frustrating issue, it also makes it much harder for both users and customer support to figure out if clicking issues are only caused by Cubase, or compounded by issues with user hardware, OS, bluetooth, etc. It’s a complete mystery to me why Steinberg thinks this is acceptable UI design.
Earthling -
No one has said that there are hardware or system issues! MarkDaws customer service response says that Steinberg devs have suggested it may be the case, but as we’re all well aware, that’s a very unlikely scenario with the millions of Apple users using its mouse elsewhere without issue…!
The insinuation from me is more along the lines of Steinberg is probably not using standard Apple programming (as we see in window zoom / scroll bars etc) and this is more likely the root of it.
Clarification -
The only thing that a wired mouse improves is text highlighting. All text boxes can be highlighted perfectly every time, whereas the bluetooth one is rubbish.
Click dragging sends is no better with a wired mouse, but it does seem to be a bit better with dropdown selections such a Grid Type.
The which, what and wherefore’s of this are all way above my pay grade - I’m a customer and I just want it fixed.
