Bad mouse response AND MOUSE FIX

#1

Since a couple of weeks the knobs in the patcher respond weird to my mouse and touchscreen. Whenever I hold down the mouse, the control starts to wiggle back and forth in whole steps. I just found out that with the touchscreen it's even worse and there it jumps from 0 to 64 all of the time..

I checked some other programs and there the mouse seems to behave well.
Are there more people experiencing this behavior or might I just need to reinstall the patcher again?

Thanks to @bigpig I found the solution to the mouse-problem. The touch-screen still ain't usable though...
Follow these instructions and it should 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"
#2

If you have not updated Axoloti recently then it can’t be the patcher software, it’s more likely either an updated windows driver, or other software (java) that’s been installed, or a hardware issue.
(software update is most likely)

All software works a bit different, so could be something that affects only some software.

What version windows and java are you running?

it’s ok on my win 10 touchscreen laptop , which has the latest windows and java updates - so I’d guess updating to latest stuff is a possible solution?!

#3

I'm using the same windows and java.. I've had a major windows 10 update just a couple of days ago. (though. perhaps it skipped updating java afterwards..)

#4

Hey Remco, just wanted to say that whenever I come across bad mouse response, I find it helps to tease them with a bit of cheese. I find extra strong mature cheddar often does the trick, but as you're in the Netherlands maybe your mice would prefer Edam instead!

Sorry, couldn't resist, just helping-out cause I have a request for your contribution thread soon :stuck_out_tongue_winking_eye:

#5

hard to say really, unless we can get a group of people that have the same problem, and then can find some common factor.
( or a developer gets it, in which case they then can debug it directly)

if your on the latest windows release, perhaps check in the java control panel and see if there is an update for you.
It might be the ‘old’ version of java your using doesn’t play nice with the windows update - that is not uncommon unfortunately.

seems odd it affects both mouse and touch, I guess as different hardware, could be java.

#6

ghehe, whoops, guess what.. first thing showing up when starting lava.. "update available".. hmmm, what would it be... XD

#7

I have this too!
Windows 10
Java 8 update 144
Axoloti build 1.0.12-0-g80370d2
I'm using a ThinkPad laptop, with a SteelSeries Sensei mouse OR with the built-in synaptics touchpad.

#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 (?)