Debugging mSBC no audio #520
Replies: 1 comment 1 reply
-
Have you confirmed that in the same environment (the same board/PC, the same BT chip)? The first thing I would check is the audio capture using mSBC audio codec. You can use arecord with the same -D option as with aplay. Without any redirection to a file, you will see in the console that the output will change when poking into headset microphone. If there is no incoming mSBC audio, then much deeper debugging will be required. EDIT: |
Beta Was this translation helpful? Give feedback.
-
Hello, I need some advice on how to debug no audio when playing using SCO (mSBC).
My dev environment: Ubuntu 20.04.3 LTS, kernel 5.11.0-43-generic, bluez 5.56, bluez-alsa master @ f055cf1, Morpheus 260 HP4500 headset
SCO (CVSD) and A2DP (SBC) playback work fine, but after configuring with --enable-msbc, SCO (mSBC) doesn't produce sound nor any errors that i can see. I have --enable-debug and I see msbc is being activated and confirmed the msbc decode path is taken. There are also no obvious errors from aplay or bluealsa or dmesg that I see. I have confirmed using pulseaudio and pipewire that my headset can playback mSBC.
Here are my commands:
I'm attaching logs of working (cvsd) and non-working(msbc) cases if anybody has a spare moment to look.
bluezalsa-cvsd-working-log.txt
bluezalsa-mSBC-not-working-log.txt
Any guidance on how to debug this further would be much appreciated.
Thank You
Beta Was this translation helpful? Give feedback.
All reactions