Hi, I’ve been using Cubase regularly for about 20 years. I’ve noticed since Cubase Pro 13 that when I try to double-click on a dB or pan value in the inspector or a dB value in the mixer to set a specific value, the double-click is not reliable. Sometimes I double-click and it works, other times I have to double-click several times until it catches and other times it works with just one click. It’s so annoying and I don’t want to move the slider while I’m mixing and prefer to go to a specific value. This has been broken for me since Cubase Pro 13 :o(
Imagine you’re sitting with a client and you’re going to mix a song, and you can’t enter a dB value… doesn’t feel very professional :o(
I read online that others have the same problem… so pleas its about time you fixed this problem, before you upgrade to cubase 15 :o(
And the same with the “Steinberg Download Assistant” the program don’t open, I have being in contact with the support and the guy say that I have to remove my antivirus program and he say its the only solution !!! but I told him that “Steinberg Download Assistant” worked fine before Cubase 14 pro
Definitely agree with you here - I’m on Mac silicon and I wondered if thats the issue?
Some boxes such as tempo in the transport bar only let me click type a value once - then I have to use the up/down buttons as it won’t let me type in it again!
Actually Benny mentions anti-virus so he’s on windows…
I’ve got 10 years more daily Cubase use on Benny - I know somethings wrong. This along with the lag on drop down box section which also appeared V13 onwards, is making daily use extremely frustrating.
Sorry to hear you guys are having issues. Using Cubase since 12 and Nuendo since 13, and now on Cubendo 14.0.32 on MacOS 15.5 on both my Studio M3 Ultra and MBP M3 Max, upgrading all along the way, and I’ve not had any issues.
There was this one time where one of the versions did indeed have a crash with a particular way a location was entered in but that’s long since fixed.
That’s the only issue I’ve verified in regard to any clicking, double-clicking, or entering in direct dB values or tempo values. Sometimes I don’t feel like turning my chair around to the other workstation and just work via Screen Sharing (which is amazing on Apple Silicon I must say) and even then I don’t have any issues.
I should note I’m fully native mode here and no Rosetta at all other than the SDA which still requires Rosetta to launch.
Happy to test anything you may want if there’s a reproducible issue you’ve got.
Windows 10/11 here and I haven’t experienced inconsistencies like that - not in C13 nor C14. Could you try to make notes next time this happens - maybe it’s happening in a specific project, track, after doing xy, etc ?
Same here on Cubase 14.0.32 (Win 11 Pro). In my case it happens if the mouse is moving while clicking (see video).
The click and release cursor positions need to be identical or Cubase registers a click-and-drag instead of a click. I tried setting the ‘Value Box/Time Control Mode’ mode to ‘Text input on Left-Click’ instead of ‘Increment/Decrement on Left Click and Drag’ but this preference only affects info line value boxes for some reason.
Making this preference affect all value boxes would solve the issue but we wouldn’t be able to click-and-drag anymore. Ideally, having Cubase register a regular click even if the mouse is released a few pixels near the click position would solve the issue without having to use ‘Text input on Left-Click’ so we would still be able to click-and-drag as well.
I’ve experienced the same issue, and many similar issues regarding certain small functions sometimes working and sometimes not, and just things working unreliably in general. I really love Nuendo 14, and have been using it as my main composing DAW for a few months now, but I do have to say my #1 problem with it is its unreliability and unpredictability.
I’ve used at least 4 different mice. The issue I described is obviously not a hardware issue, nor is it random. It happens every time the click and release mouse cursor positions are different. You can replicate it easily by clicking, holding down the mouse, moving the mouse a little and releasing it like I did in the video.
Users with higher mouse sensitivities like myself should experience it more than others because the likelihood that the cursor will be moving while clicking is greater if the sensitivity is high.
I think you’re experiencing a different issue than the OP. That said, what you show in your video is does not happen on MacOS 15.5, Cubendo 14.0.32. Once the parameter value is clicked on, I can move (drag) my mouse wherever I want and it still changes the value. I’m using a trackpad.
I’m experiencing click and double clicking not working reliably which seems like the same issue to me, maybe you meant different cause. Any issue can have multiple causes, this is the only one I was able to clearly identify and reproduce. I didn’t realize until recently that accidently moving the mouse was causing it because the tiniest movement will be registered as a click-and-drag. The only way for others to know is by doing the same test.
If the mouse sensitivity is high enough, just a light click pressure is enough to move the cursor sometimes, so it can happen even when I try my best not to move the mouse. I have to lower the cursor sensitivity to unusable levels to solve the problem entirely.
guys, any info on sorting this bug? this comes up every few projects mid work so I’m forced to start clean and migrate the tracks into fresh project to avoid it, having to put up with this is REALLY annoying. in my case the double click just stops working all of a sudden, it works if you do it 3 times in a row, and it affects every plugin and function in the project, I can’t add eq bands in Pro Q, can’t enter the midi/audio events on the grid. literally have to double click 3-4 times to get what I want which is irritating to say the least. my issue is exactly like OP and I’m on Windows 11. the issue is not linked to a cursor position like someone above stated
it’s happening to me too on cubase 14 and cubase 15, it usually takes like 3 to 6 double click to open a midi track in the inspector or to change a name of a track, it’s really problematic and slow down the workflow a lot…