-
Notifications
You must be signed in to change notification settings - Fork 78
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
Failed FlexASIOTest, failed to open in ableton #228
Comments
Perhaps this can ease some analysis, perhaps not, but here are some lines of the logs which seem relevant: Using the full toml generated with FlexASIOGUI:
It's finding the devices:
Errors found in the end:
|
I Noticed issue #94 had the same error as me but I checked that the number of channels in my input is correct. |
using "KoordASIO" worked. I figure this is relevant since it uses FlexASIO. Let me know if there is any way to get logs from KoordASIO which may help here |
Mmm yeah I'm not sure what's going on here. DirectSound fails to start with a cryptic error:
As for WASAPI, it fails with
There is nothing "weird" about the devices:
It is extremely surprising that KoordASIO would work where FlexASIO would fail, on two different backends no less, including DirectSound (which should always work). Does it work if you try to use different devices? E.g. if you just use an empty configuration? |
Hi, I installed FlexASIO GUI to make the device identification easier. Selecting the "FlexASIO" audio device in ableton 10 gives the error "failed to open the audio device "FlexASIO.""
I checked some of the other posts, so I attempted for example to edit the .TOML file to just
And this allows ableton to select the device, but it says that the audio engine is still off.
I ran the FlexASIOTest just to check and indeed it also fails. Any ideas?
FlexASIOTest console output.txt
FlexASIO_trying to open in ableton.log
Here I attach the console log of the test result and the logs i get while trying to open in ableton. Thanks a lot in advance!
The text was updated successfully, but these errors were encountered: