Creating a context causes ma_device_init to fail on Windows/Wine #970

midn1 · 2025-03-20T19:26:21Z

midn1
Mar 20, 2025

If I take the "Simple Playback Sine" example on the website it works correctly. But if I insert

ma_context ctx;
assert(ma_context_init(NULL, 0, NULL, &ctx) == MA_SUCCESS);

and replace the first arg to ma_device_init with &ctx then the program prints "Failed to open playback device."

I don't know if this is a Windows problem or specifically with Wine. The same program works on Linux.

I technically do not need a custom context, but I found this strange nonetheless. Should I also iterate over the backends one-by-one until I find one that works, like ma_device_init_ex does?

midn1 · 2025-03-22T07:19:30Z

midn1
Mar 22, 2025
Author

As a crap workaround I init a device with no set context, extract the device's context (pContext) from the struct and set isOwnerOfContext to MA_FALSE.

1 reply

midn1 Mar 22, 2025
Author

OK, initializing a second device with the first's context doesn't work:

0009:err:pulse:pulse_spec_from_waveformat Invalid channel mask: 1/2 and 4(4)
0009:err:pulse:pulse_spec_from_waveformat Invalid format! Channel spec valid: 0, format: 3

From what I understand this is probably Wine having trouble with PulseAudio.

mackron · 2025-03-23T06:46:59Z

mackron
Mar 23, 2025
Maintainer

When you pass in NULL for the context to ma_device_init(), it will cycle through backends like you mentioned. When you initialize a context, it will use the first backend that works for initializing the context. After the context is initialized, it's tied to only a single backend and no further fallback logic will be used. What I suspect is happening is your context is initializing successfully for the WASAPI backend, but then for some reason device initialization fails.

As an experiment, what happens if you define MA_NO_WASAPI? This will make it so DirectSound is used as the default Windows backend.

Also, are you able to define MA_DEBUG_OUTPUT and post the output here? It'll output some messages to stdout and should provide some details on the initialization process.

0 replies

midn1 · 2025-03-30T12:42:33Z

midn1
Mar 30, 2025
Author

Sorry for the late reply. Disabling WASAPI works.

The debug log doesn't appear to have anything useful:

001e:err:wineusb:DriverEntry Failed to initialize Unix library, status 0xc0000135.
001e:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000135
0016:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\nsiproxy": c0000135
0016:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\NDIS": 00000001
DEBUG: Loading library: user32.dll
DEBUG: Loading symbol: GetForegroundWindow
DEBUG: Loading symbol: GetDesktopWindow
DEBUG: Loading library: advapi32.dll
DEBUG: Loading symbol: RegOpenKeyExA
DEBUG: Loading symbol: RegCloseKey
DEBUG: Loading symbol: RegQueryValueExA
DEBUG: Loading library: ole32.dll
DEBUG: Loading symbol: CoInitialize
DEBUG: Loading symbol: CoInitializeEx
DEBUG: Loading symbol: CoUninitialize
DEBUG: Loading symbol: CoCreateInstance
DEBUG: Loading symbol: CoTaskMemFree
DEBUG: Loading symbol: PropVariantClear
DEBUG: Loading symbol: StringFromGUID2
DEBUG: Attempting to initialize WASAPI backend...
DEBUG: Loading library: kernel32.dll
DEBUG: Loading symbol: VerifyVersionInfoW
DEBUG: Loading symbol: VerSetConditionMask
DEBUG: Loading library: avrt.dll
DEBUG: Loading symbol: AvSetMmThreadCharacteristicsA
DEBUG: Loading symbol: AvRevertMmThreadCharacteristics
DEBUG: System Architecture:
DEBUG:   Endian: LE
DEBUG:   SSE2:   YES
DEBUG:   AVX2:   NO
DEBUG:   NEON:   NO
ERROR: [WASAPI] Failed to initialize device.

The first 4 lines are from Wine and don't have anything to do with miniaudio.

2 replies

mackron Mar 31, 2025
Maintainer

This means IAudioClient_Initialize() is failing. This is the main initialization routine so if that's failing I don't think there's a whole lot miniaudio can do about that. It would be nice to have it "just work" with Wine though.

If you're at all in a position where you can debug it, doing a searching for that [WASAPI] Failed to initialize device. error string and then putting a breakpoint on there would be useful. The hr variable might give some intelligence. The only think I can think of is maybe the bufferDuration variable is bad, but without more information I couldn't tell you for sure.

midn1 Apr 1, 2025
Author

shareMode: 0
streamFlags: 0x88040000
bufferDuration: 300000

From the MA_WAVEFORMATEX structure:

wFormatTag: 65534 (WAVE_FORMAT_EXTENSIBLE)
nChannels: 2
nSamplesPerSec: 48000
nAvgBytesPerSec: 384000
nBlockAlign: 8
wBitsPerSample: 32
cbSize: 22

The error from Initialize is 0x80070057 (invalid argument), but it all seems pretty normal. I guess this just a Wine issue, so I'll close this.

midn1 · 2025-04-02T10:19:57Z

midn1
Apr 2, 2025
Author

For the record, I've found a Linux system where this bug doesn't occur, so this is even worse.

0 replies

midn1 · 2025-04-09T19:29:02Z

midn1
Apr 9, 2025
Author

WINEDLLOVERRIDES="winepulse.drv=" may also help, for future reference.

0 replies

Creating a context causes ma_device_init to fail on Windows/Wine #970

Uh oh!

Uh oh!

midn1 Mar 20, 2025

Replies: 5 comments · 3 replies

Uh oh!

midn1 Mar 22, 2025 Author

Uh oh!

midn1 Mar 22, 2025 Author

Uh oh!

mackron Mar 23, 2025 Maintainer

Uh oh!

midn1 Mar 30, 2025 Author

Uh oh!

mackron Mar 31, 2025 Maintainer

Uh oh!

Uh oh!

midn1 Apr 1, 2025 Author

Uh oh!

midn1 Apr 2, 2025 Author

Uh oh!

midn1 Apr 9, 2025 Author

midn1
Mar 20, 2025

Replies: 5 comments 3 replies

midn1
Mar 22, 2025
Author

midn1 Mar 22, 2025
Author

mackron
Mar 23, 2025
Maintainer

midn1
Mar 30, 2025
Author

mackron Mar 31, 2025
Maintainer

midn1 Apr 1, 2025
Author

midn1
Apr 2, 2025
Author

midn1
Apr 9, 2025
Author