Ambiguity regarding which codec is actually being used via Bluetooth; Trying to default aptx on startup
Kind of both a question and an issue. I just switched over to pipewire and am using a startup script where I use bluetoothctl to autoconnect to my device, but its ambiguous of what codec that pipewire is actually using. Pulseaudio previously would seem to "save" the previously-used codec, for instance if aptx were selected, it would stay that way on reconnect after reboot and indicate it directly.
pavucontrol, the Bluetooth device I am connecting is registered as a "Headphone" device (Not actually a Headphone, it is an amplifier, but not an issue here). Under "Configuration" in pavucontrol, it lists the Profile as
High Fidelity Playback (A2DP Sink) without any information of what codec is actually being used. An example of direct information of what codec is actually being used would be
High Fidelity Playback (A2DP Sink, codec aptX)
I understand that the actual codecs available can be manually configured by editing
/etc/pipewire/media-session.d/bluez-monitor.conf under the following default options:
# Enabled A2DP codecs (default: all) #bluez5.codecs = [ sbc aac ldac aptx aptx_hd ]
My current configuration is:
bluez5.codecs = [ aptx ]
I am trying to force pipewire to have no choice but to use the aptx codec instead of sbc or something else due to the ambiguity. I have also tried changing
Enabled A2DP codecs (default: all) to
Enabled A2DP codecs (default: aptx) However, under the aforementioned Profile listing, regardless of setting, the profile still remains with no direct indication of what codec is being used.
I assume based on my current configuration, the aptx codec is being used even though pavucontrol does not directly indicate it, right? Is there any sort of command-line options to verify this? I cannot run
bluez-hcidump even though I have
bluez-utils installed either to find anything out. Must be some overlooked bug I guess, or I did not install something.
Thanks for any help or guidance