Bad mouse response AND MOUSE FIX

#8

ok, just updated java, still having the issue..

#9

sorry, my bad... apparently we are bundling the JRE in the patcher, so the general java update is not going to affect which JRE we use. (see this thread)... you could try to update the JRE as described in that thread.

#10

Ott, are you also using a wireless mouse?
I'm thinking this might also interupt..

#11

Nope, it's a wired mouse.

#12

just had a bit more closer inspection of the touchscreen response and it looks like it's not following the position given by the touchscreen, but adding the difference between "first touch position" and the "current touch position" to the position of the knob. So when I'm in the middle, it more or less hoovers around the same value, but if I go up or down just a tiny bit, the knob "slowly" goes up to max or down to minimum respectively...

#13

1st post (hello everyone)

Having the same issue as SirSickSik. Brand new Axoloti (Merry Christmas), fresh install of both Axoloti (+runtime) and a fresh installation of Java, so we can probably assume these are all on the latest release.

Running Windows 10 on the latest update. Machine is a Lenovo Yoga 2 (touchscreen). I've tried with the touchscreen drivers disabled in device manager, but there's no difference. Likewise I've tried after restarts, in case there some latent processes floating around.

To reiterate the problem: Click and hold on any of the dials causes it to oscillate back and forth between max/min values. Trying to track (find) the mouse cursor during this process, it seems to have moved to the side of the screen.

#14

This is still happening to me.
Windows 10
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)
Axoloti build 1.0.12-0-g80370d2
ThinkPad T470p with built-in Synaptics touch pad

#15

Just bought myself a new mouse as the other one sucked anyways, but still the problem persists.
This time it ain't a bluetooth mouse, just a "good old" wired USB mouse of €40,- , so I'm pretty sure now it ain't the mouse's problem but probably the touchscreen interfering somehow.
@johannes do you have any idea what this could be and how to fix this? As at the moment I can't change any knob without creating noise...

#16

oh, I missed the remark of technobear.. gonna try to update the JRE now..

#17

Thanks to @bigpig I found the solution to the (my) mouse-problem. The touch-screen still ain't usable though...
Follow these instructions and it should(/might) work:

  1. Ensure latest Java runtime is installed on your machine
  2. Rename "C:\Program Files (x86)\Axoloti\runtime" to "C:\Program Files (x86)\Axoloti\runtime.backup"
  3. Copy the folder "C:\Program Files (x86)\Java\jre1.8.0_151" to "C:\Program Files (x86)\Axoloti\"
  4. Rename "C:\Program Files (x86)\Axoloti\jre1.8.0_151" to "C:\Program Files (x86)\Axoloti\runtime"
#18

Tried this fix, but no joy.

Has it worked for anyone else?

#19

technobear had a couple of replies over here, which, together, made me be able to tackle this problem. Have you tried all his replies? It might be that one of things before my last edit is also needed to fix this problem.. Perhaps the java-install? At my computer this one was not up-to-date when I first tried to fix this problem...
Just start from the first comment and work your way down.. if it still doesn't work... I guess there's still something to work out...

#20

Hi SSS, thanks for the help. Much appreciated (also, thanks for the great objects)

When you say "a couple of replies over here" you're referring to this thread I presume? Unfortunately I've done everything in there to no success. My Java version is up-to-date (in fact, I've avoided it on this laptop until I installed Axoloti on Xmas day). Likewise Windows 10 is up-to-date.

It's not a serious problem for me as my Axoloti will spend the majority of its time hardwired to my main studio rig. In fact, it might be useful for me to keep this laptop's Axoloti version in a broken state to I can test if new Axoloti releases fix the problem (?)

#21

ah, sorry to hear this still didn't work for you. I myself was getting quite frustrated by the noise made by the controls when clicked..
Luckily this only is a mouse-problem, not an overall control problem eg midi :wink:

#22

I'm having the same problem ever since I've upgraded my display to bigger than full HD (> 1920*1080).
If I put my display back to full HD, it works as normal.
Windows 10, on different machines, different GPU's and all.
All up to date.

#23

ah, that might be helpful too, I got to notice that there's still some weird behavior every now and then..

#24

I'm seeing the same thing as @mtyas, the jitter occurs only at resolutions higher than 1920x1080. Additionally, the higher the resolution, the greater the effect of the jitter.

Note: This is after updating JRE to the latest (version 161) and copying the JRE to the Axoloti folder as described by @SirSickSik above.

#25

Just to add my voice to the confirmations that this problem only occurs at resolutions greater than 1920x1080.

#26

did a test with windows, everything over 1600 horizontal resolution , the issue appears to start.
however, on mac higher resolutions (2880 horz) are perfectly ok.
so appears to be a java/windows specific issue, rather than an Axoloti code issue.

(note: this is a 'developer' note, I'm not saying its not something Axoloti doesn't need to deal with )

a quick test on the current development branch (experimental) seems to show both swing and piccolo views still have the same issue.

( i didn't compile the full image, so didn't have the rescaling - but the native resolutions still exhibits same issue with dials)

#27

Same issue here.
Touchscreen laptop, Win 10, latest Java, wired mouse, resolution 2560x1440.

Knobs don't oscillate between extreme values but quite randomly (with a hint of also trying to follow the correct values).
Tried the OP's solution with no luck.