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.29k stars 70 forks source link

FlexASIO opening issue. #223

Closed Rexoyy closed 1 month ago

Rexoyy commented 2 months ago

I have FlexASIO downloaded with its GUI and the dotnet program, when I try to open it on Ableton Live 11, I'm told that it has failed to open the device, I have read the FAQ and looked at how to make a log etc, but when i restart my DAW and try to reopen FlexASIO, it gives me nothing in the log file, help?

Rexoyy commented 2 months ago

FlexASIO.log

I found the log problem, what seems to be the issue?

Rexoyy commented 2 months ago

image

It's telling me it can't find my output, even though its spelt correctly and written exactly how it's read in log

image

dechamps commented 2 months ago

FlexASIO.log

I found the log problem, what seems to be the issue?

2024-04-16T12:47:47.5678497+01:00 9244 21992 Selecting input device
2024-04-16T12:47:47.5678672+01:00 9244 21992 Selecting PortAudio device with host API index 2, minimum channel counts: 1 input, 0 output
2024-04-16T12:47:47.5678890+01:00 9244 21992 Searching for a PortAudio device named `Microphone (Analouge 1 + 2 (Focusrite USB A Wave)`
2024-04-16T12:47:47.5679088+01:00 9244 21992 No matching devices found

The error is correct: there is no device named Microphone (Analouge 1 + 2 (Focusrite USB A Wave) under Host API 2 (WASAPI backend). I guess you meant Analogue 1 + 2 (Focusrite USB Audio):

2024-04-16T12:47:47.5671936+01:00 9244 21992 Found device: PortAudio device index 41 (name: 'Analogue 1 + 2 (Focusrite USB Audio)', host API: 2, default sample rate: 48000, max input channels: 2, max output channels: 0, input latency: 0.003 (low) 0.01 (high), output latency: 0 (low) 0 (high))

image

It's telling me it can't find my output, even though its spelt correctly and written exactly how it's read in log

image

Your screenshots refer to a portion of the logfile that is not included in your earlier attachment, so it's difficult for me to comment. That said, I suspect the problem is you seem to be looking at devices under Host API 3 (WDM-KS), whereas you are presumably still on Host API 2 (WASAPI). If you look at devices for Host API 2 you will find:

2024-04-16T12:47:47.5670390+01:00 9244 21992 Found device: PortAudio device index 35 (name: 'Speakers (2- SteelSeries Arctis 1 Wireless)', host API: 2, default sample rate: 48000, max input channels: 0, max output channels: 2, input latency: 0 (low) 0 (high), output latency: 0.003 (low) 0.01 (high))

Which indicates the proper spelling for that device under WASAPI is Speakers (2- SteelSeries Arctis 1 Wireless), not Speakers (SteelSeries Arctis 1 Wireless).

Note the PortAudioDevices tool will list device names and the backend they are under in a more readable way than the log, so it may be easier to use that instead.