Skip to main content
Nalin
Up and Coming
November 19, 2019
Solved

No audio when using Oculus Link

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.
  1. On your keyboard, press Win+X > Select "Device Manager"
  2. Open up the "Sound, video and game controllers" node.
  3. Right click the NVIDIA High Definition Audio driver and choose "Uninstall device".

    This topic has been closed for replies.
    TheLegend271265668
    TheLegend271265668Answer
    Honored Contributor
    February 14, 2024

    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
    View in thread

    116 replies

    Show previous replies
    Replect
    Participant
    February 1, 2020
    Well, the Bluetooth solution isn't that great. I was hoping the latest Bluetooth technology would have tolerable latency... but nooo, it feels like a good second delay, which might be better than no sound, but certainly isn't good either. Damn it!

    EDIT: Well, I bought another Bluetooth earbuds with aptx feature and a fitting adapter and this indeed is without (or if with barely recognizable) audio latency. The sound quality for music and videos is good, but in-game while latency free the sound is partially odd and left/right stereo recognition is weird after a first test, but well, still better than no sound or like the other one with an obvious audio latency... it has to be enough until Link hopefully does work properly for me.

    EDIT 2: I realize that the earbuds probably only support aptx, not aptx LL necessarily. At least that causes the bad audio quality. With good and proper stereo audio, I get the bad latency again. Hmpf...

    EDIT 3: Ordered an actual wireless headset with 2.4Ghz instead of that disappointing Bluetooth stuff... I'm just worried that such a proper headset won't fit properly and comfortable while wearing the Quest...
     
    Strongit
    Honored Contributor
    February 3, 2020
    I just got an email from support about some possible solutions I haven't tried yet.  It involves updating my windows build and changing around some USB drivers so I'll give it a go and let you know what happens. Even if it works for me it may not work for you; they said the solution was based on my own log files.  I'll keep you posted.

    EDIT: still didn't work. I updated to windows 10 version 1909 and uninstalled all my USB controller drivers. At first I had an exclamation mark next to a generic headset in device manager but uninstalling it and restarting fixed that part. Still no device audio.  I'm running full diagnostics and will try a couple other things since I'm on the newer build of windows before contacting support again.

    EDIT2: Nothing, reinstalled a whole bunch of device drivers and the oculus software a few times.  Sent another message to support with my results.  On the bright side I'm getting a whole different batch of errors in the diagnostics so even though it's still not working the back end is doing something completely different.
    Quest 1, i5-8600K at 4.7 GHz, eVGA 1080 ti FTW3, Gigabyte Z370 AORUS Ultra Gaming, 16 GB 3200 MHz
    Strongit
    Honored Contributor
    February 7, 2020
    Heard back from support and they told me to wait for the version 13 update.  Just got it on my headset less than an hour ago so I'm just waiting on the desktop software to update now.  As always I will report what happens when it's updated.
    Quest 1, i5-8600K at 4.7 GHz, eVGA 1080 ti FTW3, Gigabyte Z370 AORUS Ultra Gaming, 16 GB 3200 MHz
    Replect
    Participant
    February 7, 2020
    Yeah, they got back to me as well asking if I could try version 13 update... I've responded already with what it does including a log file... As mentioned in another thread. Now not just audio doesn't work, like many others all I get is a black screen for a few seconds and then it sends me back to Quest Home... soo, no audio, no video, no nothing at this point. Not quite the direction I'd like it to go.
    jc3113
    New Participant
    February 7, 2020
    The same, after updating v13, Link is unable to use. I had a black screen then kicked back to quest library.
    jc3113
    New Participant
    February 8, 2020
    Thanks a lot!!! Finally we have a solution!!!
    Replect
    Participant
    February 8, 2020
    Just wanted to comment and link to that fix... It indeed works.
    Even my original problem of not getting any audio out of the Quest with Link is fixed with v13 Quest and v14 PTC on PC. Everything is working based on the 1 hour session I just had!

    Strongit
    Honored Contributor
    February 8, 2020
    That fix worked for me as well, I'm on 13/14.  Someone should create a sticky for that.  I was back and forth with support for three weeks.

    However that fix reeks of sloppy coding.  I'm not a programmer in any sense beyond a high school course and one or two crash courses in college but even I know that when you reference a device in a driver you use the device ID and not the user changeable description from the sound settings.  I made a final comment in my support ticket asking them to forward the note on to the developers to change that; it may not get that far though.
    Quest 1, i5-8600K at 4.7 GHz, eVGA 1080 ti FTW3, Gigabyte Z370 AORUS Ultra Gaming, 16 GB 3200 MHz
    Anonymous
    May 15, 2020
    I just had this problem too. I haven't read the whole thread.

    My issue was that the Headphones (subtext "Oculus Virtual Audio Device") somehow had been disabled. On Windows 10 it's reachable under "Sound Settings" (right-click on loudspeaker icon in system tray works), then click "Sound Control Panel" from the right-hand side under "Related settings".

    Solution was simply to enable that device. Using Oculus Quest btw, via a Link cable (not the official one).


    Sidenote:
    After reading the reddit fix a few posts up from "lenne0815", it seems relevant, though different from my issue. I had norwegian Windows but I changed it a few days back, before installing any VR stuff (I'm pretty new to Oculus Link stuff). Anyway, my headphones device is still named in norwegian (Some devices - not all ofc - in Sound Settings are still in Norwegian somehow. Even after "changing" the UI language. Except the tab's of that window, which is in English). And it still worked btw after enabling it, I didn't have to rename it to the English "Headphones". So I'm leaving it as-is for now.

    Show more replies
    Terms & ConditionsAccessibility statement