Version 0.3a progress about flexasio HOT 3 CLOSED

Solved! I forgot to set both the Windows playback devices and recording devices to 48Khz!

PS: is there a configuration file to set 44.1khz for Flex instead of 48khz? and a configuration file to set 512 or 256 latency instead of 1024 (without recompiling)?

from flexasio.

is there a configuration file to set 44.1khz for Flex instead of 48khz?

FlexASIO (more specifically, WASAPI Shared) uses the sample rate that your devices are set to. If you change both your input and output devices to 44.1 kHz, FlexASIO will use 44.1 kHz.

That said, from looking at your log I get the impression that it's Ableton that enforces the 48 kHz sample rate here; indeed, it never calls canSampleRate(), it just sets the sample rate to 48 kHz directly without asking FlexASIO which sample rates it supports. That can mean one of two things: either it's a setting you need to change in Ableton itself (not FlexASIO), or it tries to negotiate the sample rate with the ASIO driver in a more "subtle" way (e.g. it expects setSampleRate() calls to fail) which FlexASIO doesn't support.

If you really think it's FlexASIO's fault, then please open a separate issue that is specifically about sample rate negotiation between Ableton and FlexASIO, and I'll see if I can take a look. I could add a configuration knob to force FlexASIO into a specific sample rate, but I'd like to make sure that's really necessary first.

a configuration file to set 512 or 256 latency instead of 1024 (without recompiling)?

Again, this is something that the ASIO host application (here, Ableton) should be able to control. FlexASIO only "suggests" a preferred buffer size; the host application can decide to set it to something else. Ableton should allow you to change it somewhere in the settings. If it does not, then please file a separate issue to request a configuration knob for it.

from flexasio.

That said, from looking at your log I get the impression that it's Ableton that enforces the 48 kHz sample rate here; indeed, it never calls canSampleRate(), it just sets the sample rate to 48 kHz directly without asking FlexASIO which sample rates it supports. That can mean one of two things: either it's a setting you need to change in Ableton itself (not FlexASIO), or it tries to negotiate the sample rate with the ASIO driver in a more "subtle" way (e.g. it expects setSampleRate() calls to fail) which FlexASIO doesn't support.

True, the previous setting in Ableton was 48 Khz (with the previously-used audio playback device):

that's why it was then trying to use 48Khz when opening Flex.

So this issue is not really a big issue: one just has to set the right sample rate before selecting Flex.

If you really think it's FlexASIO's fault, then please open a separate issue that is specifically about sample rate negotiation between Ableton and FlexASIO, and I'll see if I can take a look. I could add a configuration knob to force FlexASIO into a specific sample rate, but I'd like to make sure that's really necessary first.

Yes, in a future "release" version, this could be useful, because the end user should never see "Failed to open the device Flex", so a clever sample rate negotiation could be useful. But for now, I think it's a minor issue, because we know how to solve it (just set the right sample rate before changing the device to Flex in Ableton).

I created 2 issues as you suggested in your previous message, and I close this one here:

• (minor issue) #18
• (more important one) #19

from flexasio.