Bug 1932677

Summary:	volume control and bluetooth device
Product:	[Fedora] Fedora	Reporter:	Mads Kiilerich <mads>
Component:	pipewire	Assignee:	Wim Taymans <wtaymans>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	brunovern.a, mads, wtaymans
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pipewire-0.3.24-1.fc34	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-23 00:16:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mads Kiilerich 2021-02-24 22:14:01 UTC

Description of problem:

Good: When playing on built-in speakers, the volume up/down keys work in Gnome for PA sound sources, showing the "Speakers" overlay, and Settings shows it controls "System Volume".

Bad: When connecting Bluetooh headset (with HiFi A2DP sink) and changing (global) Output Device, sound is routed correctly, but volume up/down shows "Headset" overlay and moves "System Volume" in settings and the device level in pavucontrol BUT the volume stays constant. Muting System Volume also does nothing.

Also: When connecting USB dac and changing (global) Output Device, sound is routed correctly, but volume up/down shows device name in overlay and controls volume correctly and moves device level in pavucontrol BUT does NOT move "System Volume". Muting System Volume also does nothing.

I don't know exactly how it is supposed to work, but the primary bug symptom I see is that Bluetooth volume can't be controlled with volume keys (or in other ways?)

I don't know exactly how Settings should work, but it must be a bug that it is consistent. I think I would expect "System Volume" to be the same as the volume of the device select as (global default) Output Device, and the volume keys controlling these.

Version-Release number of selected component (if applicable):

pipewire-0.3.22-2.fc33.x86_64

Comment 1 Mads Kiilerich 2021-02-24 22:26:05 UTC

Ok, it was not entirely true that it it worked with Bluetooth headset. I realize it only worked because I tested with deadbeef player which apparently use ALSA (shows up as "PipeWire ALSA [deadbeef]"). Rhythmbox and paplay and pw-play hangs while the bluetooth device is global default.

A part of the problem might thus be that PW generally doesn't hook correctly into this bluetooth device that at some level works just fine.

Comment 2 Fedora Update System 2021-03-18 14:31:03 UTC

FEDORA-2021-2c994d0609 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-2c994d0609

Comment 3 Fedora Update System 2021-03-18 21:48:23 UTC

FEDORA-2021-2c994d0609 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2c994d0609`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2c994d0609

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Mads Kiilerich 2021-03-18 23:49:25 UTC

It seems to work consistently now - thanks.

Now it is more clear that Gnome Control Center UI doesn't show how things actually are with PipeWire. That seems like a risk for successful rollout of PW.

I don't know what the plans are in this area or if it is useful, but FWIW, here are my WIP thoughts trying to clarify my mind about what I see going on:

"Output Device" is just the *Default* output device and should be named accordingly.
"System Volume" is the volume of this default device. It should thus really be shown after device selection, next to "Balance".
But also, the better UI for this would be a list of all devices with some kind of "radio button" for selecting the default, and separate volume (and balance) for each device.
The streams shown in "Volume Levels" are more about "Sound Sources" or "Applications" ... or "Streams". And it seems crucial that each entry also gets an option for selecting device, similar to pavucontrol.
Each of these streams need UI with explicit control for whether it should "use default" (and follow when default changes), or if has custom settings for device or volume etc. "route-settings" should only be saved if the stream has custom settings - even if it happen to be the same as the current default.
(Ultimately, it would be nice to have an option for showing streams that not are current but custom or recent streams so they can be controlled too.)

Comment 5 Fedora Update System 2021-03-23 00:16:32 UTC

FEDORA-2021-2c994d0609 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.