summaryrefslogtreecommitdiff
path: root/Software/PulseAudio/Notes
diff options
context:
space:
mode:
authorgchini <gchini@web>2021-07-26 19:39:42 +0000
committerIkiWiki <ikiwiki.info>2021-07-26 19:39:42 +0000
commit54c611813b9cbb02481b73e582a3e62779f4a6b5 (patch)
tree8748ea7e2077b294e737dc29f11d7bb480f4b92f /Software/PulseAudio/Notes
parentf222a16100402375f4243392e80390f6bcd68c89 (diff)
Diffstat (limited to 'Software/PulseAudio/Notes')
-rw-r--r--Software/PulseAudio/Notes/15.0.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/Software/PulseAudio/Notes/15.0.mdwn b/Software/PulseAudio/Notes/15.0.mdwn
index 34928b6c..282d1019 100644
--- a/Software/PulseAudio/Notes/15.0.mdwn
+++ b/Software/PulseAudio/Notes/15.0.mdwn
@@ -10,7 +10,7 @@
PulseAudio now supports the LDAC and AptX codecs for A2DP. In order to use them, the device has to support the codecs too. Also "XQ" configuration variants for the old SBC codec are available. The SBC XQ variants have a fixed (and higher than the "normal" SBC) bitrate, so they may have more drop-outs if the wireless connection is bad, but on the hand the quality is always good if the connection is good. For variable bitrate, pulseaudio is now able to increase the bitrate again after it was reduced due to connectivity issues.
-Switching the codec can be done on the command line with `pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez switch-codec CODEC`. Replace `XX_XX_XX_XX_XX_XX` with the device address, which can be found for example with `LANG=C pactl list cards | grep Name`. Replace `CODEC` with one of the available codec names: `aptx`, `aptx_hd`, `ldac_hq` ("High Quality"), `ldac_sq` ("Standard Quality"), `ldac_mq` ("Mobile Quality"), `sbc`, `sbc_xq_453`, `sbc_xq_512`, `sbc_xq_552`. A list of codecs supported by the device can be obtained with `pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez list-codecs` and the currently active codec can be queried with `pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez get-codec`.
+Switching the codec can be done on the command line with `pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez switch-codec CODEC`. Replace `XX_XX_XX_XX_XX_XX` with the device address, which can be found for example with `LANG=C pactl list cards | grep Name`. Replace `CODEC` with one of the available codec names: `aptx`, `aptx_hd`, `ldac_hq` ("High Quality"), `ldac_sq` ("Standard Quality"), `ldac_mq` ("Mobile Quality"), `sbc`, `sbc_xq_453`, `sbc_xq_512`, `sbc_xq_552`. A list of codecs supported by the device can be obtained with `pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez list-codecs` and the currently active codec can be queried with `pactl send-message /card/bluez_card.XX_XX_XX_XX_XX_XX/bluez get-codec`. A simplified way of switching codecs is already implemented in pavucontrol and will be provided with the next pavucontrol release.
### Support for HFP bluetooth profiles
@@ -93,7 +93,7 @@ pactl now supports the following additional commands: `get-default-{sink|source}
### Card profiles can be set to sticky
-Card profiles can be set to sticky using the command `pactl send-message /card/<card name> set-profile-sticky 'true|false'`. The current status can be queried using `pactl send-message /card/<card name> get-profile-sticky`. If a card profile is sticky, it will always be restored, even if the profile is unavailable. Also port availability changes on the card will not impact the profile choice. This is for example useful to set the card profile permanently to "off" for HDMI devices.
+Card profiles can be set to sticky using the command `pactl send-message /card/<card name> set-profile-sticky 'true|false'`. The current status can be queried using `pactl send-message /card/<card name> get-profile-sticky`. If a card profile is sticky, it will always be restored, even if the profile is unavailable. Also port availability changes on the card will not impact the profile choice. This is for example useful to set the card profile permanently to "off" for HDMI devices. Setting profiles to sticky is already implemented in pavucontrol and will be provided with the next pavucontrol release.
## Notes for application developers