Nope, I have the problem and I’m on my Mac with no Logitech in sight. Only started happening after release 1.x, never before. I suspect probably because one of the updated dependencies.
Same issue here, knobs randomly jump from 0-10 on the first click/hold and I’m getting sick of huge unwanted filter sweeps when performing. It’s ruining my workflow. Windows 10. Logitech Master MX mouse.
Has no one reproduced and solved this yet?
I experience sometimes the same behaviour, not in a particular module
no logitech mouse, but a razor one with high DPI settings.
maybe i can try using it with lower DPI during a few days to see if it happens less or equal
Same, I get the occasional jumping but it’s not always super obvious when it’s happening. Here’s my best attempt at explaining what’s happening:
- You’re adjusting a knob or a fader
- Let’s say the parameter is a knob and it’s currently set to ~7 o’clock
- You position your mouse over the parameter - near center, or say top right
- You click and drag in an upwards motion to move the parameter
- If it doesn’t happen at first, try it a few times in quick succession - operate the mouse a little sloppily (think Keith Richards in the 70’s)
Result: the parameter will sometimes seem to “jump” to catch up with your mouse cursor location. So instead of going smoothly from 7 o’clock and continuing to increase as you drag upwards, the parameter seems to want to jump to the value closest to the mouse x/y coordinates. So if your mouse cursor is near the 1 o’clock position as you begin the click and drag process, sometimes the mouse cursor will jump from 7 o’clock straight to 1 o’clock.
It seems least likely to occur when I position the mouse cursor near the location of the current value and drag up slowly. But if I’m clicking near the top of a knob or fader, that seems to do it.
When this happens with a mixer knob or fader (I use Console 8 in my default template and have had it happen there a few times) it can scare the beejeezus out of you when you’ve got your speakers up loud and suddenly the quiet background part jumps to near full-blast.
And I can reproduce it pretty consistently here if I’m trying. If I’m being careful and deliberate with my mouse movements it may not happen at all, but if I’m being sloppy and quick, I can get it to jump pretty regularly.
In case any of this matters: I’m using an Anker vertical/optical mouse connected via USB to a Windows 10 PC with an AMD graphics card. My guess is there’s something in the code that’s making the knobs want to catch up to the current mouse location.
1 Like
No
If you mean a carefully constructed and reproducable test case, then I think no. It’s pretty random. Happens on my Mac as well. The only thing that’s certain I believe, is that it started only in Rack v1
Thanks very much, guys!
That will be very welcome, cause this knob jumping can cause hearing damage and/or blown up speakers.
There’s a VST plugin called Ice9 that will immediately mute the audio of it crosses a defined threshold. I use an instance of HostFX with Ice9 just before my audio output as part of my template. Highly recommended.
1 Like
Wohooo! That’s great news guys! Fix coming out in an upcoming minor release of Rack or…? EDIT: Yeah, I see the fix is due to come out in 1.1.4, wonderful! Thanks for your work Ben!
Thanks for the tips! But I already have limiting protection in the hardware.
I’m more interested right now in this problem getting a proper fix, this problem didn’t exist in VCV prior to V1.x
So it is good to hear that there will be a workaround.
I’m out of the loop a touch bc of health problems, what was the workaround?
Also, a decade ago, before there was a utility to map Logitech mouse buttons on Linux, I remember cobbling together some script or another to do this for me, and in the process I remember a utility which displayed the raw mouse values in the terminal, as they arrived at the computer.
For the life of me I can’t recall what the utility was called, or if there was a windows equivalent, but I wonder if attempting to log this kind of info when we experience the issue would be helpful in narrowing down the root cause?
Oh, another question @ all Logi users: Wired or Wireless mouse? I wonder if it’s something with the Unifying/G-Series wireless interfaces?
It will be included in the next release of Rack. For details please take a look at the GitHub-issue.
1 Like
Since no one else has linked it in this thread…
3 Likes
Issue seems resolved in the next update, so closing.
1 Like