![]() ![]() However, after tinkering, the FL Studio ASIO drivers started working, but the ASIO4All drivers for Studio One just keep blinking red with that exclamation mark and it will not stop. But it was never a problem before, and those settings had never needed to be played with. I tried everything from Google to YouTube and nothing has worked, I made sure that the settings on the PC were set up correctly because I read that this can cause an issue for recording and playback. First the ASIO4All drivers (latest 2_14), and then the FL studio ASIO drivers, making all the DAWs nonresponsive. Once everything was set up and ready to go, suddenly the ASIO drivers just failed on me. I upgraded to a dual monitor set up yesterday, one with an HD connection and one with a VGA connection, both connected to a graphics card with its own dedicated ram. I am running both Studio One, FL Studio, and Notion 6 on this PC, but never at the same time, except recently when trying the new rewire feature between Studio one and Notion 6. Windows 10 Professional 64bit / Version 20H2 Build 19042.867 Like 8 years ago I have payed around 20€ for M-Audio Audiophile FireWire, it has own ASIO and allows other apps in parallel.I am using Studio One 5 (upgrade from Artist (and not professional)), ![]() Note that is not automatically expensive. In my experience, "tricking" with fancy external software till some degree works, but can't be perfect (such software still has to deal with "laggy" hardware and Windows design). But if that is "usual" activity, getting an interface which natively allow that is the best way to solve the problem. I agree that for using multiple interfaces in parallel (tricky in any case since that needs hardware sync between them) or using several applications in parallel they still can be used. So for normal use, extra proxies are pointless. MS has done relatively good job with WASAPI, on some hardware it even beats dedicated ASIO driver in latency. ![]() Back in time, proxies sitting in the "kernel" could reduce latency a bit. But they have to access hardware driver, which is not ASIO. "FL Studio/ASIO4ALL/other generic" ASIO is visible from applications as ASIO. I tried all others and came back to it all the time. This is why I recommend FL Studio ASIO to people when the topic comes to sound drivers. But you don't need this since you have a working solution called FL Studio ASIO.Īlso, it reduces the CPU load on the DAW, you can see the difference when you switch between WASAPI and FL Studio ASIO.Īnd also you can switch the active playback/recording sound device easily without having to open the Preferences menu. Having multi-input/output soundcard with the internal one and connecting one to another. Yes, there is a way to get low latency with no audio issues. I mean it also focuses on your DAW, but still allows you to hear/send other audio on your PC and still get low latency. With FL Studio ASIO you don't get any issues with the sound or latency. Suspending the Audio engine is not working all the time depending on the task you want. With the MME(32bit) you get sound crackling eventually. There is a solution with WASAPI Shared but it has too much latency. In the beginning, people get some issues and leaves it, but after getting its working principle, you can handle it without a problem.īut the problem with ASIO4All and some other drivers, you can't get sound outside of the DAW. I have had no issue with ASIO4All since I found a way to use it. What should I do, how do I get back to the way things were up until a couple days ago? Things seem to work in WASAPI mode, but it's my understanding that that isn't the best choice. Would you like to switch to WASAPI mode now?" And if I go ahead and try to use it anyway, all the inputs and outputs are listed as ASIO4All, and the usual ones for the Axe or GT-100 are greyed out. For best results, we recommend switching to a compatible ASIO or WASAPI Windows driver. Continuing to use this driver may lead to instability. I even uninstalled that driver, but still Cakewalk doesn't work right with ASIO4All, which I've had installed for ages (and is up to date.) I keep getting this message: "ASIO4ALL v2 This driver is known to be incompatible with Cakewalk. It didn't seem to want to work with ASIO, so I downloaded and installed the specific ASIO driver for it. I just bought a Native Instruments Komplete Audio 6. My usual interfaces are an IK Multimedia Axe I/O and Boss GT-100. I'm running Windows 10, with the latest version of Cakewalk. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |