Mouse behavior under macOS Logic Pro

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 :slight_smile: 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!

Another Year another change to catch up :slight_smile:

Hi @anon77818099,

As mentioned, 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.

Please respect the Forum Community Guidelines!