-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recognising from Bluetooth headphones works once in a blue moon #184
Comments
I can confirm this. I am not sure it is really a bug, i think this is the intended behavior for pipewire. It probably just get fixed now :) I am on manjaro stable, arch derivative with 3 branches, so on stable the packets are slightly older, but since 2 days i have newer versions too and i am affected. Here are some logs if it helps:
I made a video to illustrate Now, i also found a workaround, that fixes it and also the search actually (i guess the recognition did not work because the profile switching takes time and distorts the sample send to server): disable the automatic bluetooth profile switching between headset and audio profile. As shown here - https://wiki.archlinux.org/title/PipeWire#Automatic_profile_selection To sum it up: a valid workaround is to disable automatic switching to bluetooth headset profile (and not use headset mic), introduced in recent pipewire/wireplumber versions, as shown in arch wiki:
And reboot/restart service. |
I can confirm that disabling headset profile autoswitching fixes the issue. Thanks for the workaround! |
I am using SongRec 0.4.2 from nixpkgs (https://github.com/NixOS/nixpkgs/blob/4f807e8940284ad7925ebd0a0993d2a1791acb2f/pkgs/applications/audio/songrec/default.nix), PipeWire 1.2.3, and Sony WH-CH720N wireless headphones with BlueZ 5.76 and the "High Fidelity Playback (A2DP sink, codec AAC)" audio profile.
When I tick "recognise from my speakers" in SongRec and choose "Monitor of WH-CH720N" as the input, the following things happen:
Similar to #177 but I'm not using Flatpak.
The text was updated successfully, but these errors were encountered: