Incompatibility with certain VoiceMeeter configurations #5
Description
A user ran into an issue where EarPerkOSC isn't able to listen to the audio device when VoiceMeeter is running. I've created a test build that works on my system, and the default VoiceMeeter configuration also works for me, but doesn't for his configuration. The error in the logs will be something like:
2025-08-31 22:23:11.022 [ERROR] Failed to initialize audio client: 0x8889000A
2025-08-31 22:23:11.022 [ERROR] Failed to initialize audio processor
2025-08-31 22:23:11.022 [ERROR] Failed to initialize application
2025-08-31 22:23:21.690 [ERROR] Failed to initialize audio client: 0x8889000A
2025-08-31 22:23:21.690 [ERROR] Failed to initialize audio processor
and the current build (1.2 or 1.3 pre-release) won't start. The testing build of 1.3 (not yet uploaded) will start and show a dropdown of available devices, but still not allow you to listen to the proper device.
The current workaround is to not use VoiceMeeter if it's proving to not work with EarPerkOSC, but it should be possible for me to modify the application to listen to the VoiceMeeter output devices rather than attempt to grab an exclusive lock as a loopback device.