azslow3 Posted Wednesday at 09:45 AM Share Posted Wednesday at 09:45 AM 6 hours ago, Bass Guitar said: Apps like voicmeeter are designed for people who are using their computers on board sound card. Why would you want to install iffy 3rd party apps when you own an audio interface? These apps are not (only) for on board sound and they are not in the category of "generic drivers", they allow flexible audio routing in case (any) hardware interface and OS own features are insufficient. 6 hours ago, Bass Guitar said: Sonar generally doesn’t like generic audio drivers and staff always advise to remove all of them and only use your interface ASIO drivers. Generic drivers can disturb dedicated ASIO drivers, it is recommended to remove them in case of problem, as a part of troubleshooting. And keep them removed in case they are not needed, to avoid these problems appear. That is a good advise for everything not used (not only for audio processing). But when you explicitly use something for a good reason, and that can be generic driver, it is fine. If it works. 6 hours ago, Bass Guitar said: I spotted the FL Studio generic driver in your screenshot which is on the list of things that you need to delete from the registry if you’re having problems with audio. In this thread there was no discussion about any "problems with audio". It is "how to" thread Link to comment Share on other sites More sharing options...
Astraios Posted Wednesday at 11:11 AM Author Share Posted Wednesday at 11:11 AM The FL Studio driver is there because I sometimes use another DAW. That should be okay, right? Since you're so knowledgeable about audio, I have one more question: Does this "loopback stuff" also support ASIO, or does it only work with Wasabii herbs? 🙃 Link to comment Share on other sites More sharing options...
azslow3 Posted Wednesday at 06:54 PM Share Posted Wednesday at 06:54 PM 7 hours ago, Astraios said: The FL Studio driver is there because I sometimes use another DAW. That should be okay, right? Since you're so knowledgeable about audio, I have one more question: Does this "loopback stuff" also support ASIO, or does it only work with Wasabii herbs? 🙃 WASAPI does not require anything to record any WASAPI output (so loop-back, f.e. system sounds), except recording application should be able to work that way (from my knowledge Sonar doesn't, Audacity does). But that doesn't work with ASIO outputs (at least in my tests). Real interface loopback logically should support all directions, but was primary intended to record something (not ASIO) into DAW (ASIO), I mean not other way around. At the moment I don't have Focusrite to check. 1 Link to comment Share on other sites More sharing options...
Amberwolf Posted Thursday at 01:33 AM Share Posted Thursday at 01:33 AM Some loopback drivers do support ASIO, such as O Deus ASIO Link Pro and VBcable's Hifi / asio bridge version. O deus ALP is complicated to setup but it works once you do--it basically sees everyting on the system and provides a routing GUI to connect anything to anything. 1 Link to comment Share on other sites More sharing options...
Bass Guitar Posted Thursday at 03:51 AM Share Posted Thursday at 03:51 AM (edited) I try and stay away from discussion of audio and Daw’s because there are way to many different opinions about it. But for what it’s worth my opinion is very simple. You purchase a brand name Audio Interface that has all the right connections , features and controls that suit your needs. In my case one feature is now Loopback. The other most important thing I learned years ago, is you should always use the latest version of ASIO drivers from the manufacturer website when using a DAW. All other ASIO drivers that don’t belong to a hardware audio interface should be completely removed from your system including the Registry. Take note that this is more a Sonar issue than it is with other audio software. Loopback. Theres 2 different types of audio Loopback. External and Internal. External is when you connect the output of your audio interface back to an input using a patch cable. We use this to test for the accuracy of our reported latency. Example when using Oblique Audio’s RT utility. Internal loopback is where the audio remains digital. Then it makes it available as an optional input to all applications that are designed to access ASIO multi channel audio. Im not dead sure of where it accesses the audio but it seems it would be involved with the Windows mixer. So to answer your question it most certainly is available in ASIO mode. Im not sure it is actually available in other driver modes because I’ve never checked. And a heads up, Just because a Daw includes a generic ASIO driver doesn’t mean you should or have to use it with that Daw. Example Cubase includes a Generic driver that becomes an option when I set up Cubase’s audio system. But I always choose my audio interface driver. Removing FL ASIo driver will not have any effect on using the Daw. You are always better off using your interface’s ASIO driver. Edited Thursday at 03:55 AM by Bass Guitar 1 Link to comment Share on other sites More sharing options...
Astraios Posted Thursday at 11:49 AM Author Share Posted Thursday at 11:49 AM 7 hours ago, Bass Guitar said: Removing FL ASIo driver will not have any effect on using the Daw. You are always better off using your interface’s ASIO driver. Where exactly in the RegEdits Cakewalk Path would you kill the FL Driver? That sounds obvious, that it has no business being there. However, in rare cases, I also have FL Studio as Rewire on Board with Sonar... Link to comment Share on other sites More sharing options...
Bass Guitar Posted Thursday at 04:17 PM Share Posted Thursday at 04:17 PM (edited) Heres' the location. As you see I only have the drivers for the 3 audio interfaces that I use. All else is banished. Simply delete the folder. Common drivers that are installed with music apps are Steinberg, Magix and FL studio. They are supplied as well intentioned options for people using those Daw's who don't have an audio interface. If you are using an Audio interface then for Sonars sake you need to remove them. The problem is that on start up Sonar looks to see what ASIO device is connected and these will then confuse Sonar. The place to check that something is wrong is in Sync And Caching timing device. Even though your Focusrite is checked in the other audio set up tabs, if there is one of these drivers it might show as the "Recording Latency Adjustment." that's obviously going to throw things off in your syncing of new tracks. This is not a bad feature as Noel pointed out. The fact this happens is actually a good feature. Example I just was using my SSL2 interface in another Daw. I needed to switch to my Zoom L8. I had to close the Daw and then it was mad because it didn't automatically switch to the Zoom. You have to go and set that up. I think all my other Daw's as well as Video apps behave this way. To take the screenshot for you I opened Sonar and it had already switched to the Zoom all on it's own. Edited Thursday at 04:37 PM by Bass Guitar 1 1 Link to comment Share on other sites More sharing options...
Xoo Posted Thursday at 08:28 PM Share Posted Thursday at 08:28 PM 4 hours ago, Bass Guitar said: Even though your Focusrite is checked in the other audio set up tabs, if there is one of these drivers it might show as the "Recording Latency Adjustment." that's obviously going to throw things off in your syncing of new tracks. As has been said many, many times, this is wrong. The display is bogus (I think it displays the first ASIO driver), but the correct value from the active device is used for timing. 1 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