Bug ID 1223305
Summary [Regression] Bluetooth audio devices reset/disconnected/audio profile changed(??) when wine/proton applications initialize sound
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Sound
Assignee tiwai@suse.com
Reporter el@horse64.org
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

I'm sadly having what seems to be a regression possibly related to Plasma 5 to
6. Now often when wine or proton applications initialize audio , e.g. when I
startup EA App inside Steam at launch, or something like REAPER's windows
version ( https://reaper.fm/ the trial is free and unrestricted) at any time I
press "play", the following happens:

1. Audio drops out completely for a split second.

2. A visible notification is shown like my bluetooth device just freshly
connected

3. Audio profile is degraded to something horrible, it sounds like the worst
quality headset telephony codec.

4. Sometimes a second later it resets back to what bluetooth profile I had
before, usually high-quality playback only "AAC". But sometimes it also just
doesn't. This can be checked in plasma's audio device panel, where it will show
the telephony codec "Headset Unit ... mSBC" profile in case it didn't reset
properly.

This also happens when another application is already playing audio in
parallel, which sadly makes this disruptive.


You are receiving this mail because: