New AAC decoder support broke AptX codecs?
- PipeWire version (
pipewire --version
): Compiled with libpipewire 0.3.57 Linked with libpipewire 0.3.57 - Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
): Fedora Linux 36 (Thirty Six) - Desktop Environment: lxqt
- Kernel version (
uname -r
): 5.19.8-200.fc36.x86_64 - BlueZ version (
bluetoothctl --version
): bluetoothctl: 5.65 -
lsusb
: Bluetooth devices: Bus 003 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
# paste the output of "bluetoothctl devices" here
Device 22:22:33:29:9E:F0 G7
Description of Problem:
The new AAC decoder seems to have caused some kind of issue with AptX support. With AAC enabled, I can only select between AAC and SBC, and with it disabled, only SBC. Previous versions of pipewire didn't have AAC and AptX/HD worked fine. Rolling back to 0.3.49 restores AptX again.
How Reproducible:
100% of the time
Steps to Reproduce:
- Pair and connect my phone to bluetooth on the target machine with pipewire 0.3.57 and pipewire-codec-aptx. Doesn't matter if it's blueman or blueberry or bluetoothctl, same results.
- Begin playing audio over A2DP from phone to PC.
Actual Results:
If AAC is enabled (e: on the Linux machine in ["bluez5.codecs"]), you can choose between only AAC and SBC (e: on the Android phone). If it's disabled, only SBC.
Expected Results:
AptX HD was available and the default in previous versions of pipewire.