• SONAR
  • [SOLVED] Generic Low Latency ASIO driver...
2017/09/22 19:32:05
Resonant Serpent
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.
2017/09/22 19:50:23
Cactus Music
I think I've read this before and it's a Stienberg issue so that will help you narrow it down. Seems installing the newer versions of any Stienberg software trashes things. This is not the case with older versions as I have both Cubase 5 LE and Wave Lab 7 Elements.
Google "stienberg generic ASIO driver"  
 
https://www.steinberg.net/forums/viewtopic.php?f=226&t=103828
 
 
 
2017/09/22 20:33:20
Resonant Serpent
Thanks. 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. Then this...
 
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. 
2017/09/22 20:40:08
scook
try renaming aud.ini in the SONAR user directory
2017/09/23 02:14:45
Resonant Serpent
scook
try renaming aud.ini in the SONAR user directory




I did. No difference. Going to try the full re-install route and see how that pans out.
 
2017/09/23 02:26:41
scook
By full reinstall I assume you mean this or this if you have X3
2017/09/23 02:34:37
Resonant Serpent
The 2015 Knowledge Base article. Just tried it, and it didn't work. I've had the generic ASIO driver installed for over two years, and zero problems. No idea why it cropped up now. Time to start uninstalling the other items to see what happens.
 
Thank you for your help.
2017/09/23 02:42:00
scook
IDK either but I have seen other threads where that driver was a problem. The only solution was removal of the driver. It should not be necessary if you interface has a factory supplied ASIO driver.
2017/09/23 02:57:16
Resonant Serpent
Correct.
 
I figured out how to solve it, but not the why of how it happened to begin with. I deleted the ASIO folder in the Cubase install. I did this once before, but I guess it didn't take. After rebooting to assure that it was gone, I started Sonar and the constantly loading window as gone. I will mark this thread solved.
 
Thanks to everyone for your advice.
2017/09/25 15:52:18
Resonant Serpent
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. There has to be a fix for this. Take us back to when we had to reboot the program to switch drivers if that's what it takes for further stability. Unused/unseen drivers shouldn't be able to hijack the host program.
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account