OS Error 11 / os error 10053: Enabling Headset Microphone causes os error 10053

[CamachoJoseph]

Description

Virtual cable in use: VAC lite v470 (installed via link from ALVR v20.14.1)
Headset in use: Meta Quest 2

Issue: ALVR will operate as expected when option "Headset Speaker" is enabled (system default is not Line 1 created by VAC); headset will connect, ALVR will load into SteamVR, games will open but microphone on Quest 2 will not be functional. When option "Headset Microphone" (system default is not Line 1 created VAC) is enabled and set to "Automatic" or "Virtual Audio Cable" or is set to "Custom" with Sink as "Line 1" or "Virtual Audio Cable" and Source is set to "Virtual Audio Cable" and the connection to the Quest 2 is initiated then connection will fail, disconnecting and reconnecting to SteamVR and headset. In the headset the error "os error 11" is given, instructing user to look at ALVR which which gives the error "os error 10053" (An established connection was aborted by the software in your host machine.) When "Headset Microphone" is disabled and SteamVR is restarted then ALVR will return to a usable state and the connection will operate as expected. Log attached below:

General Troubleshooting

• I carefully followed the instructions in the README and successfully completed the setup wizard
• I read the ALVR GitHub Wiki

Installation

ALVR Version: v20.14.1

ALVR Settings File: session.json

SteamVR Version: v2.11.2

Install Type:

• Packaged (exe, deb, rpm, etc)
• Portable (zip)
• Source

[The-personified-devil]

Hi, I have a suspicion what the reason could be, could you please provide us with the log when you have the mic disabled, so I can check whether it's correct?

[CamachoJoseph]

Hi, I have a suspicion what the reason could be, could you please provide us with the log when you have the mic disabled, so I can check whether it's correct?

Here you are, this is taken just as the headset connects with ALVR and boots me into the Steam VR environment

[The-personified-devil]

Since this problem is kinda hard to reproduce I made a build (last version had a bug, fixed now) (automatically generated from #2938) that tries to patch out what I think is causing the issue, so if you could download nightly client and run it and attempt to see if it works, that'd be great. It includes a disable_loopback_detection setting under the game audio settings (this is a debug hack, so it's kinda scuffed), so if it works whilst that's on and not when it's off that'd essentially confirm what the issue is so we can fix it.

If setting up a nightly client and everything is too much of a hassle, that's fine too, but if it's not too much trouble trying this out be great. Btw sorry that the built is double zipped, I had to newly configure the infrastructure for making builds from PRs, but I really don't like just sending people an executable that I compiled myself (from a safety standpoint).

[CamachoJoseph]

I am not sure if I did this incorrectly, I didn't find anything in the client with disable_loopback_detection but attempted to start it with Mic turned on and it didn't connect. Here's the log and the audio settings in the client using your build. If I missed something or misunderstood just let me know.

[The-personified-devil]

Are you sure you're running a nightly client? The normal quest store one won't work, you need to use the launcher to install it to the device. The setting is under "Headset speaker" btw, it's labeled game_audio in the code so that was quite confusing from me, but it's also enabled by default.

[CamachoJoseph]

It boots directly into the streamer dashboard leaving me unable to use the APK install function of the launcher is there a way around that? It appears that everything is in place in this version other than that currently the APK is my main blocker.

[The-personified-devil]

You just need to use the normal launcher from github releases, the build is only the streamer.

[CamachoJoseph]

It seems the only way this will work on my end would be through sideloading it, unfortunately a developer account is not feasible right now since I am dealing with issues that prevent me from signing up for one to enable the ability to sideload the apk.

[The-personified-devil]

I'll see if I can cook you a version up that's compatible with the normal quest client.

[The-personified-devil]

Aight, I have a new build from #2940, this one should be compatible with the stable quest client, so no side-loading required.

[CamachoJoseph]

Failed:

but without the mic it passed:

[The-personified-devil]

Damn, that's unexpected, can you try it again but under the Extra tab enable the debug options shown here, I'm just trying to get any information at this point, because I'm really confused.
You will likely need to copy-paste the logs instead of screenshots because they'll probably be pretty long.

[CamachoJoseph]

This thing hates me!

session_log.txt

[The-personified-devil]

I don't see an actual connection attempt in there, maybe disable the server core one because it's too spammy and try again?