Tune Posted September 1, 2024 Share Posted September 1, 2024 Hi! I'm using a Scarlett Focusrite 2i2 for recording in Cakewalk. However, it does not show up in the ASIO driver mode. Only driver modes like WASAPI or MM32. I've done a bit of research and supposedly ASIO is the best driver mode for recording as it produces the least amount of latency. That being said is there any way I can get my device to be recognized in ASIO? Thanks! P.S. I have the same problem with my Peavey and Yamaha mixers as well. Link to comment Share on other sites More sharing options...
DeeringAmps Posted September 1, 2024 Share Posted September 1, 2024 Did you install Focusrite’s ASIO driver? Link to comment Share on other sites More sharing options...
Tune Posted September 1, 2024 Author Share Posted September 1, 2024 5 minutes ago, DeeringAmps said: Did you install Focusrite’s ASIO driver? I ran Window's automatic driver update search and it said the most up to date drivers were already installed on it. Link to comment Share on other sites More sharing options...
Tune Posted September 1, 2024 Author Share Posted September 1, 2024 (edited) 45 minutes ago, DeeringAmps said: Did you install Focusrite’s ASIO driver? Wow, turns out I needed to follow the "easy setup" on the box. 🙃 Followed the instructions, downloaded the software, it updated the device. Now it shows up in ASIO mode!! Hurray! 🤣 I thought I'd never see the day... Thanks for the suggestion! Edited September 1, 2024 by Tune 2 Link to comment Share on other sites More sharing options...
Wookiee Posted September 1, 2024 Share Posted September 1, 2024 5 hours ago, Tune said: I ran Window's automatic driver update search and it said the most up to date drivers were already installed on it. That would have probably installed ASIO4all which is not supported and isn't really ASIO. 1 Link to comment Share on other sites More sharing options...
Leo .R.S. Posted January 11 Share Posted January 11 On 8/31/2024 at 9:23 PM, Tune said: Wow, turns out I needed to follow the "easy setup" on the box. 🙃 Followed the instructions, downloaded the software, it updated the device. Now it shows up in ASIO mode!! Hurray! 🤣 I thought I'd never see the day... Thanks for the suggestion! Hi bro, can you tell me, what did you exactly do? I have the same problem 😞 Link to comment Share on other sites More sharing options...
Starship Krupa Posted January 12 Share Posted January 12 13 hours ago, Leo .R.S. said: Hi bro, can you tell me, what did you exactly do? I have the same problem 😞 Go to Focusrite's website, download the software for your interface and install it. Windows doesn't (yet) have native ASIO drivers, so it's always necessary to get them from the manufacturer's website. Link to comment Share on other sites More sharing options...
Amberwolf Posted January 12 Share Posted January 12 4 hours ago, Starship Krupa said: Windows doesn't (yet) have native ASIO drivers, so it's always necessary to get them from the manufacturer's website. And to uninstall any of the generic ASIO drivers like ASIO4all, etc. Link to comment Share on other sites More sharing options...
Leo .R.S. Posted January 17 Share Posted January 17 On 1/11/2025 at 9:23 PM, Starship Krupa said: Vaya al sitio web de Focusrite, descargue el software para su interfaz e instálelo. Windows no tiene (todavía) controladores ASIO nativos, por lo que siempre es necesario obtenerlos del sitio web del fabricante. I'm supposed to have already installed them, but when I select the ASIO driver in Cakewalk it doesn't detect the interface, but if I select another one like WASAPI it does detect it. Do you have a solution for that? Link to comment Share on other sites More sharing options...
Chaps Posted January 17 Share Posted January 17 25 minutes ago, Leo .R.S. said: I'm supposed to have already installed them, but when I select the ASIO driver in Cakewalk it doesn't detect the interface, but if I select another one like WASAPI it does detect it. Do you have a solution for that? I had that problem and discovered that because I had an audio driver installed (Steinberg low latency driver) other than the one I needed to use (the Yamaha Steinberg USB ASIO driver) I was not able to use ASIO in Cakewalk by Bandlab. Didn't make any difference that I wasn't using the other driver or that it didn't show in the Cakewalk audio devices list. Just having it installed was the problem. Once I uninstalled the Steinberg driver I was able to use ASIO in CbB. I suggest opening the Registry Editor and looking in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO to see what is there. Before I did that I used Revo Uninstaller to see what other audio drivers were installed and that's when I saw the Steinberg driver was installed and I uninstalled it using Revo Uninstaller. I always use Revo to uninstall software because it has the ability to delete registry entries along with everything else related to the software you are installing. 1 Link to comment Share on other sites More sharing options...
Leo .R.S. Posted January 19 Share Posted January 19 On 1/17/2025 at 3:06 PM, Chaps said: I had that problem and discovered that because I had an audio driver installed (Steinberg low latency driver) other than the one I needed to use (the Yamaha Steinberg USB ASIO driver) I was not able to use ASIO in Cakewalk by Bandlab. Didn't make any difference that I wasn't using the other driver or that it didn't show in the Cakewalk audio devices list. Just having it installed was the problem. Once I uninstalled the Steinberg driver I was able to use ASIO in CbB. I suggest opening the Registry Editor and looking in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO to see what is there. Before I did that I used Revo Uninstaller to see what other audio drivers were installed and that's when I saw the Steinberg driver was installed and I uninstalled it using Revo Uninstaller. I always use Revo to uninstall software because it has the ability to delete registry entries along with everything else related to the software you are installing. I just tried what you proposed, but it didn't work. I had another Beer Driver installed and I uninstalled it with Revo but it doesn't work, could it have something to do with the fact that it is not detected from Focusrite Control? Typical non-hardware connected Link to comment Share on other sites More sharing options...
Amberwolf Posted January 19 Share Posted January 19 5 hours ago, Leo .R.S. said: I had another Beer Driver installed What specifically is a "Beer Driver"? 5 hours ago, Leo .R.S. said: but it doesn't work, could it have something to do with the fact that it is not detected from Focusrite Control? Typical non-hardware connected If that is an app that comes with the device (or is from the manufacturer of the device, made for that device), and it doesn't see the hardware, it means the hardware doesn't have the drivers for it installed, or there is a problem with the drivers being unable to detect the device (usually because of a hardware problem, but sometimes because of drivers for a different device that may not even be connected to the system anymore, but are still installed). Link to comment Share on other sites More sharing options...
Sock Monkey Posted January 21 Share Posted January 21 The OP has the answer They actually read the very clear instructions supplied by Focusrite. What a concept hey! Reading the instructions. And Asio4all is never installed by Windows. Windows will use its own drivers , WASAPI, MME or WDM. It has never been involved in downloading ASIO. You always need to download the drivers from the manufacturer web site. This is always CLEARLY outlined by the Quick start guide that is ALWAYS in the box! Asio4 all doesn’t interfere with your ASIO driver. The only known issue is with Steinberg generic and Magix . And only with Sonar and Cakewalk. They sometimes confuse the software. Doesn’t seem to happen elsewhere. Real tech also has a very bad ASIO driver but that also doesn’t matter if you use a proper ASIO audio interface. . It can only be used when you use the Realtek sound card. But they advise that you use WASAPI instead. Link to comment Share on other sites More sharing options...
T Boog Posted January 21 Share Posted January 21 (edited) 4 hours ago, Sock Monkey said: What a concept hey! Reading the instructions Stop trying to make us read Sock. We'd rather die! 😋 Edited January 21 by T Boog 1 Link to comment Share on other sites More sharing options...
msmcleod Posted Sunday at 10:18 AM Share Posted Sunday at 10:18 AM On 1/21/2025 at 3:52 AM, Sock Monkey said: Asio4 all doesn’t interfere with your ASIO driver. The only known issue is with Steinberg generic and Magix . And only with Sonar and Cakewalk. They sometimes confuse the software. Doesn’t seem to happen elsewhere. Actually it does. As soon as you open ASIO4ALL, it opens the WDM driver for your audio interface and sets its sample rate/bit depth to what ASIO4ALL wants. Even when the DAW closes the ASIO4ALL driver, ASIO4ALL stays active in the system tray with the WDM driver still open. Most audio interfaces will refuse to operate in different sample rates/bit depths in WDM / ASIO mode, so ASIO4ALL and the native ASIO driver will be fighting each other. Some audio interfaces won't even allow WDM and ASIO to be used at the same time. Obviously YMMV depending on what audio interface you're using, but the above highlights the main issue with using ASIO4ALL. TLDR: If you're using Realtek, use WASAPI. For anything else, use native ASIO driver for your audio interface. DO NOT use ASIO4ALL unless you absolutely need to, and you fully understand what it's doing. 2 1 Link to comment Share on other sites More sharing options...
Sock Monkey Posted Sunday at 03:54 PM Share Posted Sunday at 03:54 PM Excellent explanation. What I was told a long time ago was having asio4 all installed should not cause problems if you don’t use it. I personally have almost no experience with it. I remember installing it years ago when all I had was a sound blaster card. It didn’t work then either. Link to comment Share on other sites More sharing options...
pwalpwal Posted Sunday at 04:55 PM Share Posted Sunday at 04:55 PM i personally have no issues with asio4all and use it all the time for the laptop realtek 6 hours ago, msmcleod said: Even when the DAW closes the ASIO4ALL driver, ASIO4ALL stays active in the system tray with the WDM driver still open. this is not true for studio one or ableton live or standalone VSTs like arturia or cherry audio, closing the daw/host closes the driver, life continues /goodluck Link to comment Share on other sites More sharing options...
Sock Monkey Posted Sunday at 11:16 PM Share Posted Sunday at 11:16 PM 6 hours ago, pwalpwal said: i personally have no issues with asio4all and use it all the time for the laptop realtek this is not true for studio one or ableton live or standalone VSTs like arturia or cherry audio, closing the daw/host closes the driver, life continues /goodluck This is what I have observed as well as far as these other driver s that only seem to cause issues in Sonar. You will never see poeple having those issues in most other Daw's. This is why Steinberg includes the generic driver, it works. But not in Cakewalk or Sonar. I learned this after I had upgraded to Cubase 14 and I was also only using Mixcraft as well as sometimes testing Harrison and Waveform. I had no issues at all for a few weeks. I then one day opened Sonar and had no sound. I quickly spotted the Generic drive so I removed it in reg edit. But as I say. All those other Daw's used my Motu interface happy, happy. Only Sonar it would seem is ultra sensitive to drivers. Link to comment Share on other sites More sharing options...
pwalpwal Posted Monday at 04:32 PM Share Posted Monday at 04:32 PM 17 hours ago, Sock Monkey said: Only Sonar it would seem is ultra sensitive to drivers. i guess it's to do with their implementation of wdm driver mode, and that clashes with asio4all's wdm wrapper implementation 🤷♀️ 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