search

dechamps / FlexASIO

A flexible universal ASIO driver that uses the PortAudio sound I/O library. Supports WASAPI (shared and exclusive), KS, DirectSound and MME.
Other
1.35k stars 72 forks source link

Use ASIO backends too? #239

Closed josephernest closed 3 months ago

josephernest commented 3 months ago

Hi, I noticed: FlexASIO can use MME, DirectX, WASAPI, etc. and nearly all backends available from PortAudio. But can it use ASIO backends too?

I know it doesn't make much sense because the goal of FlexASIO is to provide a bridge x to ASIO, where x != ASIO, I agree that most of the time, ASIO2ASIO wouldn't make sense.

In my case, it would help, because I could handle all my devices from a single config file. Laptop case : WASAPI2ASIO Studio case : ASIO2ASIO (!) with channel_count=16 Everything without changing the device in Ableton Live, just by automating the changes in the .TOML file (and your excellent feature watches the .toml filechange and restarts the driver!)

Do you think this crazyness can be easily enabled? I guess you probably have a filter in PortAudio listing to avoid devices that are ASIO already, is that right, can this if be easily removed?

dechamps commented 3 months ago

This is a duplicate of #67. I'll answer there.

josephernest commented 3 months ago

Thanks @dechamps.

There is a slight difference between my proposal here and #67: there, they want to be able to mix different backends, which is hard and non-trivial.

In my case, I just want to be able to choose backend=ASIO (which is already provided by PortAudio), and use only ASIO backend.

(Until I modify the .toml, and then the driver will restart, and I'll use only WASAPI backend).

TL;DR here I'm asking about using ASIO backend only, whereas #67 deals about multiple backends at the same time.