Volume delay in GNOME

There’s a very annoying 20-second delay when sliding the volume control in Leap 15.6, GNOME 45.3. I tinkered with the PulseAudio config according to

https://wiki.archlinux.org/title/PulseAudio/Troubleshooting#Delay_when_changing_volume_using_media_keys

but this applies to media keys and doesn’t make a difference in the slide control. Does anybody know where this delay is set? Thanks.

I don’t see any delay, but I’m using pipewire. Any real reason for still using PulseAudio?

Checked also the PulseAudio interface of pipewire, no delay.
So even if you need a PulseAudio server for legacy players you can still switch to pipewire.

The default openSUSE settings are:

; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0

so 8 milliseconds of delay, less than most buffers in the sound chain; I doubt that your problem might be related to those settings.

I wasn’t aware that pipewire was the default audio handler. They’re both installed.

That is not possible, the two servers are conflicting.
Please show:

zypper se -si pipewi pulse

The other option is to create a test user and login as that test user and test. Should define whether a system or user issue.

1 Like
> zypper se -si pipewi pulse
Loading repository data...
Reading installed packages...

S  | Name                        | Type    | Version                             | Arch   | Repository
---+-----------------------------+---------+-------------------------------------+--------+-------------------
i  | alsa-plugins-pulse          | package | 1.2.7.1-150500.1.1                  | x86_64 | Main Repository
i  | gstreamer-plugin-pipewire   | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | libpipewire-0_3-0           | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | libpulse-mainloop-glib0     | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | libpulse0                   | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | mpg123-pulse                | package | 1.26.4-1.15                         | x86_64 | Main Repository
i  | pipewire                    | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | pipewire-lang               | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | noarch | Packman Repository
i  | pipewire-modules-0_3        | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | pipewire-spa-plugins-0_2    | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | pipewire-spa-tools          | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | pipewire-tools              | package | 1.0.5+git36.60deeb2-150600.3.7.pm.2 | x86_64 | Packman Repository
i  | pulseaudio                  | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-bash-completion  | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-lang             | package | 17.0-150600.2.3                     | noarch | Main Repository
i  | pulseaudio-module-bluetooth | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-module-gsettings | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-module-x11       | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-module-zeroconf  | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-setup            | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | pulseaudio-utils            | package | 17.0-150600.2.3                     | x86_64 | Main Repository
i  | system-user-pulse           | package | 17.0-150600.2.3                     | noarch | Main Repository

I installed VLC and Audacity. Think one of those pulled it in?

I don’t think so, anyway you don’t have pipewire-alsa and pipewire-pulseaudioinstalled, so I wonder if pipewire does anything useful on your system.
Can you show:

inxi -Axxz

please?

> inxi -Axxz
Audio:
  Device-1: Intel Comet Lake PCH-V cAVS vendor: Acer Incorporated ALI
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a3f0
  Device-2: Medeli AudioPro X5 Microphone
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 bus-ID: 1-2.1:5 chip-ID: 0a67:d090
  Device-3: Creative Sound BlasterX Kratos S5
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-5:6 chip-ID: 041e:30ca
  API: ALSA v: k6.4.0-150600.23.42-default status: kernel-api with: aoss
    type: oss-emulator
  Server-1: PipeWire v: 1.0.5 status: off with: wireplumber status: active
  Server-2: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin

OK, pipewire is installed but not active (it lacks two essential pieces).
Your system sound is controlled by pulseaudio and there is nothing wrong with that.

I would check what happens if you create a fresh test user as Malcolm suggested, just to rule out the obvious.

Nothing’s obvious to me at this point. The delay is the same with a test user.

A few things you can try.
Are there keyboard keys to increase/decrease volume (often at or near F11 and F12 keys)? Is the action delayed even when using keys?

Open a terminal and issue top (or use your favourite system monitor), look for process pulseaudio and check that its PR and NI values are at 9 and -11 respectively.

In a terminal, from your “normal” user, issue systemctl --user status pulseaudio and look for anything error/warning/interesting, change the volume and look again.

In a terminal issue alsamixer , choose your sound card (hit F6?), then change the volume with relevant sliders there: is there a delay?

Start pavucontrol (you may need to install the pavucontrol package first) and try if you have similar delay.

You may also use pactl but I haven’t used that tool for quite some time, so let’s hope it is not needed :wink:

BTW, are you using Wayland or X11? Does anything change if you log in to the other (X11 resp Wayland) Gnome session?

1 Like