- Fl studio asio driver not working install#
- Fl studio asio driver not working drivers#
- Fl studio asio driver not working driver#
- Fl studio asio driver not working Pc#
My speculation is you are basically confusing the heck out of your interface if you are using more than one app, for instance one app may be wanting a different sample rate and the other does not. It's like something gets switched off and I can not for the life of me, simply re-select my FP10 in the "Sounds"/"Playback Devices" panel.
Fl studio asio driver not working Pc#
It's only a matter of time before WMP, YouTube or VLC fail to play via my monitors and revert to only playing through my PC speakers.
Fl studio asio driver not working driver#
If I uninstall my Firewire and FP10 driver they're reinstalled after a "Restart" and all plays through my monitors but only for an hour or so. My Win 8.1 updates listed as "Security" and "Rollout" types. I wonder if it was something in one of the Windows updates? My FP10 stopped working around a day of this post. I know this is NOT what you wanted to hear but it IS the facts imo FL Studio ASIO driver is made specifically FOR FL Studio and if it has been working in other DAWs then consider yourself lucky.
Fl studio asio driver not working install#
even now FL Studio installation installs ASIO4ALL during the install process and honestly ASIO4ALL's ASIO driver has ALWAYS worked better for me than the new FL Studio ASIO driver. you can't expect Presonus to try and make their product work with another company's proprietary driver. it is what they used before trying to create their own proprietary driver) (ASIO4ALL has always worked great in FL Studio.
Fl studio asio driver not working drivers#
actually FL Studio ASIO is only solid on FL Studio for me (on 2-3 systems now) so i don't use that driver because ASIO4ALL and my Audient ASIO drivers have worked fine in FL Studio. i have been using FL Studio since probably 2005 and when Image-Line made their own ASIO driver it was give and take on all my DAWs. It is hardcore to get this working, but totally worth it.My suggestion is to use ASIO4ALL and see if it works for you. But on normal sound cards, you can run Jack and use ALSA at the same thank you so much for WineASIO. there seems to be a lot of bugs here, where you have to start one thing before the other and can't have another enabled or disabled or it breaks things for no reason.īut could the "main bug", the one that requires use of snd_dummy, be caused by my card supporting multichannel playback? On cheap sound cards like snd_hda_intel, using Jack will block the only channel it has and you can't use the card via ALSA anymore. If you use "Autostart Server", you don't have to worry about stopping Jack before starting Wine, it avoids this other bug as it can only run after.ĭon't select anything but 44100 as sample rate, or a popup will tell you that the ASIO driver doesn't support it and then it doesn't work until you restart Wine. Run setcap cap_sys_nice+ep /usr/bin/wineserver once like documented here: Īnd then like I said use the icon on the virtual desktop to start FL. In regedit -> HKLU->Software->Wine->WineASIO I enabled "Autostart Server" and I disabled "Fixed Buffer Size" (and set buffer size to 512) so I can just use this shortcut with its own wine prefix so it doesn't mess up my other windows programs:įRUITY= killall -9 jackd sleep 0.1 STAGING_RT_PRIORITY_SERVER=92 STAGING_RT_PRIORITY_BASE=92 WINEDEBUG=-all ASIO_INPUTS=4 ASIO_OUTPUTS=8 WINEARCH=win32 WINEPREFIX=/mnt/2/wine32_FL wine explorer /desktop=FruityLoops,1920x1040 start FL studio from the virtual desktop icon (don't use "winedbg -command cont FL.exe" or "tee >/dev/null" to prevent the logo freeze! or it will bug out just like before) start winecfg and switch all sound outputs to the Dummy soundcardĤ. While fiddling with the other sound card, I discovered: THE WORKAROUNDģ.