Open mboltonnet opened 2 years ago
I have an MX master mouse myself and I actually run into this issue as well. I think it happens because the logitech options control panel interferes with how middle click is sent to windows. The new implementation used to fix this issue, but with the newer versions of the control panel even my workaround doesn’t work.
It may be happening because the logitech control panel invokes a different application for a short period of time, which causes LES to disable all its functionality. This behavior is necessary to prevent keys from getting stuck.
It used to be that one syntax for the macro would work on mx master mice, while the other would not. Now you can end up in a situation where neither hotkey syntax works.
Right now I personally just uninstall the control panel. The mouse stores the sensitivity settings you change somehow. This is obviously not a good solution, but I don’t really know a way around this problem for the time being until logitech improves their implementation of macros, or until autohotkey releases an update to their language that allows you to ignore its interference.
It anyone knows more than me, help would be appreciated.
@Inversil, thanks a lot for the tip. After I've settled on a control scheme and I don't need the Logitech Options panel anymore, I'll try uninstalling it and see if that works until LES is updated. Really appreciate you taking the time to comment.
Can confirm the bug (it actually took me months to realise how this should work in the first place) with another Logitech mouse (M720). I though that was the way it is destined to work, and was already disappointed, until I realised Options is getting in the way here. Too bad, the Ctrl + Alt + mouse drag replacement would be so good here! Since I use Options to configure my keyboard I can't sadly just uninstall Options for this feature to work. Drats!
I have tried using X-Mouse Button Control, which in that software I am able to recreate the middle click to pan feature while having the Logitech Options software installed. Unfortunately though, this only works when LES is not running because for some reason even if I disable the middleclickpan setting in LES settings if LES is running it makes middle click basically not work when I am using Ableton.
So if anyone is only interested in the middle click to pan feature of LES it can be recreated with X-Mouse Button Control and not use LES at all
I took a quick look at X-Mouse, it seems that it integrates on a driver level, which would indeed bypass logitech options's interference.. unfortunately this is not really a practical solution considering everything else in the project uses AHK.
If you want to make them play nice together, you could try make a custom build and take out references to "Mbutton"
I looked a bit into that but I am absolutely useless with coding anything so I wouldn't know how to do that. I don't even know how to open the code to tinker with it and compile it again
Uninstalled Logitech Options, and it started working without even restarting! Thanks, this thread is awesome. Super detailed issue description (kudos to the 20ms cue for maximizing diagnostic confidence), and the workaround is immediately obvious.
Since commenting I have made an LES version with the middle click to pan feature removed and a used X-mouse for that function that seems to work. This way you can have the Logitech app so you can customize the button functions .I have also made a secondary ahk script that replaces the regular save shortcut with the collect all and save function and regular save is now alt + s. Also really cool addition
Describe the bug Pan only works for ~20ms Middle Mouse is pressed down. LES ignores the Middle Mouse being held down.
To Reproduce Steps to reproduce the behavior:
Expected behavior The cursor should turn to the "Grab" cursor, and the Arrangement view should pan according to the mouse movement as long as Middle Mouse is held down.
Screenshots Gif: https://imgur.com/lknPZKP
Desktop (please complete the following information):
Additional context I noticed that this (or a similar) issue was addressed in LES v1.3, so I double-checked that I've updated to v1.3.3. Any ideas? THANK YOU, by the way, for making the single most powerful Ableton Live add-on out there. Amazing work.