You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the time of writing this, it is currently a pain in the neck integrating ASIO drivers with Linux. Users have complained about the installing ASIO drivers with PlayOnLinux with no luck. KXStudio provides WineASIO, however, it is only compatible with Ubuntu Linux distributions, meaning Federo, Debian, & other non-Ubuntu Linux users are out of luck . It would be nice if FlexASIO were a cross-platform driver.
Just to clarify things in case people get confused: there is no such thing as "ASIO on Linux" or "ASIO on Mac". The ASIO spec is only defined for Windows; there is no defined way to discover and load ASIO drivers on Linux nor Mac.
The only way your request makes sense is when discussing Windows emulation layers for foreign OSes (e.g. Wine).
It looks like you want FlexASIO to detect when it's running under a Windows emulation layer such as Wine, and change its behavior accordingly, i.e. bypass the emulation layer and reach out directly to native OS audio APIs.
Because FlexASIO is really just a thin wrapper around PortAudio, in practice this would be a PortAudio feature request, which I just filed under PortAudio/portaudio#929.
I wouldn't hold my breath though - this sounds very messy to implement, and it may be vastly easier to improve WineASIO to work on your particular distribution instead.
At the time of writing this, it is currently a pain in the neck integrating ASIO drivers with Linux. Users have complained about the installing ASIO drivers with PlayOnLinux with no luck. KXStudio provides WineASIO, however, it is only compatible with Ubuntu Linux distributions, meaning Federo, Debian, & other non-Ubuntu Linux users are out of luck . It would be nice if FlexASIO were a cross-platform driver.
WineASIO: https://github.com/wineasio/wineasio
KXStudio: https://kx.studio/
The text was updated successfully, but these errors were encountered: