General debugging if sth does not work?

I have the issue that as soon as I am opening LogicPro (App) on macOS I get a delay on my trackpad if I press and draw e.g. a selection of audio files. It is reproducable and I have this since 6 months or so, in between there were several BTT updates and macOS updates I did - no change.

My steps which are not complete

  1. deactivate BTT while Logic is running = fix the problem
  2. deactivate all shortcuts for keys for trackpad for whatever (floating window) = no changes. The issue persists.
  3. right click on LogicPro in BTT and selecting “Due as you would be active” → I would expect to have the delay selecting folders or documents on my desktop = no changes, no delay.
  4. selecting on the right side bar: “deactivate Better Touch Tool completely” = works, delay is gone.

How should I proceed from here?

unfortunately it is basically impossible to debug because the issue is most likely happening inside Apple's Accessibility support code in Logic Pro.
This means only Apple could really debug it.

However you can try to disable as much Accessibility API functionality as possible for Logic Pro - most importantly disable window snapping for Logic Pro and any conditions you have that rely on the focusd or hovered UI element

Hi, your answer is too complicated for me :smiley: But at least you gave me a point: I tried once the AX window behavior (I am using wrong terms, sorry). Maybe that could cause the issue.

Bad news: I deleted many stuff I do not need, I do not use or which was de-activated to be used as a template for later.

But neither I could fix my mouse problem nor did this go a better way: using since some days an external Apple keyboard, I have a lag when typing as long as BTT is running.

So it is the mouse and it is the keyboard which gets slowed down by BTT? :grimacing:

You could try to create an empty preset (and disable your current one), then restart BTT to see whether the issue goes away immediately. (if not this would rule out it is something configured in BTT)

Unfortunately such issues are almost always not caused by BTT directly but by some other app that conflicts (although there are things in BTT that could also cause this because BTT basically allows you to configure/program anything)

The problem is if a mouse or keyboard event happens, BTT needs to catch it, analyze it and then give it back to the system. Usually this is very fast and not noticeable (even on slow machines). However if something else on your system is slowing down the process of analyzing the event it can become noticeable. Unfortunately there is no real way to determine what is slowing down the process apart from trial and error. Looking at activity monitor to see any unusal CPU spikes can also help.

Which version of macOS are you currently on?