Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After Recent Win 11 Pro Update FlexASIO Incompatibility #247

Open
Muiren opened this issue Oct 21, 2024 · 5 comments
Open

After Recent Win 11 Pro Update FlexASIO Incompatibility #247

Muiren opened this issue Oct 21, 2024 · 5 comments

Comments

@Muiren
Copy link

Muiren commented Oct 21, 2024

FlexASIO stopped working after the 2024-10 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5044285)
I've tried completely uninstalling, clearing the registry, and reinstalling to no good effect.
It's impacted Vital Audio in Reaper, Ableton, and Standalone as well as all Arturia Software.
Any suggestions to further diagnose the cause?

This isn't a burning issue since I've fallen back on using Arturia's ASIO Drivers which were not affected, but I am curious if anyone else has had a similar experience and found a solution.

@dechamps
Copy link
Owner

This seems... unlikely. Can you share a log?

@Muiren
Copy link
Author

Muiren commented Oct 21, 2024

I already uninstalled it, but let me get some sleep and I'll reinstall. It the problem reoccurs, then I'll copy the log and share it.
Would be great if this was just some coniguration issue I did without realizing it.

@Muiren
Copy link
Author

Muiren commented Oct 26, 2024

This seems... unlikely. Can you share a log?
I copied two log files. The one is attempting to play a few notes in Vital Synth and the other recorded using FlexASIOTest.exe

The DirectSound default no longer works, but if I switch the default to Windows WASAPI, everything starts working again.
FlexASIO_FlexASIOTest-Results.log
FlexASIO_Vital-Synth-Results.log

@dechamps
Copy link
Owner

Your configuration contains:

bufferSizeSamples = 20

Which is nonsensical - that's 0.5 ms at 44100 Hz, which is completely unrealistic. This likely explains why some backends don't work (the backends that do work implicitly fall back to a larger buffer internally, but that's still hugely inefficient as that leads to many buffer switches per internal buffer).

I would suggest removing that line and try again.

@Muiren
Copy link
Author

Muiren commented Oct 26, 2024

Switching back to Windows DirectSound, I tested at 256, then 512 buffer and dialed down the sample rate a little until I found a compromise that works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants