Mark Fergel Posted May 4 Share Posted May 4 Went to start recording today. Usually use WASAPI shared. Switch to ASIO (which I've done before) and it gets stuck in a loop when it runs through the profile and writes to the AUD.INI. The only way out of it is to end task on Cakewalk, boot into safe mode, go into Cakewalk and change the driver back to WASAPI, and then restart to get out of safe mode. I've tried reinstalling the Realtek drivers. Tried doing a google search and can't seem to find anyone with the same issue. I'm stuck because now I don't have any way of switching to ASIO to record audio tracks. I can record a screen capture video if that helps people understand the issue. Link to comment Share on other sites More sharing options...
Mark Fergel Posted May 4 Author Share Posted May 4 Here's a video of where it just loops this every few seconds. It's writing to the AUD.INI file each time it does this. Recording 2025-05-04 181802.mp4 Link to comment Share on other sites More sharing options...
Amberwolf Posted May 4 Share Posted May 4 Which specific ASIO driver are you using? What other ASIO drivers are installed on the system, even if not in use or disabled? Link to comment Share on other sites More sharing options...
OutrageProductions Posted May 4 Share Posted May 4 (edited) Real ASIO drivers don't go through the audio profile dialog AFAIK. Only WDM & WASAPI. There isn't currently a true ASIO driver for MOBO audio (coming soon on next gen HW tho!), only for external audio interfaces. If you have a fake (ASIO4ALL/Realtek/Behringer, et al) driver that says it's ASIO, then you're asking for problems. Edited May 4 by OutrageProductions 1 Link to comment Share on other sites More sharing options...
ptheisen Posted May 5 Share Posted May 5 Add to the list of pseudo ASIO drivers that cause problems for Cakewalk: Steinberg Virtual ASIO, which gets installed anytime a Steinberg product is installed on your system. If that is the case, it should be uninstalled, it won't hurt anything else, and will possibly make Cakewalk work the way it is supposed to when using ASIO drivers. Link to comment Share on other sites More sharing options...
Max Arwood Posted May 5 Share Posted May 5 (edited) Magix & FL studio too Edited May 5 by Max Arwood Link to comment Share on other sites More sharing options...
Canopus Posted May 5 Share Posted May 5 7 hours ago, OutrageProductions said: If you have a fake (ASIO4ALL/Realtek/Behringer, et al) driver that says it's ASIO, then you're asking for problems. For the record, Behringer use ASIO4All for their cheapest interfaces, but true ASIO compliant drivers for the others. Also, they never call their ASIO4All drivers anything but ASIO4All, so there should be no risk of confusion. Link to comment Share on other sites More sharing options...
lɐʍdlɐʍd Posted May 5 Share Posted May 5 ah this old chestnut Link to comment Share on other sites More sharing options...
Mark Fergel Posted May 5 Author Share Posted May 5 20 hours ago, ptheisen said: Add to the list of pseudo ASIO drivers that cause problems for Cakewalk: Steinberg Virtual ASIO, which gets installed anytime a Steinberg product is installed on your system. If that is the case, it should be uninstalled, it won't hurt anything else, and will possibly make Cakewalk work the way it is supposed to when using ASIO drivers. You nailed it. I installed Steinberg Backbone a couple of months ago and I bet that installed the Steinberg ASIO drivers. Unistalled those and its working fine again (I was using the Universal Audio drivers for the Volt 2). Thanks for the help. Link to comment Share on other sites More sharing options...
OutrageProductions Posted May 5 Share Posted May 5 15 hours ago, Canopus said: Also, they never call their ASIO4All drivers anything but ASIO4All This is true for their lower end I/O's from 2021 onwards. Prior to that... not so much. Hence the A4A issues. 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