Isolation:
-
Logic / GarageBand AU: dead cells reproduce.
-
REAPER (its own AU host), standalone, VST3/CLAP/LV2 in other hosts: all cells work. Same plugin binary, same machine, same OS.
Instrumentation: I added a MouseListener on the editor (with wantsEventsForAllNestedChildComponents=true) plus a direct mouseDown log inside the affected child. The user clicked extensively across the dead zone and a working cell adjacent to it. The working cell produces both log entries. Every click in the dead cells produces no log entry of any kind — events never reach JUCE.
What’s different from the existing reports (viennal, moving-window, glitchy-resize, iPlug2): those describe contiguous regions that scale with UI scale. This is a small fixed region at a specific position. Suggests AUHostingService may have a clipping rect or hit-test region with wrong geometry, in addition to (or instead of) the coordinate-transform issue others have hit.
Filed with Apple: FB22477732. If you’ve filed Feedback Assistant reports on related Tahoe AU mouse issues, please reference this FB and reply with yours so we can cross-link.
Questions:
-
Anyone else seeing geometrically-localized drops at specific positions, rather than scaled bands?
-
Any known JUCE-side workaround?
Plugin: KR-106 (JUCE-based, AU/AUv3/VST3/CLAP/LV2/Standalone). OS: macOS 26.4 / 26.4.1.
@reuk — flagging in case the specific-cell pattern is useful additional signal.