I just noticed that Sibelius shows a 'Generic Low Latency ASIO Driver' in my list of Audio Interfaces. I have no idea where it came from but Google says it's from Steinberg so maybe it came along with a certain Steinberg notation product I've installed. I have no pressing need for low latency at the moment but I use ASIO4All anyway. (I've heard it has a low cycle impact.) Is there any particular reason to choose one of these drivers over the other? I haven't found a comparison of the two (but I haven't looked very hard). -- Patrick O'Keefe Sib 7.5, GPO4, NotePerformer, lots of EWQL stuff Win10 x64 Pro Intel i7-4771, 3.50Ghz, 16GB RAM Posted by - 04 Apr 07:27PM. >Generic Low Latency ASIO Driver is the driver that is installed by Dorico.

ASIO4ALL - Universal ASIO Driver For WDM Audio: A4A News. Project Brief. Workaround for a bug in the Windows 8/8.1 Bluetooth audio driver (causing BSOD when device is opened twice). This bug seems to have been fixed in Windows 10. Improvement: UI response time and driver (re-) start time.

This may be only me (in Windows 10), but I have found that if I have the Generic Low Latency ASIO Driver installed, Sibelius plugins fail in unexpected ways. I was having weird results for a while after installing Dorico and I eventually determined that weirdness happened if that driver was being used by Sibelius. So I switched to another ASIO driver, and that worked fine until something I did caused Sibelius to use the Steinberg driver again. I went to some effort to uninstall it, and have not had those problems since. This may be a random, one-time event, but since I did not need the driver, I just dumped it. -- Bob An experienced user of Sibelius.

Sib 1.2 - 8, Windows 10 Pro 64 bit, 32 G RAM. For plugin lookup and categories see For manual plugin installation see .