安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
I run a similar config with Arch Linux on my main system. There is no technical reason why Bluetooth headset profiles should be missing from the Steam Deck, and I indeed am able to get my Bluetooth mics to work properly with the same devices. The only reason I can think of that Valve may be refusing to support headset profiles is user experience. Allow me to explain:
Bluetooth is a pretty bandwidth-limited protocol, with janky audio codecs, and bi-directional communication (sending and receiving at the same time) was an afterthought. Headset profiles have a pretty limited ability to use decent codecs, so the best official one (mSBC) sounds pretty bad. Because of this limitation, Valve likely decided that it would be better to simply omit headset profiles entirely. I disagree of course, but that's my best guess as to what's going on.
If you want the technical background, the developer discussion from the underlying audio stack can be found here[gitlab.freedesktop.org].
If you're wondering how Android and others are able to pull off high-quality Bluetooth headset communication, I'm pretty sure they have to break the Bluetooth spec by doing a non-standard probing of what the hardware supports and set up a special communication channel for the audio. Because there's no spec to follow for this, the Pipewire developers have little to go on for developing similar functionality. It may be some time before we see anything like this, unfortunately.