I think you got the version wrong. You had it right first (0.3.53) then edited it to be wrong "0.9.53"?
Confirming here too, on Ubuntu 20.04 using Pipewire build fro the Ubuntu Pipewire-Upstream PPA. Bluetooth microphone working fine on 0.3.52, but stutters and crackles on 0.3.53. There has been some kind of regression. Does something stand out in the changelog?
I just tried your suggestion and it works, thanks. I guess there is a default implicit entry in actions/update-props of bluez5.msbc-support = false
that overrides the one in properties{}
if bluez5.msbc-support = true
is not set. That was causing my problem.
Thanks for your help.
I thought update-props will copy and modify the properties{} above?
So if bluez5.msbc-support = true
is in top-level properties{} then it doesn't need to go into update-props. Is that incorrect?
After a recent change (I just updated from 0.3.23 to master), it now looks like mSBC is no longer available for me. mSBC used to work fine, now when I list the profiles I see "HSP/HFP" and "HSP/HFP (CVSD)".
Choosing either of those gives me the CVSD codec (verified by looking at the properties in pactl list soruces
.
I went ahead and set "bluez5.msbc-support = true" in bluez-monitor.conf but it didn't change anything.
@infirit I think adding in pulse-compatible driver names in the pulse emulation layer does make sense for those who are using an older distro-provided blueman version. Eg, I'm on Ubuntu 20.04 with Blueman v2.1.2. When installing pipewire, I'd prefer pipewire-pulse to emulate the pulse-compatible driver name to get Blueman working, than to have to update to a new (unreleased) version of Blueman that has the new pipewire driver name.