pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2023-05-02T19:39:40Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3182Bad quality sound on intel HDA HDMI output2023-05-02T19:39:40ZMatthieuBad quality sound on intel HDA HDMI output<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.65
Linked with libpipewire 0.3.65
- Distribut...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.65
Linked with libpipewire 0.3.65
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu 23.04
- Desktop Environment: Default (gnome I guess)
- Kernel version (`uname -r`): 6.2.0-20-generic
## Description of Problem:
The sound quality is degraded, it's hard to explain, there is some reverb / hissing on quite high pitch sound, like the [S] sound when talking. And this problem seems to be not consistent, sometimes it's more pronounced. Even on same audio file, at one time it will be subtle, and little after really obvious that ther is a trouble.
When I revert back on pulseaudio on the 22.10 install, the problem was solved. (So same hardware, same global Ubuntu settings ...)
## How Reproducible:
I've tried with Ubuntu 22.10 installed and in live CD. And with the 23.04 installed
This problem appear with every program (pw-cat, aplay or Internet Browser).
### Steps to Reproduce:
1. Just listen music or movie with bad sound
2. Revert to pulseaudio
3. The sound is now great, at least normal.
### Actual Results:
Bad quality sound
### Expected Results:
Normal qyality sound
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw-dump.log](/uploads/810e9e77fce565b37a97e855c6383356/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3181Add jack_position_t::tick_double, and flags around it2023-04-28T15:32:54ZDaniel AppeltAdd jack_position_t::tick_double, and flags around it<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.70
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.70
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: awesome-wm
- Kernel version (`uname -r`): 6.2.12-arch1-1
## Description of Problem:
The original jack(2) is receiving new features from time to time. One of these is more precise timing information introduced in [release 1.9.19](https://github.com/jackaudio/jack2/releases/tag/v1.9.19) of jack2.
Software that makes use of this new feature does not compile against pipewire-jack, [for example mod-host](https://github.com/moddevices/mod-host/issues/55).
## How Reproducible:
Always
### Steps to Reproduce:
1. git clone https://github.com/moddevices/mod-host.git
2. cd mod-host
3. make
### Actual Results:
Compilation fails with `JackTickDouble` not declared.
### Expected Results:
Compilation does not fail..https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3180API to discard buffers2023-04-28T11:09:22ZAleix PolAPI to discard buffersIt can happen at times that a buffer that we dequeued needs to be discarded rather than enqueued back.
It would be useful to have an API to give the buffer back without having to send its contents into the other side of the stream.It can happen at times that a buffer that we dequeued needs to be discarded rather than enqueued back.
It would be useful to have an API to give the buffer back without having to send its contents into the other side of the stream.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3179`Dummy Output` doesn't work on RHEL9 aarch642023-10-09T16:25:56ZAlessandro Bono`Dummy Output` doesn't work on RHEL9 aarch64- PipeWire version (`pipewire --version`): 0.3.47
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Red Hat Enterprise Linux 9.1 (Plow)
- Desktop Environment: GNOME
- Kernel version (`uname -r`): 5.14.0-162....- PipeWire version (`pipewire --version`): 0.3.47
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Red Hat Enterprise Linux 9.1 (Plow)
- Desktop Environment: GNOME
- Kernel version (`uname -r`): 5.14.0-162.23.1.el9_1.aarch64
## Description of Problem:
On EC2 instances there is no output device and `Dummy Output` is used as fallback. However, applications fail to play sound. Even GNOME Settings (aka `gnome-control-center`) is unable to play the test sound:
```
pipewire-pulse[5998]: mod.protocol-pulse: client 0xaaab032696c0 [gnome-control-center]: ERROR command:-1 (invalid) tag:3 error:25 (Input/output error)
pipewire-pulse[5998]: mod.protocol-pulse: client 0xaaab032696c0 [gnome-control-center]: ERROR command:-1 (invalid) tag:4 error:25 (Input/output error)
pipewire-pulse[5998]: mod.protocol-pulse: client 0xaaab032696c0 [gnome-control-center]: ERROR command:-1 (invalid) tag:5 error:25 (Input/output error)
gnome-control-c[62435]: Failed to play sound: IO error
```
## How Reproducible:
Always on `aarch64`, never on `x86-64`.
### Steps to Reproduce:
1. Execute `canberra-gtk-play --id "audio-channel-front-right"`
### Actual Results:
An error is given and no sound is sent to `Dummy Output`:
```
$ canberra-gtk-play --id "audio-channel-front-right"
Failed to play sound: IO error
```
### Expected Results:
No error is given and the sound is sent to `Dummy Output`
# Additional Info (as attachments):
- For some reasons `echo -e '\a'` works
- Debug output of `pipewire-pulse` when executing `canberra-gtk-play --id "audio-channel-front-right"`: [pipewire-pulse-debug-canberra.log](/uploads/dd975aa1a41ef1b69b9187dd7260354f/pipewire-pulse-debug-canberra.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3177crackling every second after switching to "pro audio" output configuration2023-04-25T10:20:00ZOswald Buddenhagencrackling every second after switching to "pro audio" output configuration<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 3.70
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 3.70
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): debian sid
- Desktop Environment: none
- Kernel version (`uname -r`): 6.3.0-rc2 + patches
during playback with the "Pro Audio" profile, there is a crack roughly every second.
but it happens only when playback starts right after switching to the profile, or the switch happens during playback.
switching in the other direction to one of the "Analog Stereo" profiles doesn't appear to induce any artifacts (except during the switch itself if done while playing back, of course).
switching to "Pro Audio" and then waiting for some seconds before starting playback works fine.
it's not related to the connection to the server, as it doesn't matter whether the playback app (audacious) was running while the profile was changed.
so i guess the server fails to re-adjust some of the parameters while it's keeping the alsa device handle open.
the hardware is an E-MU 0404 with the (patched) emu10k1 driver. but as both profiles are using the exact same driver config (as there is only one) and one of them works, i think it's safe to dismiss the hardware and driver as the source of the problem per se.
issue #2992 sounds vaguely similar.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3176Minecraft cannot select right default device (probably JACK problem)2023-10-02T06:38:26ZTimofey XMinecraft cannot select right default device (probably JACK problem)<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
```
pipewire
Compiled with libpipewire 0.3.70
Linked with libpipewire 0.3.70
```
- D...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
```
pipewire
Compiled with libpipewire 0.3.70
Linked with libpipewire 0.3.70
```
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): EndeavourOS
- Desktop Environment: KDE Plasma 5.27.4
- Kernel version (`uname -r`): 6.2.12-arch1-1
## Description of Problem:
After an update sound in Minecraft chooses laptop speakers when default device is bluetooth headphones. Probably caused not by bluetooth module, but by JACK support. Minecraft has output device switcher with two options: Default and JACK Default pressing that button . And to fix the issue you must downgrade pipewire-jack, but may leave pipewire-alsa and pipewire-pulse.
Can be fixed by downgrading pipewire libpipewire pipewire-audio pipewire-jack to 0.3.66
## How Reproducible:
Every time
### Steps to Reproduce:
1. Latest EndeavourOS
2. Install java-17-openjdk (also tried with another java version and with Liberica JDK)
3. Connect bluetooth headphones
4. Open some Minecraft launcher (tried two different)
5. Run 1.19.4
6. Press some Minecraft interface buttons
### Actual Results:
Click sounds from speakers
### Expected Results:
Click sounds from headphones
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw-dump.log](/uploads/dcb52b3050d4721b3450777987d8e36e/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3174check_realtime_privileges(): Can't set rt prio to 88: Operation not permitted...2023-04-26T13:07:08ZAtemucheck_realtime_privileges(): Can't set rt prio to 88: Operation not permitted (try increasing rlimits)I'm trying to get pipewire to run with realtime priority.
```
$ PIPEWIRE_DEBUG=5 pipewire
...
[I][12603.799702] pw.conf | [ conf.c: 953 pw_context_conf_section_for_each()] handle override '/Users/atemu/.config/pipewire/pi...I'm trying to get pipewire to run with realtime priority.
```
$ PIPEWIRE_DEBUG=5 pipewire
...
[I][12603.799702] pw.conf | [ conf.c: 953 pw_context_conf_section_for_each()] handle override '/Users/atemu/.config/pipewire/pipewire.conf.d/test.conf' section 'context.modules'
[I][12603.799709] pw.module | [ impl-module.c: 162 pw_context_load_module()] 0x55f27b2551a0: name:libpipewire-module-rt args:{
nice.level = -11
rt.prio = 88
#rt.time.soft = -1
#rt.time.hard = -1
}
[D][12603.799716] pw.module | [ impl-module.c: 167 pw_context_load_module()] moduledir set to: /nix/store/7zblgkp9iakf9hh21xzq9g397h9zf2ff-pipewire-0.3.68-lib/lib/pipewire-0.3
[D][12603.799723] pw.module | [ impl-module.c: 177 pw_context_load_module()] trying to load module: libpipewire-module-rt (/nix/store/7zblgkp9iakf9hh21xzq9g397h9zf2ff-pipewire-0.3.68-lib/lib/pipewire-0.3/libpipewire-module-rt.so) args({
nice.level = -11
rt.prio = 88
#rt.time.soft = -1
#rt.time.hard = -1
})
[D][12603.799732] pw.global | [ global.c: 88 pw_global_new()] 0x55f27b298ba0: new PipeWire:Interface:Module 29
[D][12603.799738] mod.rt | [ module-rt.c: 966 pipewire__module_init()] module 0x55f27b2db2a0: new
[I][12603.799745] mod.rt | [ module-rt.c: 610 check_realtime_privileges()] Can't set rt prio to 88: Operation not permitted (try increasing rlimits)
[I][12603.799778] mod.rt | [ module-rt.c: 640 set_nice()] main thread nice level set to -11
[I][12603.803584] mod.rt | [ module-rt.c: 640 set_nice()] main thread nice level set to -11
[D][12603.803696] mod.rt | [ module-rt.c: 661 set_rlimit()] clamping rt.time.soft from 18446744073709551615 to 200000 because of RTKit
[D][12603.803715] mod.rt | [ module-rt.c: 677 set_rlimit()] rt.time.soft:200000 rt.time.hard:200000
[D][12603.803727] pw.module | [ impl-module.c: 363 pw_impl_module_update_properties()] 0x55f27b298970: updated 4 properties
[D][12603.803738] pw.module | [ impl-module.c: 363 pw_impl_module_update_properties()] 0x55f27b298970: updated 2 properties
[D][12603.803750] mod.rt | [ module-rt.c: 1057 pipewire__module_init()] initialized using RTKit
[D][12603.803760] pw.global | [ global.c: 164 pw_global_register()] 0x55f27b298ba0: registered 29
[D][12603.803771] pw.module | [ impl-module.c: 256 pw_context_load_module()] 0x55f27b298970: loaded module: libpipewire-module-rt
[I][12603.803781] pw.conf | [ conf.c: 582 load_module()] 0x55f27b2551a0: loaded module libpipewire-module-rt
...
```
```
$ chrt -p $(pidof -o $(pidof pipewire-pulse) pipewire)
pid 47742's current scheduling policy: SCHED_OTHER|SCHED_RESET_ON_FORK
pid 47742's current scheduling priority: 0
```
But I can run `chrt 88 echo test` just fine and the `echo` command does get rt prio.
```
$ ulimit -a
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 127949
max locked memory (kbytes, -l) 8192
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 99
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 127949
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
```
```
$ cat /proc/$(pidof -o $(pidof pipewire-pulse) pipewire)/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 127949 127949 processes
Max open files 1024 524288 files
Max locked memory 8388608 8388608 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 127949 127949 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 99 99
Max realtime timeout 200000 200000 us
```
What's going on? Am I doing something wrong?
```
$ pipewire --version
pipewire
Compiled with libpipewire 0.3.68
Linked with libpipewire 0.3.68
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3173Realtek ALC 4080 on MSI B650 Tomahawk2023-09-04T14:00:00ZarleyantesRealtek ALC 4080 on MSI B650 TomahawkHi, i have the following problem:
With default pipewire my chipset is not working and only shows up as 'analog audio'.
Its also broken in alsa ucm but when editing it like https://github.com/alsa-project/alsa-ucm-conf/issues/306 it star...Hi, i have the following problem:
With default pipewire my chipset is not working and only shows up as 'analog audio'.
Its also broken in alsa ucm but when editing it like https://github.com/alsa-project/alsa-ucm-conf/issues/306 it starts being shown correctly, however pipewire doesnt work with it. However when disabling pipewire-alsa by deleting:
/etc/alsa/conf.d/50-pipewire.conf
/etc/alsa/conf.d/99-pipewire-default.conf
/usr/share/alsa/alsa.conf.d/50-pipewire.conf
/usr/share/alsa/alsa.conf.d/99-pipewire-default.conf
... and switching the profiles around it starts to work.
I am on Fedora 38:
$ pipewire --version
pipewire
Compiled with libpipewire 0.3.69
Linked with libpipewire 0.3.69
I am a beginner user so i will not be able to test anything except fedora builds and updates-testing builds.![Captura_de_tela_de_2023-04-21_10-06-38](/uploads/133401aaca7f4b9d6fbdf277821086ef/Captura_de_tela_de_2023-04-21_10-06-38.png)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3172Turn off hw-volume feature on 3M WorkTunes Connect2023-05-17T12:02:33ZDaniel HouckTurn off hw-volume feature on 3M WorkTunes Connect## Preamble
I have a fix Iʼm including; due to GitLab anti-spam provisions I cannot actually make a merge request for it at this time. Hereʼs the patch:
```diff
diff --git a/spa/plugins/bluez5/bluez-hardware.conf b/spa/plugins/bluez5/b...## Preamble
I have a fix Iʼm including; due to GitLab anti-spam provisions I cannot actually make a merge request for it at this time. Hereʼs the patch:
```diff
diff --git a/spa/plugins/bluez5/bluez-hardware.conf b/spa/plugins/bluez5/bluez-hardware.conf
index 0247f75d5..9004675ea 100644
--- a/spa/plugins/bluez5/bluez-hardware.conf
+++ b/spa/plugins/bluez5/bluez-hardware.conf
@@ -44,6 +44,7 @@ bluez5.features.device = [
{ name = "SoundCore 2", no-features = [ sbc-xq ] }, # #pipewire-2291
{ name = "Tribit MAXSound Plus", no-features = [ hw-volume ] }, # #pipewire-1592
{ name = "Urbanista Stockholm Plus", no-features = [ msbc-alt1, msbc-alt1-rtl ] },
+ { name = "WorkTunes Connect", no-features = [ hw-volume ] }, # 3M WorkTunes Connect
{ address = "~^44:5e:cd:", no-features = [ faststream, a2dp-duplex ]}, # #pipewire-1756
```
## Requested info
<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
<!-- If you can, test also with Pulseaudio and list `pulseaudio --version`. -->
- PipeWire version (`pipewire --version`): 0.3.69
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: KDE
- Kernel version (`uname -r`): 6.2.11-zen1-1-zen
- BlueZ version (`bluetoothctl --version`): 5.66
- `lsusb`: [Irrelevant, and unlike the rest contains more information than Iʼd like to give unless needed]
- Bluetooth devices:
```
Device 1C:6E:4C:17:AE:20 WorkTunes Connect
```
## Description of Problem:
Volume settings reset to 100% a few seconds after change, but the slider still shows whatever percent I set it to
## How Reproducible:
Completely, deterministic
### Steps to Reproduce:
1. Connect to 3M WorkTunes Connect headset
2. Set volume to less than 100%
3. Play a sound (but not too loud of one or youʼll hurt your ears, because volume settings are not respected)
### Actual Results:
Sound plays at full volume
### Expected Results:
Sound plays at less than full volume
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
- Bluetooth debug log, see [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth): [pw-dump.log](/uploads/a192bb9b2c7abf5bcea890ffea150c49/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3171-Wdangling-pointer warnings in 0.3.70 with GCC 132023-04-21T00:39:08ZSam James-Wdangling-pointer warnings in 0.3.70 with GCC 13With GCC 13, I get several `-Wdangling-pointer` warnings in pipewire-0.3.70.
This is using 13.0.1 20230419 (prerelease) (this is GCC 13 RC2).
For the 32-bit multilib build:
```
[229/778] x86_64-pc-linux-gnu-gcc -m32 -mfpmath=sse -Ispa/...With GCC 13, I get several `-Wdangling-pointer` warnings in pipewire-0.3.70.
This is using 13.0.1 20230419 (prerelease) (this is GCC 13 RC2).
For the 32-bit multilib build:
```
[229/778] x86_64-pc-linux-gnu-gcc -m32 -mfpmath=sse -Ispa/plugins/alsa/libspa-alsa.so.p -Ispa/plugins/alsa -I../pipewire-0.3.70/spa/plugins/alsa -I. -I../pipewire-0.3.70 -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -DHAVE_ALSA_UCM -DHAVE_READLINK -MD -MQ spa/plugins/alsa/libspa-alsa.so.p/alsa-pcm.c.o -MF spa/plugins/alsa/libspa-alsa.so.p/alsa-pcm.c.o.d -o spa/plugins/alsa/libspa-alsa.so.p/alsa-pcm.c.o -c ../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c
In file included from ../pipewire-0.3.70/spa/include/spa/pod/filter.h:20,
from ../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:11:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘enum_pcm_formats.constprop’ at ../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:1039:2:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*b.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c: In function ‘enum_pcm_formats.constprop’:
../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:994:30: note: ‘f’ declared here
994 | struct spa_pod_frame f[2];
| ^
../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:988:66: note: ‘b’ declared here
988 | struct spa_pod **result, struct spa_pod_builder *b)
| ~~~~~~~~~~~~~~~~~~~~~~~~^
[...]
[674/778] x86_64-pc-linux-gnu-gcc -m32 -mfpmath=sse -Isrc/modules/libpipewire-module-protocol-native.so.p -Isrc/modules -I../pipewire-0.3.70/src/modules -I. -I../pipewire-0.3.70 -Isrc -I../pipewire-0.3.70/src -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -pthread -MD -MQ src/modules/libpipewire-module-protocol-native.so.p/module-protocol-native_v0_protocol-native.c.o -MF src/modules/libpipewire-module-protocol-native.so.p/module-protocol-native_v0_protocol-native.c.o.d -o src/modules/libpipewire-module-protocol-native.so.p/module-protocol-native_v0_protocol-native.c.o -c ../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c
In file included from ../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:9:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘remap_from_v2’ at ../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:443:3:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*builder.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c: In function ‘remap_from_v2’:
../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:414:38: note: ‘f’ declared here
414 | struct spa_pod_frame f;
| ^
../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:401:41: note: ‘builder’ declared here
401 | struct spa_pod_builder *builder)
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
```
For the regular 64-bit build:
```
[136/879] x86_64-pc-linux-gnu-gcc -Ispa/plugins/bluez5/libspa-codec-bluez5-faststream.so.p -Ispa/plugins/bluez5 -I../pipewire-0.3.70/spa/plugins/bluez5 -I. -I../pipewire-0.3.70 -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -DCODEC_PLUGIN -MD -MQ spa/plugins/bluez5/libspa-codec-bluez5-faststream.so.p/a2dp-codec-faststream.c.o -MF spa/plugins/bluez5/libspa-codec-bluez5-faststream.so.p/a2dp-codec-faststream.c.o.d -o spa/plugins/bluez5/libspa-codec-bluez5-faststream.so.p/a2dp-codec-faststream.c.o -c ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-faststream.c
In file included from ../pipewire-0.3.70/spa/include/spa/param/audio/format-utils.h:13,
from ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-faststream.c:15:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘codec_enum_config’ at ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-faststream.c:138:2:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*b.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-faststream.c: In function ‘codec_enum_config’:
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-faststream.c:117:30: note: ‘f’ declared here
117 | struct spa_pod_frame f[2];
| ^
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-faststream.c:114:41: note: ‘b’ declared here
114 | struct spa_pod_builder *b, struct spa_pod **param)
| ~~~~~~~~~~~~~~~~~~~~~~~~^
[187/879] x86_64-pc-linux-gnu-gcc -Ispa/plugins/bluez5/libspa-codec-bluez5-aac.so.p -Ispa/plugins/bluez5 -I../pipewire-0.3.70/spa/plugins/bluez5 -I. -I../pipewire-0.3.70 -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -DCODEC_PLUGIN -MD -MQ spa/plugins/bluez5/libspa-codec-bluez5-aac.so.p/a2dp-codec-aac.c.o -MF spa/plugins/bluez5/libspa-codec-bluez5-aac.so.p/a2dp-codec-aac.c.o.d -o spa/plugins/bluez5/libspa-codec-bluez5-aac.so.p/a2dp-codec-aac.c.o -c ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aac.c
In file included from ../pipewire-0.3.70/spa/plugins/bluez5/media-codecs.h:16,
from ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aac.c:17:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘codec_enum_config’ at ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aac.c:186:2:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*b.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aac.c: In function ‘codec_enum_config’:
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aac.c:165:30: note: ‘f’ declared here
165 | struct spa_pod_frame f[2];
| ^
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aac.c:162:41: note: ‘b’ declared here
162 | struct spa_pod_builder *b, struct spa_pod **param)
| ~~~~~~~~~~~~~~~~~~~~~~~~^
[190/879] x86_64-pc-linux-gnu-gcc -Ispa/plugins/bluez5/libspa-codec-bluez5-aptx.so.p -Ispa/plugins/bluez5 -I../pipewire-0.3.70/spa/plugins/bluez5 -I. -I../pipewire-0.3.70 -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -DCODEC_PLUGIN -MD -MQ spa/plugins/bluez5/libspa-codec-bluez5-aptx.so.p/a2dp-codec-aptx.c.o -MF spa/plugins/bluez5/libspa-codec-bluez5-aptx.so.p/a2dp-codec-aptx.c.o.d -o spa/plugins/bluez5/libspa-codec-bluez5-aptx.so.p/a2dp-codec-aptx.c.o -c ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aptx.c
In file included from ../pipewire-0.3.70/spa/include/spa/param/audio/format-utils.h:13,
from ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aptx.c:11:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘codec_enum_config’ at ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aptx.c:227:2:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*b.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aptx.c: In function ‘codec_enum_config’:
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aptx.c:206:30: note: ‘f’ declared here
206 | struct spa_pod_frame f[2];
| ^
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-aptx.c:203:41: note: ‘b’ declared here
203 | struct spa_pod_builder *b, struct spa_pod **param)
| ~~~~~~~~~~~~~~~~~~~~~~~~^
[257/879] x86_64-pc-linux-gnu-gcc -Ispa/plugins/alsa/libspa-alsa.so.p -Ispa/plugins/alsa -I../pipewire-0.3.70/spa/plugins/alsa -I. -I../pipewire-0.3.70 -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -DHAVE_ALSA_UCM -DHAVE_READLINK -MD -MQ spa/plugins/alsa/libspa-alsa.so.p/alsa-pcm.c.o -MF spa/plugins/alsa/libspa-alsa.so.p/alsa-pcm.c.o.d -o spa/plugins/alsa/libspa-alsa.so.p/alsa-pcm.c.o -c ../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c
In file included from ../pipewire-0.3.70/spa/include/spa/pod/filter.h:20,
from ../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:11:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘enum_pcm_formats.constprop’ at ../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:1039:2:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*b.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c: In function ‘enum_pcm_formats.constprop’:
../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:994:30: note: ‘f’ declared here
994 | struct spa_pod_frame f[2];
| ^
../pipewire-0.3.70/spa/plugins/alsa/alsa-pcm.c:988:66: note: ‘b’ declared here
988 | struct spa_pod **result, struct spa_pod_builder *b)
| ~~~~~~~~~~~~~~~~~~~~~~~~^
[259/879] x86_64-pc-linux-gnu-gcc -Ispa/plugins/bluez5/libspa-codec-bluez5-ldac.so.p -Ispa/plugins/bluez5 -I../pipewire-0.3.70/spa/plugins/bluez5 -I. -I../pipewire-0.3.70 -Ispa/include -I../pipewire-0.3.70/spa/include -I/usr/include/ldac -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -DCODEC_PLUGIN -DENABLE_LDAC_ABR -MD -MQ spa/plugins/bluez5/libspa-codec-bluez5-ldac.so.p/a2dp-codec-ldac.c.o -MF spa/plugins/bluez5/libspa-codec-bluez5-ldac.so.p/a2dp-codec-ldac.c.o.d -o spa/plugins/bluez5/libspa-codec-bluez5-ldac.so.p/a2dp-codec-ldac.c.o -c ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-ldac.c
In file included from ../pipewire-0.3.70/spa/plugins/bluez5/media-codecs.h:16,
from ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-ldac.c:23:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘codec_enum_config’ at ../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-ldac.c:164:2:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*b.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-ldac.c: In function ‘codec_enum_config’:
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-ldac.c:138:30: note: ‘f’ declared here
138 | struct spa_pod_frame f[2];
| ^
../pipewire-0.3.70/spa/plugins/bluez5/a2dp-codec-ldac.c:135:41: note: ‘b’ declared here
135 | struct spa_pod_builder *b, struct spa_pod **param)
| ~~~~~~~~~~~~~~~~~~~~~~~~^
[660/879] x86_64-pc-linux-gnu-gcc -Isrc/modules/libpipewire-module-protocol-native.so.p -Isrc/modules -I../pipewire-0.3.70/src/modules -I. -I../pipewire-0.3.70 -Isrc -I../pipewire-0.3.70/src -Ispa/include -I../pipewire-0.3.70/spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wold-style-declaration -Wdeprecated-declarations -Wunused-result -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -O2 -pipe -march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type -ggdb3 -Werror=format-security -Werror=implicit-function-declaration -Wimplicit-int -Werror=int-conversion -Wformat -fPIC -pthread -MD -MQ src/modules/libpipewire-module-protocol-native.so.p/module-protocol-native_v0_protocol-native.c.o -MF src/modules/libpipewire-module-protocol-native.so.p/module-protocol-native_v0_protocol-native.c.o.d -o src/modules/libpipewire-module-protocol-native.so.p/module-protocol-native_v0_protocol-native.c.o -c ../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c
In file included from ../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:9:
In function ‘spa_pod_builder_push’,
inlined from ‘spa_pod_builder_push_choice’ at ../pipewire-0.3.70/spa/include/spa/pod/builder.h:390:2,
inlined from ‘remap_from_v2’ at ../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:443:3:
../pipewire-0.3.70/spa/include/spa/pod/builder.h:112:30: warning: storing the address of local variable ‘f’ in ‘*builder.state.frame’ [-Wdangling-pointer=]
112 | builder->state.frame = frame;
| ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c: In function ‘remap_from_v2’:
../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:414:38: note: ‘f’ declared here
414 | struct spa_pod_frame f;
| ^
../pipewire-0.3.70/src/modules/module-protocol-native/v0/protocol-native.c:401:41: note: ‘builder’ declared here
401 | struct spa_pod_builder *builder)
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
```
Full build log: [build.log](/uploads/920fbf1c1e51fcd64e3af09fc5f802f6/build.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3170Documentation unclear on how to use 'actions' in configuration2023-05-15T11:08:10ZJonathan WattDocumentation unclear on how to use 'actions' in configurationAt a high level, my issue is that when using libpipewire-module-raop-discover, in GNOME settings the Device Output dropdown shows two copies of the AirPlay device I want to play to. One works and the other does not.
A recent PipeWire up...At a high level, my issue is that when using libpipewire-module-raop-discover, in GNOME settings the Device Output dropdown shows two copies of the AirPlay device I want to play to. One works and the other does not.
A recent PipeWire update renamed these (thanks!) to clarify that the reason there are two copies is because one is IPv4 (works), the other is IPv6 (does not work).
I would like to somehow remove the IPv6 output device from GNOME settings, and perhaps the cleanest way is to prevent PipeWire from creating a stream for it(?). So was hoping to be able to do something like:
```
{ name = libpipewire-raop-discover
args = {
stream.rules = [
{ matches = [
{ raop.ip.version = 6
}
]
}
]
actions = {
DO-NOT-CREATE-A-STREAM
}
}
flags = [ ifexists ]
}
```
Unfortunately I'm having some trouble figuring out from the documentation what the valid contents of `actions` are, or if this is possible some other way.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3169crackling audio every 1-2 seconds2023-04-21T10:22:34ZFlorian Hänelcrackling audio every 1-2 seconds<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): libpipewire 0.3.58
- Distribution and distribution version (`PRETTY_NAME` from `/etc...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): libpipewire 0.3.58
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu 22.10
- Desktop Environment: KDE plasma
- Kernel version (`uname -r`): 5.19.0-1022-lowlatency
## Description of Problem:
audio crackling every 2-3 seconds for few ms. it appears on SPDIF speakers but also bluetooth headphones.
I can record it using audacity on a monitor device and it looks like zero samples
this manifested one or two weeks ago
## How Reproducible:
first noticed on spotify, firefox. also on speaker-test -t sine -f 100 and pa-play
### Steps to Reproduce:
1. play any audio using any client
### Actual Results:
crackling
### Expected Results:
no crackling
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/31deab10947862d8131d3aa1a812fdbd/pw-dump.log)
PIPEWIRE_DEBUG=5 pw-play does not show xruns that coincide with the crackling
speaker-test crackles every time it prints Time per period = 10.989598 but also more than thathttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3168USB DAC disappearing after waking from sleep/suspend (fiio k3)2023-09-11T00:07:46ZAdis DurakovicUSB DAC disappearing after waking from sleep/suspend (fiio k3)When waking the PC from sleep, my USB DAC (FiiO K3) disappears, and only comes back when I re-plug it.
The problem does not affect the BT speaker or my onboard audio jack.
```
pipewire --version
pipewire
Compiled with libpipewire 0.3.6...When waking the PC from sleep, my USB DAC (FiiO K3) disappears, and only comes back when I re-plug it.
The problem does not affect the BT speaker or my onboard audio jack.
```
pipewire --version
pipewire
Compiled with libpipewire 0.3.69
Linked with libpipewire 0.3.69
Fedora 38
when it's connected: cat /proc/asound/modules
1 0 snd_usb_audio
2 1 snd_hda_intel
3 2 snd_usb_audio
4 3 snd_hda_intel
5 4 snd_usb_audio
6 5 snd_usb_audio
after wakeup: cat /proc/asound/modules
1 0 snd_usb_audio
2 1 snd_hda_intel
3 2 snd_usb_audio
4 3 snd_hda_intel
5 4 snd_usb_audio
```
If you need anything else, let me know.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3167Microphone no longer works on bluetooth with FastStream A2DP Source/Sink2023-04-19T16:01:03ZaraujormMicrophone no longer works on bluetooth with FastStream A2DP Source/SinkSince commit 1d5c693d33cff81761a775b70e1c697c544c4b63 microphone stopped working with Faststream A2DP Source/Sink. Issue persists since that commit, and is present on latest version 0.3.69 and in master (at the time I tested, was 74b1b63...Since commit 1d5c693d33cff81761a775b70e1c697c544c4b63 microphone stopped working with Faststream A2DP Source/Sink. Issue persists since that commit, and is present on latest version 0.3.69 and in master (at the time I tested, was 74b1b63c3d865b1b21845bb4422982c1de26c885).
This is confirmed with (at least) the Avantree Aria Podio headphones. In previous commit 60718c4b4f80504c2d9d6f82bb06d17bff25a456 it works as expected.
Aforementioned commit 1d5c693d33cff81761a775b70e1c697c544c4b63 also seems to have broken the microphone on HSF/HFP profile (at least on the Aria Podio), that was apparently fixed since commit 282c7975fa2d8a728790d6fc7f8befcd19a74ab7 (`bluez5: backend-native: fix getsockopt/fcntl error code handling`). Perhaps in this latest fix, something was missing for Faststream A2DP Source/Sink to work again?
If any more info or testing is needed, please tell me. Thanks in advance.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3166Avoid sound aliasing2023-06-26T10:05:10ZMarek MosiewiczAvoid sound aliasingI recently decided to use amplifier for music. I used my old amplifier and after trying FLAC CD found that there is some issue with sound. The problem was that CD uses 44100Hz sampling and pipewire was set by default to 48000Hz. Configur...I recently decided to use amplifier for music. I used my old amplifier and after trying FLAC CD found that there is some issue with sound. The problem was that CD uses 44100Hz sampling and pipewire was set by default to 48000Hz. Configuring pipewire to 44100 solved the problem for CD music. But there are sources which uses 48kHz (I think lot of YouTube). Firefox seems to not switch output and this is questionable how to do this as there can be other sources playing. Anyway some algorithm which does not require client change can be considered. Kind of daemon which detects new input source and if it has some threshold and different frequency it changes output. In fact normal workflow is that it can even by configuration silent previous main source (e.g. we play music but want to see video)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3165Updating pipewire 0.3.68 to 0.3.69 broke bluetooth and crashes wireplumber an...2023-04-19T13:10:36ZDolf AndringaUpdating pipewire 0.3.68 to 0.3.69 broke bluetooth and crashes wireplumber and pipewire
- PipeWire version (`pipewire --version`): 0.3.69-1
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora 37
- Desktop Environment: Gnome-shell
- Kernel version (`uname -r`): 6.2.10-200
## Description o...
- PipeWire version (`pipewire --version`): 0.3.69-1
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora 37
- Desktop Environment: Gnome-shell
- Kernel version (`uname -r`): 6.2.10-200
## Description of Problem:
Gnome refuses to connect bluetooth devices and restart of Pipewire (wireplumber) crashes during restart with core dump after upgrade on fedora 37 from pipewire 0.3.68 to 0.3.69
After I did a `dnf downgrade pipewire` and restarted pipewire (no reboot needed) which downgrades to 0.3.59, the issue is gone and bluetooth connects again. I can't seem to easily downgrade to 0.3.68, since that version is no longer available. But yesterday (before I updated) everything worked just fine, so I think it is due to an issue with 0.3.69.
## How Reproducible:
Connect any a2dp bluetooth device.
`systemctl --user restart pipewire`
`systemctl --user restart pipewire-pulse.service`
### Steps to Reproduce:
1. `dnf update` on fedora 37
2. reboot
3. try to connect a bluetooth device (fails)
4. restart pipewire (crashes)
### Actual Results:
When trying to connect a bluetooth audio device:
```
Apr 18 10:25:35 dolfdesktop bluetoothd[33432]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for xx:xx:xx:xx:xx:xx: Protocol not available
```
Restarting `pipewire` and `pipewire-pulse` crashes pipewire and all audio stops working (audio ui components even disappear from gnome).
```
Apr 18 10:42:44 dolfdesktop abrt-notification[55239]: [🡕] Process 2945 (wireplumber) crashed in _nl_load_domain.cold()
Subject: ABRT has detected unexpected termination: wireplumber
Defined-By: ABRT
Support: https://bugzilla.redhat.com/
Documentation: man:abrt(1)
wireplumber killed by SIGABRT
#1 [libc.so.6] _nl_load_domain.cold
#2 [libc.so.6] 81daba31ee66dbd63efdc4252a872949d874d136+218710
#3 [libasound.so.2] snd_mixer_elem_add
#4 [libspa-alsa.so] mixer_class_event
#5 [libasound.so.2] hctl_event_handler
Use the abrt command-line tool for further analysis or to report
the problem to the appropriate support site.
```
### Expected Results:
Bluetooth connection working.
# Additional Info (as attachments):
Additional crash info.
```
abrt-notification[55060]: [🡕] Process 2945 (wireplumber) crashed in _nl_load_domain.cold()
Subject: ABRT has detected unexpected termination: wireplumber
Defined-By: ABRT
Support: https://bugzilla.redhat.com/
Documentation: man:abrt(1)
wireplumber killed by SIGABRT
#1 [libc.so.6] _nl_load_domain.cold
#2 [libc.so.6] 81daba31ee66dbd63efdc4252a872949d874d136+218710
#3 [libasound.so.2] snd_mixer_elem_add
#4 [libspa-alsa.so] mixer_class_event
#5 [libasound.so.2] hctl_event_handler
Module libpcre2-8.so.0 with build-id 51cf2b0dc0884111cd6107b8b84bc1dc9e896de6
Metadata for module libpcre2-8.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "pcre2",
"version" : "10.40-1.fc37.1",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libffi.so.8 with build-id 56594b436dfdeaf3559f3dd0748c0e476cca46de
Metadata for module libffi.so.8 owned by FDO found: {
"type" : "rpm",
"name" : "libffi",
"version" : "3.4.4-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libgio-2.0.so.0 with build-id 67b6e34538841cb4a37f2627dac7626ec451d721
Metadata for module libgio-2.0.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "glib2",
"version" : "2.74.6-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libgmodule-2.0.so.0 with build-id ec8aa7c05708af8a1b0c56b828d88352a5c2bafc
Metadata for module libgmodule-2.0.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "glib2",
"version" : "2.74.6-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libc.so.6 with build-id 81daba31ee66dbd63efdc4252a872949d874d136
Module libgcc_s.so.1 with build-id bad96a3adc0a3a006e7ef4900ff3ae1ddcc33ed2
Module libpipewire-0.3.so.0 with build-id f6dd038300adbf1c8cef3a1946be042c70fe03bd
Metadata for module libpipewire-0.3.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "pipewire",
"version" : "0.3.69-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libglib-2.0.so.0 with build-id eac9203e396de94741ad9651644497c245a83ae8
Metadata for module libglib-2.0.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "glib2",
"version" : "2.74.6-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libgobject-2.0.so.0 with build-id dca95a679cf6bb8d7e3a9a2e239aa50b95026ceb
Metadata for module libgobject-2.0.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "glib2",
"version" : "2.74.6-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module libwireplumber-0.4.so.0 with build-id 96a2e6ae07de51ddada1f3fc1a634c1595d13fca
Metadata for module libwireplumber-0.4.so.0 owned by FDO found: {
"type" : "rpm",
"name" : "wireplumber",
"version" : "0.4.14-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Module wireplumber with build-id e710ebce923a74d6648e2a0990372e84e2af52fe
Metadata for module wireplumber owned by FDO found: {
"type" : "rpm",
"name" : "wireplumber",
"version" : "0.4.14-1.fc37",
"architecture" : "x86_64",
"osCpe" : "cpe:/o:fedoraproject:fedora:37"
}
Stack trace of thread 54924:
#0 0x00007f70ce6c6e5c __pthread_kill_implementation (libc.so.6 + 0x8ce5c)
#1 0x00007f70ce676a76 raise (libc.so.6 + 0x3ca76)
#2 0x00007f70ce6607fc abort (libc.so.6 + 0x267fc)
#3 0x00007f70ce66071b __assert_fail_base.cold (libc.so.6 + 0x2671b)
#4 0x00007f70ce66f656 __assert_fail (libc.so.6 + 0x35656)
#5 0x00007f70be59d1f3 snd_mixer_elem_add (libasound.so.2 + 0x741f3)
#6 0x00007f70be6a8851 mixer_class_event (libspa-alsa.so + 0x6f851)
#7 0x00007f70be58eeee hctl_event_handler (libasound.so.2 + 0x65eee)
#8 0x00007f70be59121d snd_hctl_load (libasound.so.2 + 0x6821d)
#9 0x00007f70be59d541 snd_mixer_load (libasound.so.2 + 0x74541)
#10 0x00007f70be6a8a90 pa_alsa_open_mixer_by_name (libspa-alsa.so + 0x6fa90)
#11 0x00007f70be6b5883 pa_alsa_open_mixer_for_pcm.constprop.0 (libspa-alsa.so + 0x7c883)
#12 0x00007f70be6b103e mapping_paths_probe.constprop.0 (libspa-alsa.so + 0x7803e)
#13 0x00007f70be6a32d4 pa_alsa_profile_set_probe (libspa-alsa.so + 0x6a2d4)
#14 0x00007f70be690d57 acp_card_new (libspa-alsa.so + 0x57d57)
#15 0x00007f70be667b9a impl_init.lto_priv.1 (libspa-alsa.so + 0x2eb9a)
#16 0x00007f70ce8ad0da load_spa_handle.lto_priv.0 (libpipewire-0.3.so.0 + 0x760da)
#17 0x00007f70ce8ad444 pw_load_spa_handle (libpipewire-0.3.so.0 + 0x76444)
#18 0x00007f70ce87f94c pw_context_load_spa_handle (libpipewire-0.3.so.0 + 0x4894c)
#19 0x00007f70ceae2508 wp_spa_device_new_from_spa_factory (libwireplumber-0.4.so.0 + 0x2a508)
#20 0x00007f70bf8b6867 spa_device_new (libwireplumber-module-lua-scripting.so + 0x15867)
#21 0x00007f70bf84d672 luaD_precall (liblua-5.4.so + 0x1a672)
#22 0x00007f70bf85fdf7 luaV_execute (liblua-5.4.so + 0x2cdf7)
#23 0x00007f70bf845a26 f_call (liblua-5.4.so + 0x12a26)
#24 0x00007f70bf849f13 luaD_rawrunprotected (liblua-5.4.so + 0x16f13)
#25 0x00007f70bf84b694 luaD_pcall (liblua-5.4.so + 0x18694)
#26 0x00007f70bf845af0 lua_pcallk (liblua-5.4.so + 0x12af0)
#27 0x00007f70bf8bc8e8 _wplua_pcall (libwireplumber-module-lua-scripting.so + 0x1b8e8)
#28 0x00007f70bf8bca1a _wplua_closure_marshal (libwireplumber-module-lua-scripting.so + 0x1ba1a)
#29 0x00007f70cea6c060 g_closure_invoke (libgobject-2.0.so.0 + 0x14060)
#30 0x00007f70cea98f66 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x40f66)
#31 0x00007f70cea894da g_signal_emit_valist (libgobject-2.0.so.0 + 0x314da)
#32 0x00007f70cea896f3 g_signal_emit (libgobject-2.0.so.0 + 0x316f3)
#33 0x00007f70cea76b04 g_object_dispatch_properties_changed.lto_priv.0 (libgobject-2.0.so.0 + 0x1eb04)
#34 0x00007f70cea7cf7f g_object_notify (libgobject-2.0.so.0 + 0x24f7f)
#35 0x00007f70bf88c3b3 on_acquire_transition_done (libwireplumber-module-reserve-device.so + 0x93b3)
#36 0x00007f70cea6c060 g_closure_invoke (libgobject-2.0.so.0 + 0x14060)
#37 0x00007f70ceafe4f8 wp_transition_return (libwireplumber-0.4.so.0 + 0x464f8)
#38 0x00007f70ceb07efb wp_transition_advance (libwireplumber-0.4.so.0 + 0x4fefb)
#39 0x00007f70bf88ba6c on_name_acquired (libwireplumber-module-reserve-device.so + 0x8a6c)
#40 0x00007f70ce568884 do_call.lto_priv.0 (libgio-2.0.so.0 + 0x107884)
#41 0x00007f70ce568aa8 on_name_lost_or_acquired (libgio-2.0.so.0 + 0x107aa8)
#42 0x00007f70ce55f55f emit_signal_instance_in_idle_cb (libgio-2.0.so.0 + 0xfe55f)
#43 0x00007f70ce96cc72 g_idle_dispatch (libglib-2.0.so.0 + 0x55c72)
#44 0x00007f70ce96dc7f g_main_context_dispatch (libglib-2.0.so.0 + 0x56c7f)
#45 0x00007f70ce9c4118 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xad118)
#46 0x00007f70ce96d24f g_main_loop_run (libglib-2.0.so.0 + 0x5624f)
#47 0x0000565079aead0c main (wireplumber + 0x2d0c)
#48 0x00007f70ce661510 __libc_start_call_main (libc.so.6 + 0x27510)
#49 0x00007f70ce6615c9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x275c9)
#50 0x0000565079aeafe5 _start (wireplumber + 0x2fe5)
Stack trace of thread 54927:
#0 0x00007f70ce746196 epoll_wait (libc.so.6 + 0x10c196)
#1 0x00007f70ceb53e48 impl_pollfd_wait (libspa-support.so + 0x17e48)
#2 0x00007f70ceb446db loop_iterate (libspa-support.so + 0x86db)
#3 0x00007f70ce87ea87 do_loop (libpipewire-0.3.so.0 + 0x47a87)
#4 0x00007f70ce6c512d start_thread (libc.so.6 + 0x8b12d)
#5 0x00007f70ce745d74 __clone (libc.so.6 + 0x10bd74)
Stack trace of thread 54931:
#0 0x00007f70ce73e92d syscall (libc.so.6 + 0x10492d)
#1 0x00007f70ce9bfde0 g_cond_wait_until (libglib-2.0.so.0 + 0xa8de0)
#2 0x00007f70ce93d451 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x26451)
#3 0x00007f70ce99cb0a g_thread_pool_thread_proxy.lto_priv.0 (libglib-2.0.so.0 + 0x85b0a)
#4 0x00007f70ce997982 g_thread_proxy (libglib-2.0.so.0 + 0x80982)
#5 0x00007f70ce6c512d start_thread (libc.so.6 + 0x8b12d)
#6 0x00007f70ce745d74 __clone (libc.so.6 + 0x10bd74)
Stack trace of thread 54930:
#0 0x00007f70ce73921f __poll (libc.so.6 + 0xff21f)
#1 0x00007f70ce9c408d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xad08d)
#2 0x00007f70ce96af00 g_main_context_iteration (libglib-2.0.so.0 + 0x53f00)
#3 0x00007f70ce96cb91 glib_worker_main (libglib-2.0.so.0 + 0x55b91)
#4 0x00007f70ce997982 g_thread_proxy (libglib-2.0.so.0 + 0x80982)
#5 0x00007f70ce6c512d start_thread (libc.so.6 + 0x8b12d)
#6 0x00007f70ce745d74 __clone (libc.so.6 + 0x10bd74)
Stack trace of thread 54932:
#0 0x00007f70ce73921f __poll (libc.so.6 + 0xff21f)
#1 0x00007f70ce9c408d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xad08d)
#2 0x00007f70ce96d24f g_main_loop_run (libglib-2.0.so.0 + 0x5624f)
#3 0x00007f70ce571eca gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0x110eca)
#4 0x00007f70ce997982 g_thread_proxy (libglib-2.0.so.0 + 0x80982)
#5 0x00007f70ce6c512d start_thread (libc.so.6 + 0x8b12d)
#6 0x00007f70ce745d74 __clone (libc.so.6 + 0x10bd74)
ELF object binary architecture: AMD x86-64
Subject: Process 54924 (wireplumber) dumped core
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Documentation: man:core(5)
Process 54924 (wireplumber) crashed and dumped core.
This usually indicates a programming error in the crashing program and
should be reported to its vendor as a bug.
```
pw-dump:[pwdump.log](/uploads/d3e1010e2a5d3bd082014105e89a3508/pwdump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3164spa logger enables stderr buffer2023-04-17T19:23:48ZChristian Spielbergerspa logger enables stderr buffer<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
- De...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
- Desktop Environment:
- Kernel version (`uname -r`):
## Description of Problem:
A pipewire client that calls `pw_init()` looses direct stderr feedback because `setlinebuf()` is called on `stderr` in `./spa/plugins/support/logger.c:358`.
Due to man page of `setlinebuf` by default `stderr` is always unbuffered.
We wrote a pipewire module for baresip. Another module called `stdio` enables stdin echo to stderr which does not work like expected if pipewire module is loaded. See the original report of the issue: https://github.com/baresip/baresip/pull/2439#issuecomment-1505080336
## Suggested Solution
```c
if (this->file != stderr)
setlinebuf(this->file);
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3163Frequent underruns with `disable-tsched` at lower latencies2023-04-16T11:59:58ZM BriarFrequent underruns with `disable-tsched` at lower latencies- PipeWire version (`pipewire --version`): 0.3.69
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Gnome
- Kernel version (`uname -r`): 6.2.11
## Description of Problem:
...- PipeWire version (`pipewire --version`): 0.3.69
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Gnome
- Kernel version (`uname -r`): 6.2.11
## Description of Problem:
When using the IRQ based scheduling, I get frequent underruns on my system when playing back anything with lower latency. I noticed that first with games on wine, which tend to end up with around 5ms of latency, but it's also reproducible with seemingly everything else, like e.g. mpv when using PIPEWIRE_LATENCY=256/48000.
I realize IRQ based scheduling is probably still WIP, and I have no good reason to use it in the first place, but I thought I should report this anyways.
## How Reproducible:
Always.
### Steps to Reproduce:
1. Enable IRQ based scheduling with `api.alsa.disable-tsched = true`
2. Play a video in mpv like: `PIPEWIRE_LATENCY=256/48000 mpv --ao=pipewire some_video.mp4`
3. Notice underruns being reported in `pw-top`
### Actual Results:
Frequent underruns.
### Expected Results:
No underruns, like with the default timer-based scheduling.
# Additional Info (as attachments):100:
- `pw-dump > pw-dump.log`: [pw-dump.txt](/uploads/83a1bb2169dc7710a8e38c32520a66eb/pw-dump.txt)
![Screenshot_from_2023-04-16_13-15-32](/uploads/b43ddeaa3f754697632525453a0af68a/Screenshot_from_2023-04-16_13-15-32.png)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3162USB DAC hifi said connected but there is sound2023-04-15T08:01:38ZJohan de SandeUSB DAC hifi said connected but there is soundUsing kubuntu 22.04 /2 pipewire is working but on mine yamaha hifi it said not connected but there is sound. ![IMG_20230415_095257_134](/uploads/8bad104e614369ec8932a03082183cdd/IMG_20230415_095257_134.jpg)This happened by an upgrade of ...Using kubuntu 22.04 /2 pipewire is working but on mine yamaha hifi it said not connected but there is sound. ![IMG_20230415_095257_134](/uploads/8bad104e614369ec8932a03082183cdd/IMG_20230415_095257_134.jpg)This happened by an upgrade of pipewire in November and the next after didn't change anything. Thats why i am asking it if this is an issue or do i need change some settings? Maybe it is an idea if there is an config tool.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3161filter-chain regression with 0.3.692023-04-16T16:39:32ZA Tfilter-chain regression with 0.3.69A filter-chain derived from sink-eq6.conf from the Pipewire examples works well on 0.3.68, but won't start on 0.3.69. Multiple errors are logged:
```
Apr 15 18:38:37 hostname systemd[1066]: Started PipeWire Multimedia Service.
Apr 15 18:...A filter-chain derived from sink-eq6.conf from the Pipewire examples works well on 0.3.68, but won't start on 0.3.69. Multiple errors are logged:
```
Apr 15 18:38:37 hostname systemd[1066]: Started PipeWire Multimedia Service.
Apr 15 18:39:21 hostname pipewire[4729]: mod.filter-chain: cannot create plugin instance: Invalid argument
Apr 15 18:39:21 hostname pipewire[4729]: pw.stream: 0x560422030d30: error can't start graph: Invalid argument
Apr 15 18:39:21 hostname pipewire[4729]: mod.filter-chain: cannot create plugin instance: Invalid argument
Apr 15 18:39:21 hostname pipewire[4729]: pw.node: (effect_input.hpeq-0) start node error -5: Input/output error
Apr 15 18:39:21 hostname pipewire[4729]: mod.client-node: node 0x56042206a440: start failed
Apr 15 18:39:21 hostname pipewire[4729]: pw.core: 0x560421fa5950: error -22 for resource 2: can't start graph: Invalid argument
Apr 15 18:39:21 hostname pipewire[4729]: mod.client-node: 0x5604221a5570: error seq:205 -22 (can't start graph: Invalid argument)
Apr 15 18:39:21 hostname pipewire[4729]: pw.core: 0x560421fa5950: error -22 for resource 2: can't start graph: Invalid argument
Apr 15 18:39:21 hostname pipewire[4729]: mod.client-node: 0x5604221a5570: error seq:215 -22 (can't start graph: Invalid argument)
Apr 15 18:39:21 hostname pipewire[4729]: pw.core: 0x560421fa5950: error -5 for resource 2: start failed
Apr 15 18:39:21 hostname pipewire[4729]: mod.client-node: 0x5604221a5570: error seq:215 -5 (start failed)
Apr 15 18:39:27 hostname pipewire[4729]: mod.filter-chain: cannot create plugin instance: Invalid argument
Apr 15 18:39:27 hostname pipewire[4729]: pw.node: (effect_input.hpeq-0) start node error -5: Input/output error
Apr 15 18:39:27 hostname pipewire[4729]: mod.client-node: node 0x56042206a440: start failed
Apr 15 18:39:27 hostname pipewire[4729]: pw.core: 0x560421fa5950: error -22 for resource 2: can't start graph: Invalid argument
Apr 15 18:39:27 hostname pipewire[4729]: mod.client-node: 0x5604221a5570: error seq:265 -22 (can't start graph: Invalid argument)
Apr 15 18:39:27 hostname pipewire[4729]: pw.core: 0x560421fa5950: error -5 for resource 2: start failed
Apr 15 18:39:27 hostname pipewire[4729]: mod.client-node: 0x5604221a5570: error seq:265 -5 (start failed)
Apr 15 18:39:29 hostname pipewire[4729]: mod.filter-chain: cannot create plugin instance: Invalid argument
Apr 15 18:39:29 hostname pipewire[4729]: pw.node: (effect_input.hpeq-0) start node error -5: Input/output error
Apr 15 18:39:29 hostname pipewire[4729]: mod.client-node: node 0x56042206a440: start failed
```
pw-top shows only one of two expected filter-chains (output, no input) and playback attempts result in accumulated errors. Interestingly the 7.1 virtual surround sound chains load.
I suspect this might be related to the biquad filter changes between 0.3.68 and 0.3.69. Downgrading to 0.3.68 works OK (Arch Linux packages).
P.S. Is it possible to add some of the filter-chain examples as regression tests before releasing a new version? The ones that don't require LADSPA filters should be easy-ish to test?