Не нашли то, что искали?

Новая публикация
Bungie Answered

in game audio settings do not change output or inputs at all + bluetooth earbuds with hands free and microphone capabilities disabled causes bad bitrate isseus with prox and party chat is turned on

using bluetooth earbuds, which has it's microphone capabilities disabled via device manager in Windows, causes the normal bitrate degradation when your input and output are both  on a singular bluetooth device as well.

never had this issue with other games. tried finicking with window sound device settings. did uninstall the headset and hands free device item in device manager. 

Important note: i have been lfging with random teams using discord vcs, as i can actually use my inbuilt laptop mic, and direct game and discord audio to my headphones. There is no bitrate issues when i have prox and party chat turned off in game with my earbuds. Regardless of that fact, switching inputs from speakers to earbuds, or settings the input device makes ZERO changes.

0

Комментарии

1 комментарий
  • Официальный комментарий

    Hello there,
    Thank you for reaching out.

    We are aware of situations on PC with Bluetooth headsets + voice/prox chat. We are currently investigating Bluetooth/voice-chat problems where audio quality tanks or routing ignores your in-game device choice

    Here are some workarounds that might help

    1. Easiest: fully disable in-game voice when on Bluetooth
    Since you’re already using Discord:

    In Marathon go to Settings → Social → Voice Chat.
    Set Voice Chat to Off and Proximity Chat to Off.
    With voice/prox chat disabled, Marathon stops trying to open a “communications” audio path to your earbuds, which is why your quality goes back to normal (you’ve already observed this). 

    2. If you must use in-game voice on Bluetooth
    You’re fighting Windows’ Bluetooth “hands-free” profile plus Marathon’s separate voice-output routing. The goal is: game audio on your Bluetooth stereo device, voice chat either on another device or forced to stereo-only.

    A. Make sure Windows defaults are sane
    Press Win + R, type mmsys.cpl, press Enter. 
    Playback tab:
    Right-click your Bluetooth “Stereo” device →
    Set as Default Device
    Set as Default Communication Device.
    Recording tab:
    Set your laptop mic (or other non-Bluetooth mic) as both Default and Default Communication Device.
    Disable any Bluetooth “Hands-Free” / headset mic entries if they still show up.
    B. Kill the hands-free profile entirely (strongly recommended)
    Windows will often re-enable the low-quality hands-free path unless you shut it off at the source:

    Method 1 – Devices & Printers

    Open Control Panel → Devices and Printers.
    Right-click your headset → Properties → Services tab.
    Uncheck “Hands-Free Telephony”, apply, then power your headset off and on again. 
    Method 2 – Device Manager (do both sections)

    In Device Manager, under Audio inputs and outputs and under Sound, video and game controllers,
    right-click any entry that says Headset / Hands-Free for your earbuds and choose Disable device.
    Leave only the Stereo endpoint enabled. 
    This prevents Windows from dropping your headset into low-bitrate HFP mode when Marathon starts voice chat.

    C. In-game routing trade-off
    If it still sounds bad whenever voice chat is enabled, the only reliable workaround right now is:

    In Settings → Social → Voice Chat:
    Set Input Device to your laptop mic (or other non-BT mic).
    Set Output Device to anything that is not your Bluetooth headset (e.g., laptop speakers/monitor). 
    That keeps your main game audio in your earbuds at full quality, but crew/prox voice will come out of the other device, which is obviously a compromise—but matches what other affected players have found is the only way to avoid bitrate collapse while still having in-game comms.

Войдите в службу, чтобы оставить комментарий.