I have no audio on my Quest headset when using Oculus Link. These are all the things I have tried to resolve the issue:Reboot PC and/or Quest and plugged things back in in many different orders.Restarted the Oculus service.Tried different USB ports.Tried different USB cables.Tried both an active and a passive extender.Tried throwing a USB 3 hub into the mix just because, both as the first part of the chain and as the second part.Tried with headphones plugged into the Quest and with them removed.Tried toggling all the options related to sound that I could find within the software (Devices > Quest and Touch, all those sound options).Repaired / reinstalled Oculus software.Uninstalled Virtual Desktop Streamer app and its audio driver.Changed my desktop speakers from 5.1 to stereo.Attempted setting every single audio output device as default in Windows.Plugged in my CV1, went through the setup, and then tried piping audio through the Oculus Rift Headphones audio output adapter.Reinstalled oculus-driver.exe.Opened a ticket with Oculus Support (they told me they won't support beta software, lol)Is there anybody with the same issue who found a solution? Or at this point is my only bet to wait a year until it stops being beta and Oculus Support actually tries to help?EDIT: I finally got it working after uninstalling the NVIDIA HD Audio driver.On your keyboard, press Win+X > Select "Device Manager"Open up the "Sound, video and game controllers" node.Right click the NVIDIA High Definition Audio driver and choose "Uninstall device".

Up and Coming

Solved

No audio when using Oculus Link

116 replies
177655 views

I have no audio on my Quest headset when using Oculus Link. These are all the things I have tried to resolve the issue:

Reboot PC and/or Quest and plugged things back in in many different orders.
Restarted the Oculus service.
Tried different USB ports.
Tried different USB cables.
Tried both an active and a passive extender.
Tried throwing a USB 3 hub into the mix just because, both as the first part of the chain and as the second part.
Tried with headphones plugged into the Quest and with them removed.
Tried toggling all the options related to sound that I could find within the software (Devices > Quest and Touch, all those sound options).
Repaired / reinstalled Oculus software.
Uninstalled Virtual Desktop Streamer app and its audio driver.
Changed my desktop speakers from 5.1 to stereo.
Attempted setting every single audio output device as default in Windows.
Plugged in my CV1, went through the setup, and then tried piping audio through the Oculus Rift Headphones audio output adapter.
Reinstalled oculus-driver.exe.
Opened a ticket with Oculus Support (they told me they won't support beta software, lol)

Is there anybody with the same issue who found a solution? Or at this point is my only bet to wait a year until it stops being beta and Oculus Support actually tries to help?

EDIT: I finally got it working after uninstalling the NVIDIA HD Audio driver.

On your keyboard, press Win+X > Select "Device Manager"
Open up the "Sound, video and game controllers" node.
Right click the NVIDIA High Definition Audio driver and choose "Uninstall device".

This topic has been closed for replies.

TheLegend271265668Answer

Honored Contributor

Hey everyone! It looks like this thread is still getting some traffic from the occasional user, so I'm going to go ahead and lock it. This looks like an issue that was present in the early days—dating back to V13. To avoid floating old threads with outdated information, I highly recommend creating a new thread detailing the new issue, so that our teams can monitor new emerging issues caused by recent releases—or other leading causes. I also recommend taking a look with the native search function to find a more recent existing thread with the same issue.

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

Show previous replies

R

Replect

Participant

Strongit said:

I went through the logs myself and the error that kept coming up was about a non-existent USB device. Seems like a driver or software issue with link, not a hardware issue thankfully.

Do you mind sharing what log file exactly it was you found that error in? And what was the error text you've found?

I didn't see anything after a first look and probably I'm just missing something.

Thanks a lot!

S

Strongit

Honored Contributor

Replect said:

Strongit said:

I went through the logs myself and the error that kept coming up was about a non-existent USB device. Seems like a driver or software issue with link, not a hardware issue thankfully.

Do you mind sharing what log file exactly it was you found that error in? And what was the error text you've found?
I didn't see anything after a first look and probably I'm just missing something.

Thanks a lot!

These are the instructions given to me by support to generate the logs:

If the issue persists, please be so kind as to send us your Oculus log files, making sure your Quest is plugged into your computer:

Open the Run window (Windows key + R).
Enter and run: C:\Program Files\Oculus\Support\oculus-diagnostics\OculusLogGatherer.exe
- The above link is the default directory. Bear in mind that if you installed Oculus Home to another drive you will need to update the command with the correct file path.
Select the checkbox next to ‘Full logs’.
Select "1 day" from the "Collect last" drop down list.
Wait for the log collection to finish. This can take some time to complete.
The program will automatically generate a zip file containing your logs, which will be saved to your desktop automatically.
Attach the newly created zip file to your next support response.

If you open the zip file afterwards you want to look for the file that has AutoAnalysis at the beginning. It goes through the logs and finds all of the errors then compiles it into one file. The errors I keep seeing in my logs are:

{!ERROR!} [xrstreaming] failed to open device vid=2833, class=ff, subclass=89: (10) no device
{!ERROR!} [xrstreaming] WinUsb_ReadPipe(handle:-787940528, ep:129, len:1024) failed: (433) A device which does not exist was specified.
{!ERROR!} [xrstreaming] WinUsb_WritePipe(handle:-787940528, ep:129, len:1024) failed: (433) A device which does not exist was specified.

It points to it being a driver/software issue since I've tried three USB cables and different USB ports.

Quest 1, i5-8600K at 4.7 GHz, eVGA 1080 ti FTW3, Gigabyte Z370 AORUS Ultra Gaming, 16 GB 3200 MHz

R

Replect

Participant

Thanks a lot! Didn't recognize that AutoAnalysis file. I've plenty of errors in there, including those you've pointed out (just with German description text partially though):

{!ERROR!} [xrstreaming] failed to open device vid=2833, class=ff, subclass=89: (10) no device

{!ERROR!} [xrstreaming] WinUsb_WritePipe(handle:-51464032, ep:1, len:1024) failed: (433) Ein nicht vorhandenes Ger�t wurde angegen

I assume some errors though, probably including those above are rather just showing up if the Oculus Software is running and the headset just isn't connected? Or if you pull the cable while the software is running, so probably nothing necessarily related to the audio issues...

I also see the following errors though, which based on the timestamps I think were errors while I actually wear the headset with active link connection and might be related to the audio issue:

{!ERROR!} [xrstreaming] WinUsb_Initialize(4124) failed: (8) Zur Verarbeitung dieses Befehls sind nicht gen�gend Speicherressourcen verf�gbar.

{!ERROR!} [xrstreaming] couldn't open device USB\VID_2833&PID_0186\1PASH9B1A59414 (path: \\?\usb#vid_2833&pid_0186#1pash9b1a59414#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
{!ERROR!} [RemoteHeadset] matchCount != kVirtualDeviceCount
{!ERROR!} [xrstreaming] AudioCapture: Unsupported loopback capture device format
{!ERROR!} [xrstreaming] AudioCapture: initializeWasapi() failed: 0x80004005
{!ERROR!} [xrstreaming] RemoteHeadphones::initialize: AudioCapture::create() failed
{!ERROR!} [xrstreaming] OculusVadRemoteHeadphonesServerPipe::workThread: GetOverlappedResult() failed: (109) Die Pipe wurde beendet.

The USB-device mentioned in these errors is the following:
Device ID: USB\VID_2833&PID_0186\1PASH9B1A59414
   Oculus Device: True
   Connected to USB 3 Port: True
   PnP Device ID: USB\VID_2833&PID_0186\1PASH9B1A59414
   PnP Class: USB
   Description: USB-Verbundgerät
   Manufacturer: (Standard-USB-Hostcontroller)
   ClassGuid: {36fc9e60-c465-11cf-8056-444553540000}
   HardwareID: USB\VID_2833&PID_0186&REV_0404; USB\VID_2833&PID_0186;
   Related: [usbccgp]; [DESKTOP-xxxxxxx]; PCI\VEN_10DE&DEV_1ADA&SUBSYS_37321462&REV_A1\4&15001D53&0&0208[NVIDIA USB 3.10 eXtensible-Hostcontroller – 1.10 (Microsoft)]; PNP_BUS_0[Bus]; ; USB\VID_2833&PID_0186\1PASH9B1A59414[USB-Verbundgerät];
   Status: OK
   Caption: USB-Verbundgerät
   Name: USB-Verbundgerät
   SystemName: DESKTOP-xxxxxxx
   Service: usbccgp
   Last Error Code: 0
   Error Description:

That might be my USB-C port of the RTX 2070 I used during the latest tests with Link. Unfortunately I don't have any idea what to work out of that to get it fixed... I've also sent a support ticket to hopefully get it sorted out.

R

Replect

Participant

I got response from Oculus, unfortunately so far no solution to fix the issue, just 2 things they saw:

"From the log files I saw 2 things your processor is not recommended to
run Link, and also the USB I see it plugged into shows as unknown, if
possible try attaching it to the Intel one and see, although I see you
tried multiple USB ports.

Considering you need recommended specifications just to run the Link I
am surprised it is working, let me know if plugging into the Intel
controller works."

While I've tested already all USB ports, I gave it another shot... unfortunately with the same results as before.

Beside that, I wasn't aware of that my CPU isn't recommended for
Link and considering everything else runs flawless, VR games in general,
the video via Link... I'm surprised that is actually a thing.

What
is it my CPU doesn't support that everything is running fine but audio
is not? I mean, this would be a real disappointment if the only solution
is a new CPU, because a new CPU will require a different socket, which
means I would also be forced to buy a new mainboard, which might also
force me to buy new memory, and all of a sudden I was required to buy
half of a new PC, just to get audio with Link. :-(

I've given response and hope the outcome is not that I would need to buy a new CPU to get Link working with audio.

S

Strongit

Honored Contributor

Replect said:

I got response from Oculus, unfortunately so far no solution to fix the issue, just 2 things they saw:
"From the log files I saw 2 things your processor is not recommended to
run Link, and also the USB I see it plugged into shows as unknown, if
possible try attaching it to the Intel one and see, although I see you
tried multiple USB ports.

Considering you need recommended specifications just to run the Link I
am surprised it is working, let me know if plugging into the Intel
controller works."

While I've tested already all USB ports, I gave it another shot... unfortunately with the same results as before.

Beside that, I wasn't aware of that my CPU isn't recommended for
Link and considering everything else runs flawless, VR games in general,
the video via Link... I'm surprised that is actually a thing.
What
is it my CPU doesn't support that everything is running fine but audio
is not? I mean, this would be a real disappointment if the only solution
is a new CPU, because a new CPU will require a different socket, which
means I would also be forced to buy a new mainboard, which might also
force me to buy new memory, and all of a sudden I was required to buy
half of a new PC, just to get audio with Link. :-(

I've given response and hope the outcome is not that I would need to buy a new CPU to get Link working with audio.

You've got more of a response than I have so far. I have an i5 8600k and a 1080 ti (had a 970 that died right in the middle of the currency mining boom and couldn't find any other model. $1500 later...) but haven't heard beyond that they were looking into the issue. Still just using headphones via two 3.5mm extensions for the time being. I'll keep posting updates on my situation when I either hear from them or try something else to fix the issue.

Quest 1, i5-8600K at 4.7 GHz, eVGA 1080 ti FTW3, Gigabyte Z370 AORUS Ultra Gaming, 16 GB 3200 MHz

A

Anonymous

I am on the same boat here.
Any idea of what broke? Because I had mic working on link before, it's not working now.
Is it an isolated case, does other users have their mic's working?
Or am I one of the unlucky ones?
If so I would consider buying a modmic. It's kind of a pain playing games like that, where you can't communicate.

R

Replect

Participant

Strongit said:

You've got more of a response than I have so far. I have an i5 8600k and a 1080 ti (had a 970 that died right in the middle of the currency mining boom and couldn't find any other model. $1500 later...) but haven't heard beyond that they were looking into the issue. Still just using headphones via two 3.5mm extensions for the time being. I'll keep posting updates on my situation when I either hear from them or try something else to fix the issue.

Wonder why I got quicker response, though currently it's rather "standard" response and suggestions (which I understand them doing, there are certainly plenty who write to support while the solution is just around the corner). I got another response in regards to my worry with the CPU:

"I was not suggesting you purchase a new CPU or that it is the cause of
the audio issue, considering everything is working I doubt it would
cause the audio not to work.

I would just like to know if you have tried these steps:

...."

I was asked to check if the Quest is the selected audio source, that the sound of my computer is turned up and that there is no pending update within the Oculus PC software.
Again, I understand the initial suggestions to check for these (to me) common things before going any further, though with each response I'm getting more nervous about if there will be a solution to be found (for my issue). *keep fingers crossed*

S

Strongit

Honored Contributor

BlTEY said:

I am on the same boat here.
Any idea of what broke? Because I had mic working on link before, it's not working now.
Is it an isolated case, does other users have their mic's working?
Or am I one of the unlucky ones?
If so I would consider buying a modmic. It's kind of a pain playing games like that, where you can't communicate.

They disabled the mic in the most recent update, they're going to try to enable it again soon. I'm hoping the next update will also fix the audio passthrough issues we're having as well.

Quest 1, i5-8600K at 4.7 GHz, eVGA 1080 ti FTW3, Gigabyte Z370 AORUS Ultra Gaming, 16 GB 3200 MHz

R

Replect

Participant

I had another short conversation with the Oculus Support yesterday. They asked me about which cables I've tested and after I have given them that information (at least 3 cables, 2 Anker, 1 CableTex) and them probably seeing it's cables which should work just fine (and do based on other comments out there), they now asked to give them some time to further investigate and they hope to have information or an update in the next 3-4 business days (Mo to Fr).

In the meantime I've ordered a bluetooth 5.0 earbuds and usb adapter and hope this will work decent for the time being until there is (hopefully) a solution. It will be delivered today, so I might find out soon... *fingers crossed*

A

Anonymous

Screw this. I am getting a modmic.

Oculus, this is dissapointing, at least you could let us know what the issue is, it looks like even your support doesn't know what's going on and your team keep asking stupid questions, when in reality as people say here it was disabled in the software.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO