Depends what you mean by audio drivers, if you mean the audio server, Jack has always been good for pro audio, and pipewire (the modern default) can be configured to be good too with the right packages. In terms of timing (latency you mean?) I have zero complaints using Jack via pipewire on a proper audio interface.

If you mean device drivers, it can be a bit hit or miss, generally stuff works but for example I have an SSL audio interface and while the audio works, it's missing a lot of the configuration options that the Windows drivers give you around customisable audio routing.

▲

criddell 2 hours ago | parent [-]

> latency you mean?

Maybe timing is the wrong word. Latency is definitely a related concern.

If something needs to fire every 1209 ms then it can't get fired in 1232 ms this time and then 1198 ms next time. Maybe a better term would be clock jitter or drift?

As I understand it, a DAW needs something close to a RTOS.

	▲	MrDrMcCoy 2 hours ago \| parent \| next [-]
		Linux can run specific apps with realtime priority since 6.12. Just gotta configure your audio stack to run that way.
	▲	lewispollard an hour ago \| parent \| prev [-]
		Ah yes, I understand - yes as the other comment says, kernel supports it but most distros aren't configured that way out of the box, but it's pretty simple in most of them - on Arch you install the `realtime-privileges` package and add your user to the `realtime` group, the audio server and DAW software takes it from there.