Setting sample rate?

[Enaphets]

Hi there,
Is it possible to set the sample rate of FlexASIO in the config file?
I tried a few times but didn't seem to work.
I tried adding a line...
Sample rate = 44100,it didn't seem to switch anything.

Thanks

[dechamps]

In ASIO, the sample rate is normally decided by the application, not the driver. The application can ask the driver if it supports a given sample rate and then switch to it.

It follows that if you want to change the sample rate, the proper way to do that is from within the application. If that's a problem for you, then more details about your use case would be helpful.

[dechamps]

Where do you want me to upload the log?

You can upload the log by attaching it to your reply on GitHub.

[Enaphets]

Here is the log,

So i guess you will see 2 phases in there,first one is when i start Asiolinkpro which uses Flexasio and then second one when i start the music software which will use a second Asio instance and where i get the invalid sample rate message
FlexASIO.log
.

[dechamps]

The log doesn't show anything going wrong really. As I suspected initially, asiolinktool.exe takes the default sample rate from FlexASIO (48000 Hz in your case) and just rolls with it and starts streaming normally. There are no errors in the log and I don't see anything that could possibly result in an application showing an "invalid sample rate" message.

Here's what I think is happening: the problem is on the other side, i.e. between ASIO Link Pro and Plogue Bidule. Specifically, it looks like ASIO Link Pro "locks" itself to the 48 kHz sample rate before Bidule initializes. Presumably Bidule doesn't like 48 kHz and tries to make ASIO Link Pro use 44.1 kHz instead, but at this point it's too late.

If my theory is correct, then technically this is not a problem with FlexASIO (the log clearly shows it's not doing anything wrong). The problem is that ASIO Link Pro does not seem to allow the application to change the sample rate. That would explain your "invalid sample rate" message and the fact that you need to manually adjust the settings in ASIO Link Pro to match the sample rate the application expects.

The log shows you are using WASAPI. Have you tried the workaround I described earlier? I.e. go to the Windows audio control panel settings for your "Speakers (Roland Rubix 22)" device and change the "Default format" to 44100 Hz. That will make FlexASIO use 44100 Hz as its initial sample rate, which should in turn compel ASIO Link Pro to use that sample rate by default, and Plogue Bidule should then be happy. Compared to what you're currently doing (setting ASIO Link Pro to use 44100 Hz), this is a cleaner approach because it will remove an unnecessary 44.1 → 48 sample rate conversion in the Windows audio engine.

Alternatively, you can try the other way around and make Plogue Bidule use 48000 Hz instead of 44100 Hz.

[Enaphets]

Changing my Roland Rubix to default 44100 does work! I see it was set at 48000.
The intriguing thing though is i didn't have to do that before,i was using FLASIO "fruity loop" and had nothing to adjust.
But no big deal,i will use what you suggested.

Thanks for the help.
By the way FlexAsio seems to be much more efficient for me in my setup than FLAsio...i have a somewhat complex setup,lots of inputs,outputs and 3 Bidule in serial...i have way less glitches with your driver.

Keep up the good work!

[dechamps]

i was using FLASIO "fruity loop" and had nothing to adjust

I'm not familiar with FL Studio ASIO, but one explanation could simply be that you got lucky and 44.1 kHz just happens to be the initial sample rate that FL ASIO uses by default, regardless of what the Windows audio device settings are set to. (Similar to FlexASIO's MME and DirectSound backends for example, which use 44.1 kHz as their initial sample rate regardless of Windows settings.)