jm52 Posted April 5 Share Posted April 5 (edited) Just spent a week messaging support trying to fix this. They appear to not know of this issue.... "Uninstall all other audio hardware devices." Doesn't work. Not a hardware issue. It is a CW/Sonar issue. Installed Halion..... obviously with the generic low latency asio driver. Now CW will NOT work with ASIO selected. And no obvious way to select the correct ASIO driver. Every other program i use provides for selecting the correct ASIO driver.... And all work. I suggested they talk with a programmer to find-out what the CW loader refers to for this setting. No response. SO::::: Anybody have an idea what file/registry entry is CW accessing to select the generic driver? What can i change to force CW to use the correct driver? Why does CW/Sonar NOT provide a way to select which ASIO driver? This has been an issue for years. Nothing in windows applications to uninstall... Anybody? Bueller? Bueller? Edited April 5 by jm52 Link to comment Share on other sites More sharing options...
Promidi Posted April 5 Share Posted April 5 Can it be assumed that you have uninstalled the Generic Low Latency ASIO driver (which is actually just a wrapper) so that the only drivers you have installed are the native ASIO drivers that came with your Audio interface? 1 Link to comment Share on other sites More sharing options...
IgoRr Posted April 5 Share Posted April 5 22 minutes ago, jm52 said: "Uninstall all other audio hardware devices." Doesn't work. Does Cakewalk by Bandlab launch (open) itself for you? If so, you first need to configure the system audio - specifically in the system settings (Windows audio settings) select the driver from your sound card for "Playback" and mark it as "Set Default", then select the same driver in Cakewalk. If Cakewalk does not launch, then try deleting the "AUD.INI" file along the route: C:\Users\IGOR\AppData\Roaming\Cakewalk\Cakewalk Core -- The next time you launch Cakewalk, it will recreate this file, and you will be able to select any of the drivers available in the system. Link to comment Share on other sites More sharing options...
jm52 Posted April 6 Author Share Posted April 6 5 hours ago, Promidi said: Can it be assumed that you have uninstalled the Generic Low Latency ASIO driver (which is actually just a wrapper) so that the only drivers you have installed are the native ASIO drivers that came with your Audio interface? Not possible... Link to comment Share on other sites More sharing options...
jm52 Posted April 6 Author Share Posted April 6 5 hours ago, IgoRr said: Does Cakewalk by Bandlab launch (open) itself for you? If so, you first need to configure the system audio - specifically in the system settings (Windows audio settings) select the driver from your sound card for "Playback" and mark it as "Set Default", then select the same driver in Cakewalk. If Cakewalk does not launch, then try deleting the "AUD.INI" file along the route: C:\Users\IGOR\AppData\Roaming\Cakewalk\Cakewalk Core -- The next time you launch Cakewalk, it will recreate this file, and you will be able to select any of the drivers available in the system. Did that.... selecting asio results in CW wanting to use wasapi.... Cannot select the proper driver. Link to comment Share on other sites More sharing options...
Promidi Posted April 6 Share Posted April 6 2 minutes ago, jm52 said: Not possible... Why not? Link to comment Share on other sites More sharing options...
jm52 Posted April 6 Author Share Posted April 6 (edited) Update:::: just installed Reaper... Prompted to choose hardware... Selected ASIO.... and then used the next menu to select the driver from the three installed. Why is this so hard? Edited April 6 by jm52 Link to comment Share on other sites More sharing options...
jm52 Posted April 6 Author Share Posted April 6 1 minute ago, Promidi said: Why not? How? NOt listed separately on the applications page. Uninstall Halion? Might work... I should not have to do that.... CW should provide a way to select the proper driver. Link to comment Share on other sites More sharing options...
Promidi Posted April 6 Share Posted April 6 5 minutes ago, jm52 said: How? NOt listed separately on the applications page. Uninstall Halion? Might work... I should not have to do that.... CW should provide a way to select the proper driver. Is the “Generic Low Latency ASIO driver” not listed in Control Panel “Programs and features”? You can also go into the Registry and remove ANY unwanted ASIO driver. Remove the unwanted ASIO driver entries in the following locations: HKLM>Software>ASIO HKLM >Software>WOW6432Node>ASIO Link to comment Share on other sites More sharing options...
mettelus Posted April 6 Share Posted April 6 6 hours ago, jm52 said: And no obvious way to select the correct ASIO driver. Only one ASIO driver can be selected at a time, so if the wrong one is selected (I am assuming this is the case if you can see the one you want but it is greyed out), you need to uncheck all ASIO devices currently in use, hit "Apply" (to deselect everything), then select the correct one. Have you tried this? 3 Link to comment Share on other sites More sharing options...
57Gregy Posted April 6 Share Posted April 6 45 minutes ago, jm52 said: Update:::: just installed Reaper... Prompted to choose hardware... Selected ASIO.... and then used the next menu to select the driver from the three installed. Why is this so hard? Frankly, I think WASAPI will give you better performance than any generic ASIO driver. 3 Link to comment Share on other sites More sharing options...
John Vere Posted April 6 Share Posted April 6 (edited) The OP is using a proper ASIO interface and is trying to use its driver, correct? It is true that only Cakewalk/ Sonar has issue with Generic drivers being installed. I use other Daw’s now. One of them is Cubase. So yes it installed the Generic driver. Cubase simply asks you what driver you want to use on first run. I choose my Motu ASIO — end of story. It always uses that device. Waveform- Ditto. Mixcraft-Ditto Studio one Ditto. Harrison- Ditto. All once set up stay connected. More than 2 months ran by and I opened Sonar to get at an older project. I had to update and re authorize. and it crashes. I open in safe mode and get my project back and I opened Preferences and find Im in WASAPI mode?? I noticed the Generic driver on the list. I choose Motu ASIO and carry on. Next day on reboot Im in WASAPI mode again. The only solution is to delete the Generic driver in the RegEdit app. I should not have to do that! So the OP is not alone in their complaint. I know of no other Daw that behaves as badly as Sonar when it comes to driver issues. All the other Daw’s happily ignore the Generic driver. Edited April 6 by John Vere Link to comment Share on other sites More sharing options...
Mr No Name Posted April 6 Share Posted April 6 there's a thing in the preferences, playback and recording called use MMSCS - enable MMSCS for asio driver , maybe obvious , but it caught me out. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now