Nov 02, 2014  What the heck happened to my ASIO driver? I don't know why installing Cubase 7.5 screws up ASIO drivers/settings but it did for me. ProgramFiles Steinberg Asio which contained the Generic Low Latency ASIO Driver. Ran CCleaner to clean registry of the driver info. I have an asio driver, and an asio multimedia driver. And the latency is at 155ms which is ridiculously high for recording, i have tried everything i can think of, but i cant lower the latency so that there isnt a delay from when i play my instrument through my desk into the computer.

Chainer comes in two flavors (free and not free). Avast internet security serial key 2038 calendar. For live performance, the input latency problem doesn't come from you asio driver, but almost certainly because of using an emulated midi input; t's a well known problem in Cubase, the solution is to move ignoreportfilter file to the root of your Cubase installation, then choose the non-emulated version of your input (you can hide the emulated versions if you want). This has been fixed starting with Cubase SX 3. 45 ms seems very high for a specific asio driver, have you tune it?

[SOLVED] Generic Low Latency ASIO driver. In the past couple of days, I installed Wavelab 9 and Reason 9.5. Now, when I start Sonar, I get a small window popping up every second saying: Generic Low Latency ASIO Driver Record 13 + 14 (LynxTwo-C) Checking 2 Channels 96000 SPS 16 BPS I uninstalled the driver, and followed the configuration resetting instructions. I never had this driver activated.

Still, I get the message. I tried re-installing Sonar. Even with the driver uninstalled, it still shows as an option in the Sonar driver selection window. Anyone have a clue? S1, Reaper, and Cubase still running normal. Sonar is unusable. I googled it, and read up, but no real solution.

I followed everything I could find including uninstalling the driver and the registry edits, but still having the problem in Sonar. This is how it is. I took the time to wipe every vestige of Sonar off my machine, reinstalled, and everything was great for a couple of weeks.

I've spent more time trouble-shooting Sonar than I have using it over the past month. At this point, I'm ready to call it a day. Maybe when I decide to upgrade to Windows 10, it'll work like it should. I'm not a newb. I've been using Sonar products since 1995. Like I stated, none of my other programs are showing any kind of error.

Updating for those who may have this problem in the future. I was able to use Sonar again, but, Rewire wouldn't load in any host. I reinstalled Reason, and everything is now operating properly. I don't know exactly why, but it seems that Rewire has some kind of interaction with the Generic ASIO Driver installed by Cubase. I know that Cubase and Props initially developed Rewire together, so maybe that's a clue. My main concern is that drivers that I don't have enabled in the program, or even showing up in the program dialog (AMD High Definition Audio Device) are affecting the way Sonar runs.