I tried the lastet demo version and it is still broken. I am waiting to renew my plugins until this has been fixed.
âJust a gentle bump!â
As it turns out, little while after posting my response I did end up experiencing some issues. Odd, as for me it seems to come and go, depending on the day.
Anyway, that was on my last system. I just upgraded recently. Well actually Apple ended up replacing my computer as it had power issues, so now Iâm on a Mac Studio M4 Max. I doubt it will change my experience though.
Try getting on to Tech Support and share your video with them.
1 Like
Yes please do so.
Iâve already reached out to them multiple times, but each time they responded that itâs up to Apple to resolve the issue.
Other times, I simply donât get any response at all.
Waves Marketing Claim:
Waves is the world-leading maker of audio plugins
So how is it that every other developer seems to know how to fix this, but the industry leader doesnât?
btw this also happens with the standalone instruments so it is NOT only Logic related.
Official answer :
The issue of the disappearing cursor is a bug on Appleâs side.
We reported it a while ago, and we are now waiting for Apple to address this.
In my limited experience with working with them it was very difficult, very allusive. Couldnât actually pin anything down. It may just be an Apple thing.
Even though you do say the apps donât haver the same issue, apps are also governed by a slightly different rule. Theyâre not hosted by another app which makes it like a window within a window, kind of. So Apple may have somehow left out a graphics update call when a mouse button up event happens outside of the plugin window, but still inside the main app, or something to that effect.
I donât know. Iâm just saying it is possible and would explain why it is a hard issue to pin down.
1 Like
Theyâre not hosted by another app
This also happens witan etc standalone instruments.
But the question still remains:
So how is it that every other developer seems to know how to fix this, but the industry leader doesnât?
Having studied programming before with in interest in plugin development, I can tall you that the architecture works a bit different between apps and plugins.
Standalone instruments are an app in their own right with a direct line of communication to the OS. While plugins are like an app within an app they have a means of communicating with the host and itâs the host that communicates to the OS, for the most part.
In the case of mouse pointer behaviour thatâs governed by the OS from memory. A plugin has to communicate via the host to relay any changes. If Apple missed something in the terms of plugin UI/mouse refresh itâs very possible that Logic and the OS arenât getting the message to update the mouse when it should.
Iâm not saying this is the case. Iâm just saying that from what Iâve learned in the past and from what Iâve observed with the behaviour and from what they told you itâs actually a plausible scenario.
Looking at it from another perspective. Itâs in Wavesâ best interest to fix these issues, theyâve fixed many others in the past. So if theyâve said theyâve looked into it and discovered that they canât fix it from their end that would also come across as a very plausible scenario.
So when we put these two plausible scenarios together we get something more concrete, we get a very likely scenario. Except that doesnât help us now.
My suggestion would be to report your problems to Apple and I should probably do the same. Make sure the bases are covered.
1 Like
and yet it is still broken since years
this is not MY problem 
It it Wavesâ problem which they canât sort out.
yes please!
âJust a gentle bump!â
Still broken with version 16
âJust a gentle bump!â
Just another gentle bump!
Still the same odd behaviour under macOS 26 Tahoe
Just another gentle bump!