Forum Discussion

FinalYOSHI's avatar
FinalYOSHI
Honored Guest
2 years ago

Problem watching videos when connected to Bluetooth Audio?

Hello!

My headset self updated itself to v71 earlier this week and I typically use my Meta Quest 3 to watch YouTube/Netflix while my spouse is asleep next to me. I use bluetooth headphones to isolate the noise to myself. After the firmware update I noticed when watching video content through any of my installed browsers, the video will just be a stationary picture. I noticed if I disconnect the bluetooth headphones, the picture will begin to move or work  normally, then if reconnecting the bluetooth headphones, the video will start stuttering until it freezes.

I've tried resetting the headset and I've also tried updating to v72 PTC and the same issue persists. Has anyone had a similar issue?

 

Version 72.0.0.368.347.665705819

Runtime: 72.0.0.368.346.665705565

13 Replies

  • Same issue here with my Sony WF-1000XM4. I think it's since the v71 update. Weird is - playing games doesn't have the problem (yeah yeah, I know - huge latency is still there but at all - it works). YT app works well too.
    So the problem is only when watching some videos with the browser (any kind of browser).

    • FinalYOSHI's avatar
      FinalYOSHI
      Honored Guest

      I actually found the solution a while ago,

      the Quest 3 software has trouble processing high quality audio with the Sony and Lenovo (maybe others too) headphones. When I connect my cheaper WF-C700N, the videos will play normally. To get it to work normally with my Link Buds S, I have to open the Sony “Sound Connect” app through my phone. My Device -> Device Settings -> Bluetooth Connection Quality -> Prioritize Stable Connection. The higher quality audio codec appears to make the video stutter on the Quest software.

       

      Hope this helps

      • XelineDev's avatar
        XelineDev
        Explorer

        Tried to do what you mentioned and it works as it should. Thanks!

  • Hi, noticed the same issue with v71 and v72 and Sony WH-1000XM5. Using built-in audio, there is no issue when watching video in the Browser (e.g. YouTube). However when connected to Bluetooth audio, the video in the browser will be slow (1FPS) and audio will get clipped. This will also happen with other browsers like Wolvic (Geko or Chromium), Opera, Edge... 

    Temporary solution:

    1. Open the Browser
    2. Navigate to chrome://flags
    3. Search for AAudio Output and set it to Disabled (default is Default)
    4. Re-launch the Browser
    5. Check if video works fine in the browser (e.g. YouTube)

    Looks like the culprit is the Android Audio library through which the audio seems to be processed by default in any of these browsers.

    Video will play normally in other applications, e.g. YouTube. Issue only occurs in browsers.

     

  • Quick update - this looks to be fixed in the current PTC - version 72.0.0.530.347, runtime version 72.0.0.531. Information was provided by the Wolvic developer Sergio Villar.

  • This happened to me yesterday too. I'm on v76, just updated this week. Thx for the chrome:://flags temp fix, it worked!

    • blazmalnersic's avatar
      blazmalnersic
      Explorer

      Hi,

      Thanks for the heads up. I am currently on v74 and so far no issues. I guess there is an issue with Bluetooth AAC codec support (if this is actually supported by the Quest3?) since as far as I know, "ordinary" BT headphones which utilize BT SBC codec, have no issues. 

      It seems it is generally better to use premium headphones with headphone jack - which avoids any jitter or latency issues. Personally I currently utilize BT as I am mainly watching movies and honestly I don't notice much audio latency there (maybe I am just old, GRIN).

  • Hey, I have to say I've never experienced this in prior versions, neither on v72 nor v74. It happened for me in v76.

    But I got a newer version of v76 recently that has fixed the bug. This is the quickest fix in the world.

    I'm on v76.1021 Compilation 5091273.8150.520. The compilation that gave me the bug, I think Instead 8150 it was 7XXX

    I send a bug report the other day, I updated today and everything is working fine👍.

  • Hi, I'm on version v77.1025 and i'm experiencing this issue with my Sony LE_WH-XB900N.

  • Same here. I thought it was just me. It had no issues and then after the update it just started doing the same thing as you described. Sony wf-1000xm5 earbuds