NVIDIA acknowledges latency problem (EDIT: FIXED)

[mixtur.se]

LOL. Yes, and what does that mean for your music production, or whatever? In what way does dpc latency affect you personally? And what symptoms do you get? Guess I wasn't clear

I also found the formulation in the changelog weird. It sounds like this fixes a high-latency readout, while the actual problem was that the driver was causing more latency than necessary.

What it means for music production, see my post above. -> Too high DPC latency forces you to work with higher latency / buffer sizes.

Interesting! Could you show me some article or video evidence or anything like that, that shows higher dpc latency = forced to use a higher buffer size? Because the latency caused by nvidia drivers does not affect how your asio driver performs, so I'm very curious about this claim.

It does impact audio performance, which is also why they have the studio drivers. Graphics cards are setup to get the highest framretare and will poll the cpu a lot more frequently than what’s needed which impact pretty much everything else. Some Wi-Fi adapters work in a similar way so turning off Wi-Fi can help audio with audio dropouts. The studio drivers (amd has something similar) is tuned to be less aggressive.

[mixtur.se]

I always thought the solution would be to use Nvidia's "Studio" drivers: https://www.nvidia.de/download/driverRe ... /209201/de

These drivers cater for 3d creators and Adobe, 3d Max etc type of software. I don't think that these are tested with DAWs any differently than the "game ready drivers".

Moreover, the latest studio drivers 436.40 also note the same open issue

RN-08399-536.40_v01 | 14Release 535 Driver for Windows, Version 536.40
Increase in DPC latency observed in Latencymon [3952556]

They are actually pretty much the same drivers with the game ready drivers for audio (or otherwise) with the same limitations, give or take.

The studio drivers is less aggressive in cpu requests and hence reduce real time performance impact. I have done test myself over the years and the difference can be noticeable if you are experiencing problems.

[Pictus]

Improve DPC Latency Spikes For Ada Lovelace-based GPUs(4000 series)
in R536.67 Driver​.
https://forums.guru3d.com/threads/impro ... er.448143/

[Masterofdisaster]

Like what you are gaining from decreased DPC latency? More VST plugins in session? What?

Mainly less clicks and pops, maybe more VSTs and the possibility to
use lower ASIO buffers. The tweaks improve the system performance.

Source? None of what you say makes sense. More vsts are strictly cpu bound. Which tweaks are you referring to, and what is "system performance"?

Impact of high dpc latency on daw performance is well known. An issue with the default configuration of nvidia software (which impacts daw usage) has been known for some years. Perhaps it is you who should google and read up before making demands?

Sure back in the day when cpus were slow and interrupts and threading were issues.
I've yet to see a source to the claim that nvidia driver dpc latency affects asio performance. You (not you specifically maybe) made the claim so you put the source.

LOL. Yes, and what does that mean for your music production, or whatever? In what way does dpc latency affect you personally? And what symptoms do you get? Guess I wasn't clear

I also found the formulation in the changelog weird. It sounds like this fixes a high-latency readout, while the actual problem was that the driver was causing more latency than necessary.

What it means for music production, see my post above. -> Too high DPC latency forces you to work with higher latency / buffer sizes.

Interesting! Could you show me some article or video evidence or anything like that, that shows higher dpc latency = forced to use a higher buffer size? Because the latency caused by nvidia drivers does not affect how your asio driver performs, so I'm very curious about this claim.

It does impact audio performance, which is also why they have the studio drivers. Graphics cards are setup to get the highest framretare and will poll the cpu a lot more frequently than what’s needed which impact pretty much everything else. Some Wi-Fi adapters work in a similar way so turning off Wi-Fi can help audio with audio dropouts. The studio drivers (amd has something similar) is tuned to be less aggressive.

Yes they're setup to get the highest performance IN GAME, how would that affect daw/asio performance?
Again, please provide a source for your claims...

[christianwn]

How graphics can have an impact on audio and asio. If you touch any gui elemnt of your daw, like a knob, open a plugin, you get audio dropouts. The same with harddrives, try to open a folder when the daw is running and you also get audio dropouts.
So how you solve this, is to run your soundcard/usb driver on a separate cpu core from the other drivers, so that interrupt processing do not collide. But with nvidia they where saturating the irq system so all other irq requests got pushed aside and then you got audio dropouts because of that too. So switching to studio drivers, solved that problem on nvidia. This I have done myself and know to be true.

[Kaine]

In general not installing the Experience component along with the gaming driver has the same effect on lowering DPC as using the Studio drivers from my own prior testing on an otherwise well running system. Even with Experience installed currently, it shouldn't be tipping over into the 1000μs and corrupting, I think it's more like an occasionally 800μs peak on a otherwise decent setup and 380μs with it removed. If you're seeing it spike hard enough to generate dropouts, you've got other things in the background that's having a knock on effect pushing it upwards.

I run the gaming drivers on my Ableton/Cubase box with no fuss and I also have Steam, Epic and GOG on there as well.

[Pictus]

How graphics can have an impact on audio and asio. If you touch any gui elemnt of your daw, like a knob, open a plugin, you get audio dropouts. The same with harddrives, try to open a folder when the daw is running and you also get audio dropouts.
So how you solve this, is to run your soundcard/usb driver on a separate cpu core from the other drivers, so that interrupt processing do not collide. But with nvidia they where saturating the irq system so all other irq requests got pushed aside and then you got audio dropouts because of that too. So switching to studio drivers, solved that problem on nvidia. This I have done myself and know to be true.

For lowest possible DPC latency, check
viewtopic.php?p=8820694#p8820694