alvr-org / ALVR

Stream VR games from your PC to your headset via Wi-Fi
MIT License
5.3k stars 475 forks source link

VB cable is never detected for mic use #1699

Closed Josh65-2201 closed 1 year ago

Josh65-2201 commented 1 year ago

Description

When using v20 and selecting microphone to automatic it will never connect as it says it can't find VB cable. It is installed and worked on v19

General Troubleshooting

Environment

Hardware

Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload

CPU: AMD Ryzen 5 2600

GPU: EVGA RTX 3060 12GB

GPU Driver Version: 531.68

Audio:

Installation

ALVR Version: 20.1.0

ALVR Settings File: session.txt

SteamVR Version: 1.26.3

Install Type:

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions): Windows 11 build 22621.1848

Vixea commented 1 year ago

Try manually selecting what virtual driver you use

Josh65-2201 commented 1 year ago

It says it cant find the device image

This is what I have it set to find image

This is what it's named as in Windows image

Vixea commented 1 year ago

Reset back to default and try all the drop downs in devices

Vixea commented 1 year ago

(the name field)

Vixea commented 1 year ago

Oh you're not even looking at the right setting

Vixea commented 1 year ago

That's for Linux my guy

Vixea commented 1 year ago

So disable it and scroll all the way to the top and look carefully for the first microphone also issue reports aren't for support they are for issues always ask in the discord or matrix to make sure it's actually an issue before making an issue this would've been solved quicker if you did

Josh65-2201 commented 1 year ago

Alright, the top mic option doesn't change anything, Setting it to VB cable or automatic still has the cant find VB cable issue.

Vixea commented 1 year ago

Did you make sure the driver installed correctly and is currently running

Josh65-2201 commented 1 year ago

Yes and I have tried reinstalling VB cable. Other programs can use the device it makes.

Josh65-2201 commented 1 year ago

I've also join the discord if you want to continue there

Vixea commented 1 year ago

Yes let's do that

Vixea commented 1 year ago

For anyone in the future who happens to run into this it was because the user was likely following Linux instructions DO NOT FOLLOW THEM if you're on windows, do NOT rename the driver's name it uses