Mouse hover triggers unwanted action. Solved!

Virtual instruments Groove Agent
1

Inside Groove Agent, hovering mouse over “coarse” knob the knob automatically turns to value 12. It only happens with “coarse” knob.

How to recreate:

  • Open Groove Agent
  • Hover mouse cursor over coarse knob
  • The knob turns to value 12 only by hovering mouse over it with no buttons clicked.

I recorded a video of this bug:

Cubase 14.0.20 pro, win 10.
Mouse MX Master 3S.

2

Hi,

I cannot reproduce it here on my side.

What Groove Agent version do you have? Can you reproduce it with any Groove Agent instance, every library, and every project?

3

Also unable to repro on CP140.20.240 GA5.2.20.49 MacOS 15.4.1

4

Hi,

My Groove Agent version is 5.1.20.213
I tried to troubleshoot it and it happened with every project I opened or created.
It happens with every instance of Groove Agent and with every kit as long as the kit has a “coarse” knob. Only this knob is affected. I recall having this issue before but I didn´t bother diving into it, thinking it might be a temporary glitch.

I will try updating Groove Agent to latest version and let you know if it helps.

1 Like
5

I now updated to Groove Agent 5.2.220.49 but the issue is still there.
I switched my mouse to Logitech M330 and I disconnected all MIDI inputs on the Groove Agent channel but it didn´t help.

What is weird is that it happens about 50% of the times I hover over the knob.

Here is another closer look of the issue:

If you have any suggestions on how to troubleshoot further, please let me know.

6

First time viewing the video, and man, that’s some Ghost in the Machine action.

Have you mapped automation to that knob somewhere? If you create a completely blank project and load an empty GA session does it still happen?

7

Thanks Thor.Hog for the suggestions.

I tried creating a new and empty project, made an instrument track with GA as the instrument and then after loading a beat agent kit or dragging a sample onto a pad the problem is still there. There is no automation on the track.

I can also hear the coarse pitch changing together with the knob moving, so it´s not only a visual glitch.

8

I now opened a standalone Groove Agent app and there is no problem there.
So for me, the glitch only happens with Groove Agent inside Cubase.

9

I kind of wish it was happening to me! I mean, in a “curiosity of root cause attribution” way. It’s not cool, particularly since the action seems to destructively change the original parameter value of Course when you do it. If it just spun out to +12 and back again, that’s one thing, but it looked like it changed your value source of -3 to -5.

I’ll bow-out and let Martin continue working with you - the SB guys may know something we don’t.

10

Hi,

Do you have any Remote Device (MIDI Remote, Mackie Contor, Generic Remote, Quick Controls, …) involved by any chance?

1 Like
11

Solved!

Thanks Martin for the suggestion to look into MIDI Remote.
That was it. I had Arturia Keystation 61 set up as my MIDI Remote and when I removed it, the issue when away.

I will check into the Arturia remote controls and MIDImapping if I can pinpoint the exact cause. Thank you all. Such a supportive team here.

2 Likes
12

If you want to keep your MIDI Remote setup, you may want to check, if one of the controls for that hardware controller is set up as
“Value at Mouse Pointer”. If yes, just remove that (or change it to something else) and the rest of your MIDI Remote mapping should still work fine.

image
image1026×1076 85.2 KB

That is one of those weird (but sometimes useful) remote control possibilities in Cubase.

It allows a MIDI hardware control to be used to control a GUI item, that the mouse currently hovers over.

To the best of my recollection (someone please correct me, if/where I’m wrong):

  • First introduced around 2008 ago for the (discontinued in 2022) Steinberg/Yamaha CC121 Controller
  • The current MIDI Remote allows any hardware controller to emulate that feature via something called “Value at Mouse Pointer” (previously known as the “AI Knob” - but “AI” stood for “Advanced Integration” before it became the current abbreviation for machine learning related stuff.
  • I assume it’s available via the VST3 API, but not widely used by developers other than Steinberg.
2 Likes
13

You should mark this

as the solution.

2 Likes
14

Thanks Nico5. I found the control with the corresponding “Value at Mouse Pointer”, changed that action and now everything works like a charm.

1 Like