pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2022-10-10T15:44:19Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2696module-roc-sink/source mono stream2022-10-10T15:44:19ZJaroslav Škarvadamodule-roc-sink/source mono streamI need to mono stream to save some bandwidth. With the old PulseAudio module-rtp-send I just called it with the 'channels=1' parameter and it was mono stream.
With the ROC I tried:
$ pactl load-module module-remap-source source_name=my_...I need to mono stream to save some bandwidth. With the old PulseAudio module-rtp-send I just called it with the 'channels=1' parameter and it was mono stream.
With the ROC I tried:
$ pactl load-module module-remap-source source_name=my_source_mono master=my_source channels=1 channel_map=left master_channel_map=left
$ pactl load-module module-roc-sink sink_name=roc_sink remote_ip=192.168.1.2 remote_source_port=10001 remote_repair_port=10002 fec_code=disable
$ pactl load-module module-loopback source=my_source_mono sink=roc_sink latency_msec=100;
'my_source' is stereo source. This doesn't work. It's playing mess on the remote end and even caused the PipeWire to deadlock several times. Without the remap-source module and if the my_source is loopbacked to the roc_sink it works correctly, but it's streaming in stereo (the right channel is silent in my_source, so it's wasting bandwidth). I also tried front-left for the channels remapping, or dropping the remapping options, but the result was the same.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2695Unable to modify `device.icon_name` with WirePlumber after v0.3.542022-09-18T09:30:46ZGuilhermeUnable to modify `device.icon_name` with WirePlumber after v0.3.54- PipeWire version: 0.3.57
- Distribution and distribution version: Arch Linux
- Desktop Environment: GNOME 42.4
- Kernel version: 5.19.8-arch1-1
## Description of Problem:
After commit a31989b46d790ce14be8cb0899142dbe59d1fae9, any Wir...- PipeWire version: 0.3.57
- Distribution and distribution version: Arch Linux
- Desktop Environment: GNOME 42.4
- Kernel version: 5.19.8-arch1-1
## Description of Problem:
After commit a31989b46d790ce14be8cb0899142dbe59d1fae9, any WirePlumber rule that tries to modify the `device.icon_name` property (and maybe a few others?) is not applied anymore. I first [reported](https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/349) this on the WirePlumber repository, thinking it was a regression because this used to work previously. However, after further investigation, I was able to determine the real culprit.
## How Reproducible:
100%
### Steps to Reproduce:
1. Create the following WirePlumber rule in `~/.config/wireplumber/main.lua.d/99-change-device-icon.lua`:
```lua
custom_icon = {
matches = {
{
{ "node.name", "matches", "alsa_output.*"}
}
},
apply_properties = {
["device.icon_name"] = "audio-headset"
}
}
table.insert(alsa_monitor.rules, custom_icon)
```
2. Restart WirePlumber to apply the rule
### Actual Results:
Notice that the device icon in Pavucontrol is set to `audio-card-analog-pci` instead of `audio-headset`:
![Screenshot_from_2022-09-16_08-43-26](/uploads/e06642d83abf568138896f838870b313/Screenshot_from_2022-09-16_08-43-26.png)
```shell
$ pactl list sinks | grep device.icon_name
device.icon_name = "audio-card-analog-pci"
```
### Expected Results:
The device icon should've been set to `audio-headset`, like this:
![Screenshot_from_2022-09-16_08-42-48](/uploads/c2c3a85f92c23c63b466e3e3912c1707/Screenshot_from_2022-09-16_08-42-48.png)
```shell
$ pactl list sinks | grep device.icon_name
device.icon_name = "audio-headset"
```
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/8899d631c96e2d09b67dbfeb5e7b3894/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2694spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe - Fedora 36 ...2022-09-15T19:55:59Zlakotammspa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe - Fedora 36 and 37After a recent update to F36 (~3 days ago) the audio on my laptop started breaking if I opened sound settings before playing any sounds. The error disappeared after upgrade to F37 but reappeared once all packages were upgraded to the las...After a recent update to F36 (~3 days ago) the audio on my laptop started breaking if I opened sound settings before playing any sounds. The error disappeared after upgrade to F37 but reappeared once all packages were upgraded to the lasted version.
I attempted to clean install F37 and ended up with the same result - after install everything was fine, after full upgrade the error started appearing.
Version-Release number of selected component (if applicable):
I tested the error and confirmed it with several kernels (all the kernels tested):
5.19.8
5.19.7
5.19.2
pipewire version:
Compiled with libpipewire 0.3.57
Linked with libpipewire 0.3.57
How reproducible:
It does not work with every device. My laptop with a Skylake CPU running F37 does not suffer from this issue.
Steps to Reproduce:
1.Reboot
2.Login
3.Go straight to Sound settings and play a test sound from one of the speakers
Actual results:
There is no sound
Expected results:
Sound should be playing
Additional info:
Opening of the Sound settings can break the Audio also after other sounds have stopped playing.
Laptop: Inspiron 16 Plus 7620
DE: GNOME 43.rc
CPU: 12th Gen Intel i7-12700H
systemctl --user status pipewire.service
```
Sep 14 12:11:07 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
Sep 14 12:11:07 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
Sep 14 12:11:07 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
Sep 14 12:11:07 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
Sep 14 12:11:07 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
```
systemctl --user status wireplumber
```
Sep 14 12:10:22 fedora systemd[2005]: Started wireplumber.service - Multimedia Service Session Manager.
Sep 14 12:10:22 fedora wireplumber[2139]: Can't find xdg-portal: (null)
Sep 14 12:10:22 fedora wireplumber[2139]: found session bus but no portal
Sep 14 12:10:22 fedora wireplumber[2139]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Sep 14 12:10:22 fedora wireplumber[2139]: could not make thread 2181 realtime using RTKit: Permission denied
Sep 14 12:10:22 fedora wireplumber[2139]: Failed to set scheduler settings: Operation not permitted
Sep 14 12:10:22 fedora wireplumber[2139]: reserve-device plugin is not connected to D-Bus, disabling device reservation
Sep 14 12:10:22 fedora wireplumber[2139]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Sep 14 12:10:22 fedora wireplumber[2139]: PipeWire's libcamera SPA missing or broken. libcamera not supported.
```
journalctl is also spammed:
```
Sep 14 12:29:52 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
Sep 14 12:29:52 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
Sep 14 12:29:52 fedora pipewire[2138]: spa.alsa: hw:sofhdadsp: snd_pcm_avail after recover: Broken pipe
```
alsa.info.sh:
http://alsa-project.org/db/?f=68f2a6f9e9b66a3efe5c5b9b951cfdafee63583d
A link to Fedora's bug traker:
https://bugzilla.redhat.com/show_bug.cgi?id=2126722https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2693New AAC decoder support broke AptX codecs?2022-10-12T06:07:39ZKupper IchibaNew AAC decoder support broke AptX codecs?- PipeWire version (`pipewire --version`): Compiled with libpipewire 0.3.57 Linked with libpipewire 0.3.57
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora Linux 36 (Thirty Six)
- Desktop Environment...- PipeWire version (`pipewire --version`): Compiled with libpipewire 0.3.57 Linked with libpipewire 0.3.57
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora Linux 36 (Thirty Six)
- Desktop Environment: lxqt
- Kernel version (`uname -r`): 5.19.8-200.fc36.x86_64
- BlueZ version (`bluetoothctl --version`): bluetoothctl: 5.65
- `lsusb`: Bluetooth devices: Bus 003 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
```
# paste the output of "bluetoothctl devices" here
Device 22:22:33:29:9E:F0 G7
```
## Description of Problem:
The new AAC decoder seems to have caused some kind of issue with AptX support. With AAC enabled, I can only select between AAC and SBC, and with it disabled, only SBC. Previous versions of pipewire didn't have AAC and AptX/HD worked fine. Rolling back to 0.3.49 restores AptX again.
## How Reproducible:
100% of the time
### Steps to Reproduce:
1. Pair and connect my phone to bluetooth on the target machine with pipewire 0.3.57 and pipewire-codec-aptx. Doesn't matter if it's blueman or blueberry or bluetoothctl, same results.
2. Begin playing audio over A2DP from phone to PC.
### Actual Results:
If AAC is enabled (e: on the Linux machine in ["bluez5.codecs"]), you can choose between only AAC and SBC (e: on the Android phone). If it's disabled, only SBC.
### Expected Results:
AptX HD was available and the default in previous versions of pipewire.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2692module-echo-cancel: pw-native module seems to perform significantly poorer co...2023-01-07T12:00:22ZJost-Philipmodule-echo-cancel: pw-native module seems to perform significantly poorer compared to pulseaudio-module-echo-cancel with default settings?<!-- 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.57
Linked with libpipewire 0.3.57...<!-- 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.57
Linked with libpipewire 0.3.57
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
Arch Linux
- Desktop Environment:
Gnome
- Kernel version (`uname -r`):
Linux 5.19.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 05 Sep 2022 18:09:09 +0000 x86_64 GNU/Linux
## Description of Problem:
I recently switched over from PulseAudio to Pipewire and am aiming to use this box as a Software-DSP, as I already did with PulseAudio previously in a very similar setup (older PC, same peripheral hardware).
Among other things, it should act as a speakerphone for my mobile telephone connected via bluetooth.
### Goal/Rationale:
- Turn this setup into a Speakerphone which is convenient to use for me and sounds significantly better than just using your phone on speaker mode, and that is good enough for doing business calls
(Read: the person paying you for participating in these calls shall have no grounds to request you stop using it)
- for reasons beyond the scope of this report I need my general audio graph to run at 96KHz. module-echo-cancel may use different settings if required, when trying this I found giving it a different rate/quantum in the stream properties had no effect on the problem described
### Problem:
While the quality of error cancellation and noise suppression has always been exceptionally good with PulseAudio, when using PipeWire in a similar configuration with module-echo-cancel the performance of acoustic echo cancellation is too poor to be usable for business calls.
### Assumption:
since I don't see very many people complaining about this I suspect this might be related to my individual setup rather than the module itself, but have no way to verify or investigate further.
## What I am hoping for:
- from the documentation available here I gather that both PulseAudio and PipeWire are basically wrapping their modules around the same webRTC library, so I would expect performance/behavior to be similar in general?
- might there be additional parameters/setting/not-so-obvious tweaks I can try that will positively affect AEC performance with the PipeWire module?
## Relevant components available:
- very new computer based on Intel Core i5 12600T / 64GB DDR5 RAM / SSD storage (dedicated to doing audio)
- 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio via USB
- 1235:8201 Focusrite-Novation Scarlett 18i20 USB Studio audio device
- two identical professional XLR microphones sitting on the desk, directly connected to the Scarlett
- two identical professional Studio speakers sitting on same desk, directly connected to the same Scarlett
- Samsung Galaxy S21 5G mobile phone (stock firmware, no funny stuff, your basic generic bluetooth phone)
- Archlinux in stock configuration (if there is such a thing)
## How Reproducible:
always (test repeat count: 2)
### Steps to Reproduce:
1. install pipewire
2. configure server to use 96KHz / 256 for the graph
3. use module-loopback to create a virtual stereo source (the two microphones) and a virtual stereo sink (the two speakers) from the audio board
4. include native pipewire module-echo-cancel as per [documentation](https://docs.pipewire.org/page_module_echo_cancel.html)
5. change audio.channels to 2 in both the source and the sink configuration for module-echo-cancel because we want this to be stereo for applications supporting it, and we really have two physical microphones available (irrelevant for Bluetooth, relevant for other applications)
6. in pavucontrol / helvum, make sure the audio is routed correctly through the echo-cancel node for both inbound and outbound.
7. connect telephone to pipewire via Bluetooth and initiate a phone call with trusted far end
8. compare performance with that of a similar setup using native Pulseaudio and Pulseaudio's module-echo-cancel on an older PC but the same audio/bluetooth hardware.
### Actual Results:
- performance of echo cancellation is much inferior to the original PulseAudio setup (which was near-perfect). While still being better than having no echo cancellation at all, using the pipewire setup the echo is clearly audible for the far end, and hence using this setup is very irritating for the far end.
Performance of echo-cancellation is therefore not good enough for business calls. (Or any other production calls to non-IT-nerds for that matter).
### Expected Results:
+ performance of echo cancellation should be at least on par with older native PulseAudio module, preferably better (echo barely or not at all audible on the far end, experience for the far-end participant should be similar to when we are using good headphones).https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2691pipewire 0.3.57 segfault in libspa-audiomixer.so2022-11-09T11:00:27Zcrabbed halo ablutionpipewire 0.3.57 segfault in libspa-audiomixer.soOriginally [reported to wireplumber](https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/345) who referred me here.
While scrubbing through a video, wireplumber crashed:
```
Sep 09 14:47:19 saga.alfsgard.dk kernel: wireplumber...Originally [reported to wireplumber](https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/345) who referred me here.
While scrubbing through a video, wireplumber crashed:
```
Sep 09 14:47:19 saga.alfsgard.dk kernel: wireplumber[1575]: segfault at 7f0bc624901c ip 00007f0bb5998dd6 sp 00007f0bb7f391e0 error 4 in libspa-audiomixer.so[7f0bb598d000+17000]
```
bt from "coredumpctl debug wireplumber":
```
#0 0x00007f0bb5998dd6 in impl_node_process (object=0x55d97fb841c8) at ../pipewire-0.3.57/spa/plugins/audiomixer/mixer-dsp.c:706
#1 0x00007f0bc5fb4bef in process_node (data=0x55d97fbbd440) at ../pipewire-0.3.57/src/pipewire/impl-node.c:1088
#2 0x00007f0bc5fb3c58 in node_on_fd_events (source=<optimized out>) at ../pipewire-0.3.57/src/pipewire/impl-node.c:1148
#3 0x00007f0bc6268f2e in loop_iterate (object=0x55d97f84e148, timeout=-1) at ../pipewire-0.3.57/spa/plugins/support/loop.c:431
#4 0x00007f0bc5f8e48c in do_loop (user_data=0x55d97f84dff0) at ../pipewire-0.3.57/src/pipewire/data-loop.c:81
#5 0x00007f0bc5c8c6b3 in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007f0bc5d11810 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
```
Full coredumpctl output:
[coredumpctl.txt](/uploads/c430d378d49e80815c831b4f7deddddf/coredumpctl.txt)
see also: https://bugs.gentoo.org/869383https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2690Segfault on startup with tobii eye tracker 4c plugged in2022-09-20T08:52:56ZYorick van PeltSegfault on startup with tobii eye tracker 4c plugged in<!-- 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.56
- 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.56
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): NixOS 22.11 (Raccoon)
- Desktop Environment: sway
- Kernel version (`uname -r`): 5.18.19
## Description of Problem:
I have a Tobii Eyetracker 4C, since upgrading pipewire today this causes a segfault.
## How Reproducible:
Very reproducible, happens 100% of the time this device is plugged in.
### Steps to Reproduce:
1. Build with libcamera support
2. Plug in Tobii Eyetracker 4C
3. Start Pipewire
### Actual Results:
Pipewire segfaults.
### Expected Results:
Pipewire doesn't crash with this device plugged in.
# Additional Info (as attachments):
- [coredump.log](/uploads/605af39817608a8d933edfd6021abd1a/coredump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2686Error loading libpipewire-module-filter-chain2022-11-05T09:46:28ZHendrik SchröterError loading libpipewire-module-filter-chain<!-- 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.57
Linked with libpipewire 0.3.57
- 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.57
Linked with libpipewire 0.3.57
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora Linux 36 (Workstation Edition)
- Desktop Environment: Sway (wayland)
- Kernel version (`uname -r`): 5.19.8-200.fc36.x86_64
## Description of Problem:
Loading a filter chain module results in the following error:
```bash
$ pipewire -c filter-chain/source-rnnoise.conf
[E][02860.152809] pw.core | [ core.c: 382 core_new()] 0x560ed7845420: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
[E][02860.153119] mod.filter-chain | [module-filter-ch: 2235 pipewire__module_init()] can't connect: Operation not supported
[E][02860.154409] pw.conf | [ conf.c: 594 load_module()] 0x560ed7811790: could not load mandatory module "libpipewire-module-filter-chain": Operation not supported
[E][02860.154783] default | [ pipewire.c: 125 main()] failed to create context: Operation not supported
```
### Steps to Reproduce:
All libs should be installed:
```bash
$ ll ~/.local/lib/librnnoise_ladspa.so
.rw-r--r--. hendrik hendrik 175 KB Thu Jul 28 15:52:05 2022 /home/hendrik/.local/lib/librnnoise_ladspa.so
$ ll /usr/lib64/pipewire-0.3/
drwxr-xr-x. root root 216 B Sat Sep 10 09:10:46 2022 jack
.rwxr-xr-x. root root 24 KB Fri Sep 2 12:14:25 2022 libpipewire-module-access.so
.rwxr-xr-x. root root 144 KB Fri Sep 2 12:14:25 2022 libpipewire-module-adapter.so
.rwxr-xr-x. root root 101 KB Fri Sep 2 12:14:25 2022 libpipewire-module-avb.so
.rwxr-xr-x. root root 56 KB Fri Sep 2 12:14:25 2022 libpipewire-module-client-device.so
.rwxr-xr-x. root root 270 KB Fri Sep 2 12:14:25 2022 libpipewire-module-client-node.so
.rwxr-xr-x. root root 64 KB Fri Sep 2 12:14:25 2022 libpipewire-module-echo-cancel.so
.rwxr-xr-x. root root 20 KB Fri Sep 2 12:14:25 2022 libpipewire-module-fallback-sink.so
.rwxr-xr-x. root root 179 KB Fri Sep 2 12:14:25 2022 libpipewire-module-filter-chain.so
.rwxr-xr-x. root root 24 KB Fri Sep 2 12:14:25 2022 libpipewire-module-link-factory.so
.rwxr-xr-x. root root 52 KB Fri Sep 2 12:14:25 2022 libpipewire-module-loopback.so
.rwxr-xr-x. root root 48 KB Fri Sep 2 12:14:25 2022 libpipewire-module-metadata.so
.rwxr-xr-x. root root 88 KB Fri Sep 2 12:14:25 2022 libpipewire-module-pipe-tunnel.so
.rwxr-xr-x. root root 24 KB Fri Sep 2 12:14:25 2022 libpipewire-module-portal.so
.rwxr-xr-x. root root 56 KB Fri Sep 2 12:14:25 2022 libpipewire-module-profiler.so
.rwxr-xr-x. root root 310 KB Fri Sep 2 12:14:25 2022 libpipewire-module-protocol-native.so
.rwxr-xr-x. root root 415 KB Fri Sep 2 12:14:25 2022 libpipewire-module-protocol-pulse.so
.rwxr-xr-x. root root 60 KB Fri Sep 2 12:14:25 2022 libpipewire-module-protocol-simple.so
.rwxr-xr-x. root root 64 KB Fri Sep 2 12:14:25 2022 libpipewire-module-pulse-tunnel.so
.rwxr-xr-x. root root 24 KB Fri Sep 2 12:14:25 2022 libpipewire-module-raop-discover.so
.rwxr-xr-x. root root 80 KB Fri Sep 2 12:14:25 2022 libpipewire-module-raop-sink.so
.rwxr-xr-x. root root 32 KB Fri Sep 2 12:14:25 2022 libpipewire-module-rt.so
.rwxr-xr-x. root root 32 KB Fri Sep 2 12:14:25 2022 libpipewire-module-rtkit.so
.rwxr-xr-x. root root 195 KB Fri Sep 2 12:14:25 2022 libpipewire-module-session-manager.so
.rwxr-xr-x. root root 24 KB Fri Sep 2 12:14:25 2022 libpipewire-module-spa-device-factory.so
.rwxr-xr-x. root root 16 KB Fri Sep 2 12:14:25 2022 libpipewire-module-spa-device.so
.rwxr-xr-x. root root 80 KB Fri Sep 2 12:14:25 2022 libpipewire-module-spa-node-factory.so
.rwxr-xr-x. root root 68 KB Fri Sep 2 12:14:25 2022 libpipewire-module-spa-node.so
.rwxr-xr-x. root root 24 KB Fri Sep 2 12:14:25 2022 libpipewire-module-x11-bell.so
.rwxr-xr-x. root root 44 KB Fri Sep 2 12:14:25 2022 libpipewire-module-zeroconf-discover.so
$ cat /usr/share/pipewire/filter-chain/source-rnnoise.conf
# Noise canceling source
#
# Copy this file into a conf.d/ directory such as
# ~/.config/pipewire/filter-chain.conf.d/
#
context.modules = [
{ name = libpipewire-module-filter-chain
args = {
node.description = "Noise Canceling source"
media.name = "Noise Canceling source"
filter.graph = {
nodes = [
{
type = ladspa
name = rnnoise
plugin = librnnoise_ladspa
label = noise_suppressor_stereo
control = {
"VAD Threshold (%)" 50.0
}
}
]
}
audio.position = [ FL FR ]
capture.props = {
node.name = "effect_input.rnnoise"
node.passive = true
}
playback.props = {
node.name = "effect_output.rnnoise"
media.class = Audio/Source
}
}
}
]
```
### Expected Results:
Pipewire finds the context module `libpipewire-module-filter-chain` and loads the ladsap rnnoise lib.
# Additional Info (as attachments):
- systemd service:
```bash
$ systemctl --user status pipewire-pulse
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled)
Active: active (running) since Tue 2022-09-13 09:29:26 CEST; 3min 30s ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 42868 (pipewire-pulse)
Tasks: 2 (limit: 19016)
Memory: 1.9M
CPU: 34ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─ 42868 /usr/bin/pipewire-pulse
Sep 13 09:29:26 T480s systemd[1914]: Started pipewire-pulse.service - PipeWire PulseAudio.
Sep 13 09:29:36 T480s pipewire-pulse[42868]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Sep 13 09:29:36 T480s pipewire-pulse[42868]: mod.rt: could not make thread 43003 realtime using RTKit: Permission denied
Sep 13 09:29:36 T480s pipewire-pulse[43002]: 536870912
$ systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/user/pipewire.service.d
└─00-uresourced.conf
Active: active (running) since Tue 2022-09-13 09:29:26 CEST; 3min 32s ago
TriggeredBy: ● pipewire.socket
Main PID: 42866 (pipewire)
Tasks: 2 (limit: 19016)
Memory: 5.2M
CPU: 73ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─ 42866 /usr/bin/pipewire
Sep 13 09:29:26 T480s systemd[1914]: Started pipewire.service - PipeWire Multimedia Service.
Sep 13 09:29:36 T480s pipewire[42866]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Sep 13 09:29:36 T480s pipewire[42866]: mod.rt: could not make thread 42998 realtime using RTKit: Permission denied
```
- `pw-dump.log`: [link](/uploads/ec3421ff46c3b6a8c0bb58fd9aeb5523/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2685Volume Normalizing through filter chain doesnt work2022-09-12T07:51:47ZBigFGVolume Normalizing through filter chain doesnt work- PipeWire version: libpipewire 0.3.57
- Distribution: Arch Linux
- Desktop Environment: Gnome 42.4
- Kernel version: 5.19.7-zen2-1-zen
## Description of Problem:
When attempting to setup Volume Normalizing through a filter chain it cr...- PipeWire version: libpipewire 0.3.57
- Distribution: Arch Linux
- Desktop Environment: Gnome 42.4
- Kernel version: 5.19.7-zen2-1-zen
## Description of Problem:
When attempting to setup Volume Normalizing through a filter chain it creates the Sink but the Sink does nothing
When adding this to the pipewire-pulse.conf context.exec = [ or running from terminal the associated commands it works as expected
```
{ path = "pactl" args = "load-module module-ladspa-sink sink_name=Normalizer master=alsa_output.usb-MOTU_M4_M40000066088-00.HiFi__m4_stereo_out_M4_0_2_3__sink plugin=sc4_1882 label=sc4 control=1,1.5,401,-12,6,5,12" }
{ path = "pactl" args = "load-module module-ladspa-sink sink_name=Normalized master=Normalizer plugin=fast_lookahead_limiter_1913 label=fastLookaheadLimiter control=5,-10,0.8" }
```
Pipewire doesnt give me any complaints about it just nothing happens when i set it up through a filter chain.
## How to Reproduce:
put normalize.conf in filter-chain.conf.d
normalize.conf contains this with node.target set to appropriate output or possibly removed (may not be needed for some?)
```
context.modules = [
{ name = libpipewire-module-filter-chain
args = {
node.description = "Normalize Sink"
media.name = "Normalize Sink"
filter.graph = {
nodes = [
{
type = ladspa
name = sc4
plugin = sc4_1882
label = sc4
control = { "RMS/peak" = 1 "Attack time (ms)" = 1.5 "Release time (ms)" = 401 "Threshold level (db)" = -12 "Ratio (1:n)" = 6 "Knee radius (db)" = 5 "Makeup gain (db)" = 12 }
}
{
type = ladspa
name = limiter
plugin = fast_lookahead_limiter_1913
label = fastLookaheadLimiter
control = { "Input gain (db)" = 5 "Limit (db)" = -10 "Release time (s)" = 0.8 }
}
]
links = [
{ output = "sc4:Left output" input = "limiter:Input 1" }
{ output = "sc4:Right output" input = "limiter:Input 2" }
]
inputs = [ "sc4:Left input" "sc4:Right input"]
outputs = [ "limiter:Output 1" "limiter:Output 2" ]
}
capture.props = {
node.name = "effect_input.normalize"
media.class = "Audio/Sink"
audio.channels = 2
audio.position = [ FL FR ]
}
playback.props = {
node.name = "effect_output.normalize"
node.passive = true
audio.channels = 2
audio.position = [ FL FR ]
node.target = "alsa_output.usb-MOTU_M4_M40000066088-00.HiFi__m4_stereo_out_M4_0_2_3__sink"
}
}
}
]
```
set audio output sink to the Normalize Sink and play sound to test output
### Actual Results:
Audio will play, but fails to normalize/process the audio and simply works exactly like setting the normal output sink with no change
### Expected Results:
Audio gets normalizedhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2682module-profiler/pw-top ERR with node in different process is probably spurious2023-04-30T12:29:59ZP Vmodule-profiler/pw-top ERR with node in different process is probably spuriousI've been looking at why Bluetooth nodes rack up the ERR count in pw-top. This seems to be because impl-node.c:process_node does not wait for the remote driver node async return to complete before emitting the `complete` event, so that p...I've been looking at why Bluetooth nodes rack up the ERR count in pw-top. This seems to be because impl-node.c:process_node does not wait for the remote driver node async return to complete before emitting the `complete` event, so that profiling data sometimes gets recorded at the same time as the remote node is still processing. I think this doesn't occur with ALSA nodes just because they run in the server process, so the process call is not async, and always completes first.
With some added debug (https://gitlab.freedesktop.org/pvir/pipewire/-/commits/bt-err-debug), things look like this:
```
# pipewire server process
[T][13:56:42.896603] pw.node | [ impl-node.c: 1624 node_ready()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): ready driver:1 exported:0 0x61d0
00028a80 status:2
[T][13:56:42.896624] pw.node | [ impl-node.c: 1054 resume_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): trigger peers 9614896808539
[T][13:56:42.896636] pw.node | [ impl-node.c: 1060 resume_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): state:0x7f1edc4e8008 pending:4/
4
[T][13:56:42.896649] pw.node | [ impl-node.c: 1060 resume_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): state:0x7f1edc4e8008 pending:3/
4
[T][13:56:42.896661] pw.node | [ impl-node.c: 1060 resume_node()] 0x61d00002b280 (pw-play): state:0x7f1edbe2e008 pending:1/1
[D][13:56:42.896672] pw.node | [ impl-node.c: 1093 process_node()] 0x61d00002b280 (pw-play) awaken for process
[T][13:56:42.896682] pw.node | [ impl-node.c: 1105 process_node()] 0x61d00002b280 (pw-play): process 9614896867028
[T][13:56:42.896694][ client-node.c: 932 impl_node_process()] 0x617000002720: send process driver:0x61d000028a80
[T][13:56:42.896708][ client-node.c: 943 impl_node_process()] 0x617000002720: send process async return
[T][13:56:42.896717] pw.node | [ impl-node.c: 1116 process_node()] 0x61d00002b280 (pw-play): process returns 0
[T][13:56:42.896727] pw.node | [ impl-node.c: 1145 process_node()] 0x61d00002b280: async continue
[D][13:56:42.896815] pw.node | [ impl-node.c: 1093 process_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit) awaken for process
[T][13:56:42.896827] pw.node | [ impl-node.c: 1105 process_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): process 9614897011672
[T][13:56:42.896842][ client-node.c: 932 impl_node_process()] 0x6170000023a0: send process driver:0x61d000028a80
[T][13:56:42.896857][ client-node.c: 943 impl_node_process()] 0x6170000023a0: send process async return
[T][13:56:42.896869] pw.node | [ impl-node.c: 1116 process_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): process returns 0
[T][13:56:42.896890] pw.node | [ impl-node.c: 1132 process_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): graph completed wait:203133 run:62445 busy:265578 period:81838 cpu:4,270493:5,083025:5,204981 status:3
[T][13:56:42.896905] mod.profiler | [module-profiler.: 199 context_do_profile()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): do profile status:2
[T][13:56:42.896931] pw.node | [ impl-node.c: 1143 process_node()] 0x61d000028a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): driver emit complete done
# at the same time, in wireplumber:
D 13:56:42.896504 spa.bluez5.sink.sc ../spa/plugins/bluez5/sco-sink.c:611:sco_on_timeout: 0x623000016d28: timer 9614896644587 42666666
T 13:56:42.896528 spa.bluez5.sink.sc ../spa/plugins/bluez5/sco-sink.c:633:sco_on_timeout: 0x623000016d28: 0
T 13:56:42.896537 mod.client-node ../src/modules/module-client-node/remote-node.c:1189:node_ready: node 0x61d000663a80: ready driver:1 exported:1 status:1
D 13:56:42.896888 pw.node ../src/pipewire/impl-node.c:1093:process_node: 0x61d000663a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit) awaken for process
T 13:56:42.896902 pw.node ../src/pipewire/impl-node.c:1105:process_node: 0x61d000663a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): process 9614897084080
T 13:56:42.897047 spa.bluez5.sink.sc ../spa/plugins/bluez5/sco-sink.c:1259:impl_node_process: 0x623000016d28: queue buffer 0
T 13:56:42.897057 spa.bluez5.sink.sc ../spa/plugins/bluez5/sco-sink.c:1282:impl_node_process: 0x623000016d28: flush on process
T 13:56:42.897072 spa.bluez5.sink.sc ../spa/plugins/bluez5/sco-sink.c:526:flush_data: 0x623000016d28: send wrote:60 dt:9902009
T 13:56:42.897079 spa.bluez5.sink.sc ../spa/plugins/bluez5/sco-sink.c:531:flush_data: write socket data 60
T 13:56:42.897088 pw.node ../src/pipewire/impl-node.c:1116:process_node: 0x61d000663a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): process returns 3
T 13:56:42.897095 pw.node ../src/pipewire/impl-node.c:1054:resume_node: 0x61d000663a80 (bluez_output.00_00_AB_CD_7A_DE.headset-head-unit): trigger peers 9614897278496
```
Profiler recording data with activation status 2 here triggers ERR count increase in pw-top. It changed from 3 to 2 during `pw_context_driver_emit_complete`, apparently since the flag is on shared memory, and was changed due to the node in the remote process awakening for the async process call.
Probably it should somehow wait for the remote driver node to complete processing, before emitting the driver complete event.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2681Compilation of 32-bit build is broken2022-09-15T08:05:45ZSergey KondakovCompilation of 32-bit build is brokenRecently 32-bit compilation broke with:
```
[ 168s] ../spa/plugins/audioconvert/resample-peaks-sse.c:44:31: warning: implicit declaration of function '_mm_set1_epi32' is invalid in C99 [-Wimplicit-function-declaration]
[ 168s] ...Recently 32-bit compilation broke with:
```
[ 168s] ../spa/plugins/audioconvert/resample-peaks-sse.c:44:31: warning: implicit declaration of function '_mm_set1_epi32' is invalid in C99 [-Wimplicit-function-declaration]
[ 168s] const __m128 mask = (__m128) _mm_set1_epi32(0x7fffffff);
[ 168s] ^
[ 168s] ../spa/plugins/audioconvert/resample-peaks-sse.c:44:22: error: invalid conversion between vector type '__m128' (vector of 4 'float' values) and integer type 'int' of different size
[ 168s] const __m128 mask = (__m128) _mm_set1_epi32(0x7fffffff);
[ 168s] ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 168s] 1 warning and 1 error generated.
```
Probably due to a7c28d64ae272198b8f6581c9e8f745f9125b15ehttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2679setting realtime still doesn't work with master and rtkit2022-09-09T09:29:06ZJan Sieber-Taegertsetting realtime still doesn't work with master and rtkit<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version: git master up to commit #853a1c0b (module-rt: Fix setting realtime priority with rtkit)
- Distribution and ...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version: git master up to commit #853a1c0b (module-rt: Fix setting realtime priority with rtkit)
- Distribution and distribution version: Debian GNU/Linux 11 (bullseye)
- Desktop Environment: GNOME 3.38.5
- Kernel version: 5.18.0-0.deb11.3-amd64
## Description of Problem:
Since release 0.3.57 setting realtime permissions and nice level with rtkit doesn't work anymore.
Commit [853a1c0b](https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/853a1c0ba8c98f84f1afa902efc97eb7d72f9095) haven't brought any improvement here.
## How Reproducible:
Compile pipewire master and restart
### Actual Results:
```
mod.rt: RTKit error: org.freedesktop.DBus.Error.UnknownMethod
Sep 09 10:53:29 debian pipewire[599522]: mod.rt: could not set nice-level to -11: Eingabe-/Ausgabefehler
Sep 09 10:53:29 debian pipewire[599522]: mod.rt: RTKit error: org.freedesktop.DBus.Error.InvalidArgs
Sep 09 10:53:29 debian pipewire[599522]: mod.rt: RTKit error: org.freedesktop.DBus.Error.InvalidArgs
Sep 09 10:53:29 debian pipewire[599522]: mod.rt: RTKit error: org.freedesktop.DBus.Error.UnknownMethod
Sep 09 10:53:29 debian pipewire[599522]: mod.rt: could not make thread 599535 realtime using RTKit: Eingabe-/Ausgabefehler
Sep 09 10:53:29 debian pipewire-pulse[599524]: mod.rt: RTKit error: org.freedesktop.DBus.Error.UnknownMethod
Sep 09 10:53:29 debian pipewire-pulse[599524]: mod.rt: could not set nice-level to -11: Eingabe-/Ausgabefehler
Sep 09 10:53:29 debian pipewire-pulse[599524]: mod.rt: RTKit error: org.freedesktop.DBus.Error.InvalidArgs
Sep 09 10:53:29 debian pipewire-pulse[599524]: mod.rt: RTKit error: org.freedesktop.DBus.Error.InvalidArgs
Sep 09 10:53:29 debian pipewire-pulse[599524]: mod.rt: RTKit error: org.freedesktop.DBus.Error.UnknownMethod
Sep 09 10:53:29 debian pipewire-pulse[599524]: mod.rt: could not make thread 599542 realtime using RTKit: Eingabe-/Ausgabefehler
```
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/bd22d0f92ab71ed336eae293a6961114/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2678Microphone from bluetooth headset always silent2022-09-14T09:26:44ZJaumeMicrophone from bluetooth headset always silent<!-- 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....<!-- 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.57`
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Sway
- Kernel version (`uname -r`): `5.19.7`
- BlueZ version (`bluetoothctl --version`): `5.65`
- `lsusb`:
```
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
Bus 001 Device 003: ID 04d9:a0d1 Holtek Semiconductor, Inc. Varmilo Keyboard
Bus 001 Device 002: ID 145f:026d Trust GXT 144 Gaming Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
- Bluetooth devices:
```
Device 00:18:09:65:FB:78 MDR-ZX330BT
Device F8:4E:17:50:B6:C2 WH-1000XM3
```
## Description of Problem:
The bluetooth headsets are connected correctly and can listen to audio in A2DP mode. When I try to use it in a meeting in Firefox it switches automatically to HSP/HFP but it's always silent. I tried both CVSD and mSBC codecs but no one records any sound.
## How Reproducible:
Connect bluettoth headset and try to record audio with them.
### Steps to Reproduce:
1.
2.
3.
### Actual Results:
No audio coming from microphone.
### Expected Results:
Audio coming from microphone.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
- Bluetooth debug log, see [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth):https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2677SIGSEGV When Creating a Loopback with Helvum2022-09-18T14:43:04ZRotationMatrixSIGSEGV When Creating a Loopback with HelvumPlease let me know if I've missed something or there is other information which would be useful. I also installed master to test for this crash but ran into RTKit errors which I'm sorting out.
- PipeWire version (`pipewire --version`): ...Please let me know if I've missed something or there is other information which would be useful. I also installed master to test for this crash but ran into RTKit errors which I'm sorting out.
- PipeWire version (`pipewire --version`): 0.3.57
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): EndeavourOS
- Desktop Environment: KDE Plasma
- Kernel version (`uname -r`): 5.19.7-arch1-1
## Description of Problem:
Pipewire gets a SIGSEGV when I try to send audio from my headphones playback monitor to my display playback.
## How Reproducible:
About 90% of the time with the steps below. Only 60% of the time after a fresh boot if I skip step one. I cannot reproduce after it has crashed without running step 1 (even if systemd already restarted Pipewire).
### Steps to Reproduce:
1. `systemctl --user restart pipewire`.
2. Launch an application to play audio like VLC.
3. Launch Helvum. A portion of the graph should look like:
```mermaid
flowchart LR
vlc --> playback_headphones
subgraph headphones
playback_headphones[playback]
monitor_headphones[monitor]
end
subgraph display
playback_display[playback]
end
```
4. Complete the connection from the headphones `monitor` to the display `playback`.
```mermaid
flowchart LR
vlc --> playback_headphones
monitor_headphones --> playback_display
subgraph headphones
playback_headphones[playback]
monitor_headphones[monitor]
end
subgraph display
playback_display[playback]
end
```
### Actual Results:
Pipewire receives a SIGSEGV (usually on Thread 2).
# Additional Info (as attachments):
- `bt full`: [pipewire-trace.log](/uploads/132d9d9c5a2e96238306a649cbba1f9a/pipewire-trace.log)
- `info reg`: [pipewire-info-reg.log](/uploads/d1e11be9e8479bce8352d69b73efc8ac/pipewire-info-reg.log)
- Triggering the crash under gdb prints `Thread 2 "pipewire" received signal SIGSEGV, Segmentation fault.`https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2674RuneLite music stutters on PipeWire2022-09-08T07:17:24ZStéphane TravostinoRuneLite music stutters on PipeWireRuneLite's music stutters with pipewire, background audio is fine. It's running on top of Java and appears as an ALSA plugin.
(NB: I'm testing in flatpak for reproducibility)
I've tried the latest OpenJDK version with the latest freede...RuneLite's music stutters with pipewire, background audio is fine. It's running on top of Java and appears as an ALSA plugin.
(NB: I'm testing in flatpak for reproducibility)
I've tried the latest OpenJDK version with the latest freedesktop SDK, and it's still causing issues, and I'm beginning to wonder if it's a pipewire problem.
## Steps to reproduce
1. `flatpak install net.runelite.RuneLite`
2. `flatpak run net.runelite.RuneLite`
3. Wait a few seconds for the music to start
4. Music stops and restarts every ~2 seconds
OS: Fedora Silverblue 36https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2673No output on Airplay device (raop-sink)2023-05-25T06:42:45ZGhost UserNo output on Airplay device (raop-sink)## Configuration
* PipeWire version (`pipewire --version`): 0.3.56
* Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Debian GNU/Linux bookworm/sid
* Desktop Environment: GNOME 42.4
* Kernel version (`unam...## Configuration
* PipeWire version (`pipewire --version`): 0.3.56
* Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Debian GNU/Linux bookworm/sid
* Desktop Environment: GNOME 42.4
* Kernel version (`uname -r`): 5.18.0-4-amd64
## Description of the problem
I cannot say exactly which version introduced the probelm since there were multiple updates while I was traveling, but at some point playback to my Airplay device, which worked fine before, got broken. From the application it looks as if everything is playing fine, but there is in fact no output on the device. I increased the log level in my pipewire config and include below what I believe is the relevant part of the log.
Immediately after I start playback, the raop-sink changes states to "disconnected". I suspect the "binary response received" just before may have something do with it, but I am not sure.
```
Sep 4 10:13:34 lucre pipewire[48526]: mod.raop-discover: loading module args:'{ "raop.hostname": "192.168.86.33", "raop.port": 1025, "node.description": "Piano", "audio.channels": 2, "raop.audio.codec": "PCM", "raop.encryption.type": "auth_setup", "audio.rate": 44100, "audio.format": "S16", "raop.transport": "udp", "device.model": "XW-SMA3" stream.props = { }}'
...
Sep 4 10:13:34 lucre pipewire[48526]: pw.node: (raop-sink-48526-86-0) latency:0/0 -> 352/44100
Sep 4 10:13:34 lucre pipewire[48526]: pw.node: (raop-sink-48526-86-0) creating -> suspended
...
Sep 4 10:20:04 lucre pipewire[49509]: pw.node: (Clementine-91) suspended -> running
Sep 4 10:20:04 lucre pipewire[49509]: pw.node: (raop-sink-49509-80-0) idle -> running
Sep 4 10:20:04 lucre pipewire[49509]: pw.node: (raop-sink-49509-80-82) suspended -> running
Sep 4 10:20:04 lucre pipewire[49509]: default: status: RTSP/1.0 200 OK
Sep 4 10:20:04 lucre pipewire[49509]: default: Public: ANNOUNCE, SETUP, RECORD, PAUSE, FLUSH, TEARDOWN, OPTIONS, GET_PARAMETER, SET_PARAMETER, POST, GET
Sep 4 10:20:04 lucre pipewire[49509]: default: Server: AirTunes/103.2
Sep 4 10:20:04 lucre pipewire[49509]: default: CSeq: 1
Sep 4 10:20:04 lucre pipewire[49509]: mod.raop-sink: options 200
Sep 4 10:20:04 lucre pipewire[49509]: default: sent: POST /auth-setup RTSP/1.0#015#012CSeq: 2#015#012Client-Instance: 569b7fd079b1eb75#015#012Apple-Challenge: KWqQtP4u+kcdrqzYBHXHrg#015#012User-Agent: iTunes/11.0.4 (Windows; N)#015#012Content-Type: application/octet-stream#015#012Content-Length: 33#015#012#015#012#001Y#002��#015N�L��c0#003�#007�M�PتF[]�#001*#014~#035N
Sep 4 10:20:06 lucre pipewire[49509]: default: status: RTSP/1.0 200 OK
Sep 4 10:20:06 lucre pipewire[49509]: default: Content-Type: application/octet-stream
Sep 4 10:20:06 lucre pipewire[49509]: default: Content-Length: 1078
Sep 4 10:20:06 lucre pipewire[49509]: default: Server: AirTunes/103.2
Sep 4 10:20:06 lucre pipewire[49509]: default: CSeq: 2
Sep 4 10:20:06 lucre pipewire[49509]: default: binary response received
Sep 4 10:20:06 lucre pipewire[49509]: mod.raop-sink: disconnected
Sep 4 10:20:40 lucre pipewire[49509]: pw.context: 0x5625403ed6a0: busy:0 reason:node deactivate
Sep 4 10:20:40 lucre pipewire[49509]: pw.node: (raop-sink-49509-80-82) -> change driver (Dummy-Driver-29 -> raop-sink-49509-80-82)
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.0 -> 82.0) deactivated
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.0 -> 82.0) active -> paused
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.1 -> 82.1) deactivated
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.1 -> 82.1) active -> paused
Sep 4 10:20:40 lucre pipewire[49509]: pw.node: (Clementine-91) client too slow! rate:256/48000 pos:1720320 status:triggered
Sep 4 10:20:40 lucre pipewire[49509]: pw.node: (Clementine-91) -> change driver (Dummy-Driver-29 -> Clementine-91)
Sep 4 10:20:40 lucre pipewire[49509]: pw.node: (Clementine-91) destroy
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.0 -> 82.0) paused -> init
Sep 4 10:20:40 lucre pipewire[49509]: pw.context: 0x5625403ed6a0: busy:0 reason:link unprepared
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.1 -> 82.1) paused -> init
Sep 4 10:20:40 lucre pipewire[49509]: pw.context: 0x5625403ed6a0: busy:0 reason:link unprepared
Sep 4 10:20:40 lucre pipewire[49509]: pw.node: (Clementine-91) running -> suspended
Sep 4 10:20:40 lucre pipewire[49509]: pw.link: (91.0 -> 82.0) destroy
```
Please let me know in case you need more information. I suppose I could increase the log level even further.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2671Crackling sound on 0.3.572022-10-12T08:43:00ZGrzegorz AlibożekCrackling sound on 0.3.57<!-- 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.57
- 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.57
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Plasma
- Kernel version (`uname -r`): 5.19.6-arch1-1
## Description of Problem:
After upgrade from 0.3.56 to 0.3.57 the sound crackling / crashes / crackles when pavucontrol or other sound applet is running
## How Reproducible:
### Steps to Reproduce:
1. Run sound
2. Run pavucontrol
### Actual Results:
### Expected Results:
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2670compilation failed on ubuntu 18.04 with PW master 3f6fe392090dd4c87e9c103676e...2022-09-03T09:11:28ZSourav Dassouravdas142@gmail.comcompilation failed on ubuntu 18.04 with PW master 3f6fe392090dd4c87e9c103676e9d9d56d5a15fc```bash
[488/785] cc -Isrc/modules/libpipewire-module-filter-chain.so.p -Isrc/modules -I../src/modules -I. -I.. -Isrc -I../src -Ispa/include -I../spa/include -I/usr/include/sratom-0 -I/usr/include/sord-0 -I/usr/include/serd-0 -I/usr/inc...```bash
[488/785] cc -Isrc/modules/libpipewire-module-filter-chain.so.p -Isrc/modules -I../src/modules -I. -I.. -Isrc -I../src -Ispa/include -I../spa/include -I/usr/include/sratom-0 -I/usr/include/sord-0 -I/usr/include/serd-0 -I/usr/include/lilv-0 -flto=4 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu99 -fvisibility=hidden -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 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o -MF src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o.d -o src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o -c ../src/modules/module-filter-chain/lv2_plugin.c
FAILED: src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o
cc -Isrc/modules/libpipewire-module-filter-chain.so.p -Isrc/modules -I../src/modules -I. -I.. -Isrc -I../src -Ispa/include -I../spa/include -I/usr/include/sratom-0 -I/usr/include/sord-0 -I/usr/include/serd-0 -I/usr/include/lilv-0 -flto=4 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu99 -fvisibility=hidden -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 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o -MF src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o.d -o src/modules/libpipewire-module-filter-chain.so.p/module-filter-chain_lv2_plugin.c.o -c ../src/modules/module-filter-chain/lv2_plugin.c
../src/modules/module-filter-chain/lv2_plugin.c:38:10: fatal error: lv2/atom/atom.h: No such file or directory
#include <lv2/atom/atom.h>
^~~~~~~~~~~~~~~~~
compilation terminated.
```
For more please see the log : https://launchpadlibrarian.net/621435634/buildlog_ubuntu-bionic-amd64.pipewire_0.3.57.r4.gf957435-1~ubuntu18.04_BUILDING.txt.gzhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2668OBS horrible internal audio, strange problem, could be a pipewire issue?2022-09-02T17:38:03ZGabrieleOBS horrible internal audio, strange problem, could be a pipewire issue?Just follow [that discussion](https://github.com/obsproject/obs-studio/issues/7209#issuecomment-1229483854), then follow the "connection" to another discussion from the EasyEffects github repo.
It's just too complicated to describe again.Just follow [that discussion](https://github.com/obsproject/obs-studio/issues/7209#issuecomment-1229483854), then follow the "connection" to another discussion from the EasyEffects github repo.
It's just too complicated to describe again.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2667PipeWire as Bluetooth receiver2022-09-07T12:31:23ZBart RibbersPipeWire as Bluetooth receiverWith PulseAudio it's possible to use an instance as a Bluetooth receiver, as in a phone could connect to the machine running PulseAudio using Bluetooth and play audio, and have it come out of the speakers attached to the PulseAudio syste...With PulseAudio it's possible to use an instance as a Bluetooth receiver, as in a phone could connect to the machine running PulseAudio using Bluetooth and play audio, and have it come out of the speakers attached to the PulseAudio system.
I'd like to do the same with PipeWire, but it seems this is currently not possible. At least `module-bluetooth-discover` and `module-bluetooth-policy` are not available and I can not find any documentation to do it differently.