Mouse input lag on 2019 Mac Pro

I've been trying to get to the root of an issue with a 3 month old 2019 Mac Pro (16 core, 192GB RAM) that's being used solely for Logic & Pro Tools.


Initially projects run fine but once I'm a few hours into a project (saving versions of the file to keep the file size small) I start to get significant mouse lag of around 1 to 1.5 seconds, making adding automation points feel like working in treacle. These are even on projects that are using 5 acoustic instruments in Kontakt so nothing should be causing these issues.


I checked on the Mac Pro forum and nothing from an Etre report revealed anything in the background that could be causing the mouse input to slow (this is also noticeable when using cmd space to launch Spotlight).


The suggestion that came back was that it was probably 3rd party plugins causing the issue, however most of the ones running are on UAD cards and I try to keep plugins to a minimum, plus I wouldn't think plugins would be causing a mouse input lag on Spotlight or in Finder?


Any suggestions are greatly welcomed

Mac Pro (2019)

Posted on Apr 18, 2023 7:02 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 21, 2023 5:50 AM

Ok, this is a bit weird. Usually, I have the Mixer as a separate window open just behind the Arrange so I flick back and forth so if I change track/channel in the Arrange then it will also change to that track/channel in the Mixer.


If I minimise the Mixer window, the amount of mouse click/keyboard input lag suddenly greatly decreased. The window can't be completely hidden behind the Arrange that makes no difference. But minimised in the dock no problem.


I'll try this on a heavier project and/or revert to using the one in the Arrange (it's always felt a bit cramped to me which is why I use the Mixer window) to see if I get the same performance change. What could be causing the mixer to require all that additional processing? Occasionally I get pink bars on one or both of the monitors when I reboot or wake the screens up (they're LG so switch off after 5 mins). Could this be a GPU issue?

Similar questions

11 replies
Question marked as Top-ranking reply

Apr 21, 2023 5:50 AM in response to yoyoBen

Ok, this is a bit weird. Usually, I have the Mixer as a separate window open just behind the Arrange so I flick back and forth so if I change track/channel in the Arrange then it will also change to that track/channel in the Mixer.


If I minimise the Mixer window, the amount of mouse click/keyboard input lag suddenly greatly decreased. The window can't be completely hidden behind the Arrange that makes no difference. But minimised in the dock no problem.


I'll try this on a heavier project and/or revert to using the one in the Arrange (it's always felt a bit cramped to me which is why I use the Mixer window) to see if I get the same performance change. What could be causing the mixer to require all that additional processing? Occasionally I get pink bars on one or both of the monitors when I reboot or wake the screens up (they're LG so switch off after 5 mins). Could this be a GPU issue?

Apr 23, 2023 4:41 AM in response to Pancenter

So with the separate Mixer window no longer open, performance has noticeably improved. I hadn't experienced that level of a cpu hit in Logic 10.5.7 (on the 2012 MP) so I'm curious as to why the Mixer window in 10.7.7 would be gobbling up all those cycles? Surely there are users who have the mixer window on a separate screen? I even noticed the lag with the mixer on a second display without Pro Tools open.


I'll keep an eye on larger projects and see if editing audio (trimming the start of audio files, adding region automation for dB volume, CC Modulation etc) brings it to it's knees again.

Apr 19, 2023 10:59 AM in response to Ben Collier

"Initially projects run fine but once I'm a few hours into a project"

Just guessing, seems like a buffering issue(?)

How many undos have you set? Does it change after deleting the Undo History?

I'm working with 100 without any issue.


"saving versions of the file to keep the file size small"

What you mean by that? However, I never save the project as package but as folder. I have set auto-backup to 30 versions without any issue.


Did you already reset the PRAM ?

What is activity monitor showing (CPU, RAM, Network) when lagging?

Apr 21, 2023 10:34 AM in response to Ben Collier

Ben Collier wrote:

(...) I saw reports that it was better to leave it on and just Lock Screen when not being used.

I doubt that it's better to leave it on. I'ts more convienient, though. Do you have a source for this claim?

Is a daily reboot preferable to refresh/reset the memory?

Yes, some things will reset by a "real" shut down. More things will reset by deleting PRAM.

Apr 20, 2023 7:04 AM in response to Ben Collier

Both the Apple wireless mouse and a Kensington usb trackball, this is also affecting keyboard input as well such as creating a duplicate track (ie two tracks but the same channel, mute one and both become muted)


As the system is racked I have a USB extension for the usb, however I also tried this via a OWC Thunderbolt dock and the same issue persisted making me think this was either a Logic issue, or an OS issue as this laggyness is also sometimes seen in Finder when Logic is open

Apr 20, 2023 6:57 AM in response to yoyoBen

  • I have a habit of deleting undo history before saving and after large tasks I don't need to undo like deleting a load of unused instruments, Undo set to 100 as well


  • I save as a folder as well, never used packages so selecting Save As... and saving it Project v1.1, then Project v1.2 all within the same folder which also makes client recall easier. I've noticed that doing this can reduce a 100mb session down to around 40mb even when deleting undo history between saves
  • When I had activity monitor up the only things that are jumping up are Logic and ProTools but not by much.


I do use Summing aux stacks which have aux channels within them, have these been known to cause performance issues?


I'll give the PRAM reset a go, on my old system I would reboot every morning but this system I saw reports that it was better to leave it on and just Lock Screen when not being used. Is a daily reboot preferable to refresh/reset the memory?

Apr 22, 2023 4:07 AM in response to Pancenter

It's a stock 8GB card as I assumed that that would be more than capable especially as I'm not running at native 4K on these displays. I could try running the Apple Hardware Test to see if that picks anything up.


To confirm, both LPX windows are on the main display with PT's video using the second display. I'll try avoiding the Mixer window for now and see if there's much improvement when adding Midi CC/automation in a region.


So there shouldn't be any routing/processor/performance issues or glitches if you set up multiple summing stacks with 4-8 auxes (ie sub groups & fx channels outputting to the summing stack) inside them?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mouse input lag on 2019 Mac Pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.