"The audio engine could not be initialized" error despite having audio drivers installed

Question

"The audio engine could not be initialized" error despite having audio drivers installed

Fukumeru opened this issue a year ago · 9 comments

I've tried running abaddon's latest release, but it can't get past startup while getting "The audio engine could not be initialized" error.
This issue seems to be related to #203, except I have correct audio drivers installed, and these drivers work in other apps.
Here's what is printed in console:

[2023-10-20 10:45:14.692] [audio] [info] Audio backend: WASAPI
[2023-10-20 10:45:14.789] [audio] [info] using Headphones (Realtek(R) Audio) as playback device
[2023-10-20 10:45:14.801] [audio] [error] failed to initialize capture device

Answer 1 · 2023-10-20T04:46:47.000Z

does it work on latest build from master? i should make a new release lol

Answer 2 · 2023-12-15T07:25:03.000Z

Using build-windows-msys2-MinSizeRel, 04-12-2023. Having same issue.

Answer 3 · 2023-12-16T01:02:23.000Z

Using build-windows-msys2-MinSizeRel, 04-12-2023. Having same issue.

what do you see in the console?

Answer 4 · 2023-12-16T12:32:19.000Z

[2023-12-16 07:31:32.837] [audio] [info] Audio backend: WASAPI
[2023-12-16 07:31:33.214] [audio] [info] using Speakers (Realtek High Definition Audio) as playback device
[2023-12-16 07:31:33.247] [audio] [error] failed to initialize capture device

Answer 5 · 2023-12-17T06:23:56.000Z

and im correct in assuming you do have a functioning input device? ive just pushed some stuff to master that should make the logging a bit more helpful, so itd be useful if you could grab the latest master build and run set SPDLOG_LEVEL=miniaudio=trace,audio=trace and abaddon.exe via command line, then send the output here

audio engine initialization failure is also non-fatal now so you can at least hear/use text even if your input device isnt working (or perhaps try picking another one via the GUI which should reinitialize it)

Answer 6 · 2023-12-17T20:09:26.000Z

set SPDLOG_LEVEL=miniaudio=trace,audio=trace

Is this a command line option or something that needs to be added somewhere while building the binaries?

Answer 7 · 2023-12-17T20:17:50.000Z

its an environment variable not quite a command line option, but if you run that line in the command prompt and then run abaddon also via command prompt it will give more verbose logs

Answer 8 · 2024-01-31T16:01:07.000Z

and im correct in assuming you do have a functioning input device? ive just pushed some stuff to master that should make the logging a bit more helpful, so itd be useful if you could grab the latest master build and run set SPDLOG_LEVEL=miniaudio=trace,audio=trace and abaddon.exe via command line, then send the output here

audio engine initialization failure is also non-fatal now so you can at least hear/use text even if your input device isnt working (or perhaps try picking another one via the GUI which should reinitialize it)

i do not have a functioning mic on this computer but i would still like to use abaddon, for eg text messing (i don't use discord for voice). is this not possible?

Answer 9 · 2024-01-31T19:07:53.000Z

i do not have a functioning mic on this computer but i would still like to use abaddon, for eg text messing (i don't use discord for voice). is this not possible?

it should work fine without a microphone. do you get any issues when using the latest master build?