4 ms·

Do you know how to enable that on Linux? Or how to check what my current headset is using? I remember I had previously a patched pulseaudio that exposed appro

by krzyk 3y ago

Do you know how to enable that on Linux? Or how to check what my current headset is using? I remember I had previously a patched pulseaudio that exposed appropriate settings, but later it got "merged into mainstream" - and I couldn't find the settings or information what is being used.

abdullahkhalids 3y ago
> Or how to check what my current headset is using? `pactl list` should show you all your input and output sinks and what profiles they are using. Even though, I think the pulseaudio Volume Control app also shows this graphically. Something like `pactl set-card-profile bluez_card.98_52_3D_7E_5D_DE a2dp-sink-sbc_xq` sets the profile to sbc xq. This is a bit old and I am not sure if newer versions of pipewire have better ways of doing it.
- viraptor 3y ago
  Not sure about Gnome, but in KDE you can select the codec from a drop-down in volume panel for a while now. I got high quality headset audio with low delay for at least 2 releases of Fedora.
jeroenhd 3y ago
I use Wireplumber+Pipewire on Ubuntu and Manjaro. I stuffed the following into /etc/wireplumber/bluetooth.lua.d/bluez_monitor.properties : bluez_monitor.properties = { ["bluez5.enable-msbc"] = true, ["bluez5.enable-sbc-xq"] = true, ["bluez5.enable-hw-volume"] = true, ["bluez5.headset-roles"] = "[ hsp_hs hsp_ag hfp_hf hfp_ag ]", ["bluez5.codecs"] = "[ sbc sbc_xq aac ldac aptx aptx_hd aptx_II aptx_II_duplex faststream faststream_duplex ]", } Then from the GNOME audio settings I can pick the appropriate codec from the dropdown. I have a pair of Oneplus buds (the older ones, with a wire in between them) so I don't get any of the newer codecs, but SBC-XQ works well for reducing latency in a pinch. Pulseaudio also has support, but I don't know how to make that work. My last attempt led me to switch to Pipewire.
halz 3y ago
If you're on a distro which has migrated to pipewire+wireplumber, the available and active bluetooth profiles can be discovered with something like: pw-dump | jq -r '.[] | select(.type == "PipeWire:Interface:Device" and .info.props."device.bus" == "bluetooth") | .info.params.Props, .info.params.PropInfo' And by default, wireplumber will enable all of the codecs it has been built with [https://pipewire.pages.freedesktop.org/wireplumber/configuration/bluetooth.html https://pipewire.pages.freedesktop.org/wireplumber/configura...].

by krzyk 3y ago

abdullahkhalids 3y ago

> Or how to check what my current headset is using? `pactl list` should show you all your input and output sinks and what profiles they are using. Even though, I think the pulseaudio Volume Control app also shows this graphically. Something like `pactl set-card-profile bluez_card.98_52_3D_7E_5D_DE a2dp-sink-sbc_xq` sets the profile to sbc xq. This is a bit old and I am not sure if newer versions of pipewire have better ways of doing it.

viraptor 3y ago
Not sure about Gnome, but in KDE you can select the codec from a drop-down in volume panel for a while now. I got high quality headset audio with low delay for at least 2 releases of Fedora.

jeroenhd 3y ago

I use Wireplumber+Pipewire on Ubuntu and Manjaro. I stuffed the following into /etc/wireplumber/bluetooth.lua.d/bluez_monitor.properties : bluez_monitor.properties = { ["bluez5.enable-msbc"] = true, ["bluez5.enable-sbc-xq"] = true, ["bluez5.enable-hw-volume"] = true, ["bluez5.headset-roles"] = "[ hsp_hs hsp_ag hfp_hf hfp_ag ]", ["bluez5.codecs"] = "[ sbc sbc_xq aac ldac aptx aptx_hd aptx_II aptx_II_duplex faststream faststream_duplex ]", } Then from the GNOME audio settings I can pick the appropriate codec from the dropdown. I have a pair of Oneplus buds (the older ones, with a wire in between them) so I don't get any of the newer codecs, but SBC-XQ works well for reducing latency in a pinch. Pulseaudio also has support, but I don't know how to make that work. My last attempt led me to switch to Pipewire.

halz 3y ago

If you're on a distro which has migrated to pipewire+wireplumber, the available and active bluetooth profiles can be discovered with something like: pw-dump | jq -r '.[] | select(.type == "PipeWire:Interface:Device" and .info.props."device.bus" == "bluetooth") | .info.params.Props, .info.params.PropInfo' And by default, wireplumber will enable all of the codecs it has been built with [https://pipewire.pages.freedesktop.org/wireplumber/configuration/bluetooth.html https://pipewire.pages.freedesktop.org/wireplumber/configura...].