However as Resolve now does its "Clean Feed" monitor window without the need for specific hardware, and factoring in the incredible functionality that comes in the free version of Resolve, it appears BMD are focused on making Resolve as widely accessible as possible.ĪSIO drivers have certainly established themselves as the most successful, low-latency audio hardware driver system. BMD would of course want Resolve to work best when using BMD / Fairlight hardware. Yes, until recently I would have agreed with that. Re: Problems with plugins and Generic Low Laten.Rick van den Berg wrote:I think this has everything to do with business/the hardware blackmagic provides. Problems with plugins and Generic Low Latency A. Maybe Sib doesn't like it if multiple versions are running the same ASIO driver?Īnyway, I have not seen and random plugin failures since I did this.
Possibly that is a bad idea but I had been doing it for years with no obvious bad results. It could have something to do with the fact that I have several installed versions of Sibelius and I sometimes run them simultaneously. I was using the Yamaha driver, but then at some point I would run a version of Sibelius and in the startup screen I would see a bunch of flashing and the GLLA text was in the flashing text. I note that I never chose the GLLA driver in Sibelius. I am pretty sure it came in with a Steinberg product but I didn't find anything googling over there either. I just got fed up with weird stuff happening, and at least that does not seem to be happening anymore. I am keeping a close eye on anything that might have used that driver and so far it looks OK. I do not recommend this as a technique because of possible corruption of the registry. So I made a restore point and exported the Registry and just removed entries that looked like they were real entries for that driver. I don't really even see a way to tell it is installed other than looking for the name in the Registry. The only googling I found that gave any answer at all suggesting removing entries in the registry. It does not appear in the Control Panel uninstaller. I could find no way to uninstall the Generic Low Latency ASIO driver. Re: Problems with plugins and Generic Low Latency ASIO driver
Sib 1.2 - 8, Windows 10 Pro 64 bit, 32 G RAM. But I would really like to get rid of it.Īn experienced user of Sibelius.
So I just thought I would warn everyone that if your plugins start weirdly misbehaving, make sure you are not using that driver.Īnd does anyone know how to totally remove that driver (Windows 10)? It is not obvious and googling has led me in circles enough time that I have been putting up with it. The plugin usually has nothing to do with the sound. If I load another sound driver, the plugins suddenly work. If that driver is loaded, plugins fail unpredictably. If I think to look, sometime my Yamaha driver is not in the list, and I change it to something else.īut often I am not interested in the sound so I let it be.īut here is the weird part. I had problems with it and never used it, choosing the Yamaha Steinberg one instead.Įvery once in a while when loading Sibelius, I see flashing and text suggesting that the Low Latency Driver is loading. I have a Steinberg UR 22 mkII usb audio interface, and it indluded an ASIO driver, Yamaha Steinberg ASIO driver, and it works fine.Īt some point, possibly after installing Cubasis or Dorico, I also ended up with a driver called "Generic Low Latency ASIO driver". Re: Problems with plugins and Generic Low Laten.
Messages in this thread Problems with plugins and Generic Low Latency A.