If I write something to move the mouse via a midi knob ( Maschine 3) it works fine if I only have 1 display active.
When I set the second monitor to be on via EXTENDED in windows, the mouse movement via the knob is very erratic. Instead of it moving 1 pixel at a time, it jumps from the first monitor to the second.
I had code that worked before from this group that I had modify to get it to work. I misplaced the file and I started over and started seeing issues.
I am slowly building up the file to debug. I am not using mouse position but simply adding 1 pixel onto mouse move.
I am simply doing this in the rules.
pp is the variable value coming in off the knob and I have checked it with log statements. (63 or 65)
rr=pp-64
This give me 1 or -1 for pixels for mouse movements.
If I go to 1 monitor it works as intended. When I enable the secondary monitor on my left side ( monitor 2) I get the erratic behavior. I am guessing this information helps. mouse_new.bmtp (1.8 KB)
This works for me on either monitor. I set up the preset so that it is only one input device and since we are not sending MIDI, we don’t need an output device.
So this is strange. Reversing cables going into the KVM seems to have resolved the issue. The Right and Left were setup correctly previously in that I could move the mouse from 1 monitor to the other.
No it doesn’t make sense to me either but I’m not expert on your KVM switch either. I just know that Bome MIDI Translator Pro works as advertised.
I have a theory though. HDMI interfaces communicate the display resolution of the attached display. Maybe your KVM switch was not reading the display resolution correctly of the problem display. I recommend you take a look at your KVM switch manual. I believe the same is true if you use Displaylink but not sure about VGA interfaces.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz