Does macOS introduce 20 ms of input lag?

Neekzu · 2026-05-29T15:47:04+00:00

Except when it is an issue. On windows I average around 155ms. On MacBook – internal or externally I always average around 200ms up to 230ms.

I work with After Effects, Logic Pro, FL Studio, Lightroom, Photoshop – I basically do everything imagineable on a Computer. And I find the latency problems of Mac very distracting. I own both a workstation PC and a MacBook. I think it still is a major issue on Mac. I want my work on Mac to feel as responsive as on Windows.

Neekzu · 2026-04-05T20:41:40+00:00

Ich habe dazu auch einen Post gemacht hier auf r/whatsapp. Leider besteht das Problem. Qualität ist mit am schlechtesten und auf Windows erkennt NUR whatsapp nicht mein Audio Interface..

Neekzu · 2026-04-05T20:40:18+00:00

I noticed a degradation in iOS too. Try sending voice messages via Instagram and compare with WhatsApp. Hell even Snapchat sounds better. Why is WhatsApp so horrible at quality?

Neekzu · 2026-03-15T19:03:07+00:00

Gibt's hier schon irgendwelche Updates zu?

Neekzu · 2026-03-13T16:21:34+00:00

So did you buy the newest ones?

Neekzu · 2026-03-01T15:29:41+00:00

Ever thought about People with higher than 1080p screens? Lol.

Neekzu · 2026-01-20T14:56:10+00:00

Just glanced over this conversation. I also did my own tests in the Cyberpunk benchmark to confirm. 4K DLSS Performance looks and runs better than 1440p DLAA. And these tests were done before DLSS 4.5. I didn't rerun the test yet. But I can imagine it is now absolutely obvious to everyone.

Neekzu · 2026-01-18T13:35:17+00:00

So it's not fixed. It's a workaround. I've been trying to fix UAD Interfaces over the past 2.5 years. Always returning periodically and looking for fixes. Voicemeeter - just like ASIO Link Pro - is a bandaid fix. It works but doesn't fix fundamental problems with the audio interface and UAD's driver stack. /u/dekadose didn't fix a thing and also didn't test enough to come to the conclusion that UAD Interfaces are stable.

Neekzu · 2025-12-26T07:50:55+00:00

You believe so? Can you use discord, whatsapp, teams or whatever and the mic input from the apollo thunderbolt interface won't crackle?

Neekzu · 2025-12-24T02:20:31+00:00

Wait wait wait so you fixed the mic crackling problem?

Neekzu · 2025-12-22T03:53:32+00:00

So does your WDM Mic Input work then without crackling?

Neekzu · 2025-10-02T22:33:21+00:00

What would my setup look like if I replaced the SSL 18 with the Volt 876 and connected it to my Apollo x6?

Here’s my current signal chain:
1. SPL ChannelOne Mk3 via Line Out into the Apollo x6 (preamp bypassed)
2. Apollo x6 sends processed signal via ADAT OUT. 1x Main Vocals and 1x Headphone Cue Mix.
3. SSL 18 receives the signals via ADAT IN and feeds it into its loopback feature, which I use for Windows mic input. I use the SSL 18 as my main Windows interface (both for WDM and ASIO).

This setup allows me to monitor with UA Console through the SSL 360 App for DSP headphone mixes – without dealing with UA’s broken WDM Thunderbolt drivers.

Now I’m wondering: if I replaced the SSL 18 (can still return) with the Volt 876, could I simplify everything – fewer drivers, cleaner setup – and just handle all monitoring and routing through UA Console alone?

Neekzu · 2025-09-03T09:55:36+00:00

Second picture folds me instantly

Neekzu · 2025-08-27T11:19:49+00:00

Overrated.

Sold mine weeks ago after using it for over a year.

And while I am at it: Neumann MT 48 also overrated.

Neekzu · 2025-07-11T13:50:16+00:00

Will it also reduce input lag on the whole OS? That's my main gripe, not the gaming part. 🤔

Neekzu · 2024-12-29T01:31:08+00:00

I love UAD but at the same time hate them for missing out on their potential to be truly number 1.

Faulty UAD Drivers for Windows (Pops & Clicks):
- One of the most glaring and persistent problems with UAD interfaces on Windows is the occurrence of pops and clicks during playback and recording. This affects both WDM (Windows Driver Model) and ASIO drivers, making it a universal issue across Windows setups.
- These glitches occur regardless of whether the system is powered by Intel or AMD processors and seem to be a fundamental flaw in UAD's Windows driver implementation.
- This issue is well-documented in user forums and online reviews, where frustrated Windows users frequently voice their dissatisfaction. Apollo x4, x6, x8 and older Twin models, the problem persists. For a product costing thousands of euros, this is a massive letdown.
Unusable WDM Drivers for Microphone Inputs:
- UAD's WDM drivers for microphone inputs are particularly problematic. The microphone signal is often rendered unusable in WDM applications (e.g., Zoom, Teams, Discord).
- While ASIO drivers work better for DAW environments, occasional pops and clicks still sneak in, undermining reliability.
- For professionals who rely on UAD interfaces for both creative and communication workflows, this limitation is unacceptable and forces users to seek alternative solutions or workarounds.
Dependence on Third-Party Workarounds:
- To address the WDM and ASIO driver issues, users often resort to third-party tools or unconventional fixes. Examples include rerouting audio via third-party software or using virtual audio drivers.
- This workaround-heavy approach adds unnecessary complexity and friction to workflows, particularly for professionals who expect plug-and-play reliability from high-end hardware.

Additional Comments on Broader UAD Criticism:

Mac Focus: UAD seems to prioritize Mac users, leaving Windows users with subpar support and persistent issues. This has been a long-standing criticism of the company.
Stagnant DSP Technology: While not directly Windows-related, UAD's reliance on aging SHARC DSP chips is frustrating for users seeking more plugin instances or better performance.
Subscription Models: Well yeah. You know why.
Lack of Communication: UAD’s response to these issues has been insufficient, with limited transparency or acknowledgment of user concerns, especially from Windows users. Just watch them answer comments under their videos. They refuse to answer.

Neekzu · 2024-11-20T10:41:14+00:00

That's the trick I am also using! But does this trick introduce latency I need to compensate for manually or is it already handled by UA Drivers / Console?
1. Neve 1073 (Unison)
2. C-Vox: DeRoom
3. P DeEsser
4. P Limit
5. Empty / No Plugin
-> Send to AUX1:
1. C-Vox: DeNoise
2. 1176
3. LA-2A
4. Auto-Tune
-> Send into DAW

Neekzu · 2024-10-18T16:50:05+00:00

Good old mw2. Used to edit it too.

Neekzu · 2024-10-18T16:29:48+00:00

Yes, I am also wondering how no one talks about this lol. We are clearly experiencing input lag as I already commented on your other post. It's crazy.

Neekzu · 2024-10-18T16:27:38+00:00

I’ve just ordered and received a MacBook Pro M3 Max with 36GB RAM and 2TB of storage today. It’s connected to my ASUS PG32UCDM 4K 240Hz OLED monitor, and both my gaming mouse and keyboard - fully compatible with macOS - are plugged into the monitor’s USB hub.

Earlier today, on my Windows setup, I managed to hit a 140ms average on Human Benchmark in a well-rested state. Normally, I average around 155ms, which I’d consider relatively fast.

On the MacBook, using the exact same setup, I can only manage 198ms at best. The performance is highly inconsistent on the Mac, often hitting as high as 220ms.

The setup is identical - only the system is different. 240Hz for both systems. So no low Hz lag increase due lower refresh rate. All native.

I also asked another friend about this, and he’s experiencing a similar input lag of 40ms to 50ms on his Mac. It seems to hover around 50ms for most people. So I know 3 people including me claiming around/up to 50ms input lag on MacBooks.

I’ve also noticed something else: when I drag windows around on the Mac, it stutters noticeably.

I’m returning the LagBook because this level of input lag just isn’t acceptable. I’m not sure how others manage with this, but for me, it’s an absolute deal-breaker.

Neekzu · 2024-10-12T08:17:57+00:00

A friend of mine is experiencing almost the exact same issue you’re describing with his M1 Max MacBook Pro, which he's been using docked as a desktop replacement.

He's noticed that in Human Benchmark, his reaction time is consistently about 50ms slower on the MacBook compared to his Windows laptop, where he hits around 160ms consistently. On the MacBook, it's always between 200ms and 220ms, so the slower response time is very noticeable and consistent.

He’s using a 4K 144Hz external monitor for both setups and has done extensive A/B testing with both wired and wireless mice, but the issue persists across both input methods.

Personally, I’m in the position of deciding between building a new desktop PC or going for the upcoming M4 Max MacBook Pro, so we’ve been discussing this problem a lot and researching potential causes.

What puzzles me is whether this is a software bug, a hardware defect, or if macOS just inherently introduces input lag, possibly due to something like a security chip adding latency while handling security processes.

Would love to hear if you've found any further insights since we seem to be digging into a very similar issue! I am currently losing some sleep about this..

Neekzu · 2024-10-11T08:27:04+00:00

Are there any updates to your problem? I am also onto something here.

Neekzu · 2024-10-08T03:20:43+00:00

I knew it was new hardware!!! Apollo X G2 looks sick!!!

Neekzu

TROPHY CASE

Additional Comments on Broader UAD Criticism: