pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2022-12-22T17:53:19Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2899Multiplying Audio Source Entries In KDE Audio Settings2022-12-22T17:53:19ZvindicatorrMultiplying Audio Source Entries In KDE Audio Settings<!-- 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.62 (actually, the master "leak" commit "fix" in the other thread I'm in, but I t...<!-- 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.62 (actually, the master "leak" commit "fix" in the other thread I'm in, but I think it's unrelated, so I won't tag 1840).
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: KDE
- Kernel version (`uname -r`): 6.0.1-dirty
## Description of Problem:
I'm finding multiple entries of an audio process source in KDE's audio settings.
## How Reproducible:
Constantly once I noticed it.
### Steps to Reproduce:
1. Open KDE Audio Settings ("Configure audio devices")
2. Open Spotify
3. Play Music
4. Enjoy
5. Wait
### Actual Results:
Multiplying instances/entries of spotify in KDE's audio settings.
### Expected Results:
There ought to only be one instance of the spotify process.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:[pw-dump.tar.gz](/uploads/883d99ea32af603032fc64b44441bd40/pw-dump.tar.gz)
<details><summary>KDE Audio Settings - Screenshot</summary>
![pw_spotifyMultiplying](/uploads/2d3f3bfb8c8fef39223d40d177752f7b/pw_spotifyMultiplying.png)
</details>https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2898No HSP/HFP profiles detected on a specific bluetooth device, after a recent u...2023-01-06T15:29:10ZsaipavancNo HSP/HFP profiles detected on a specific bluetooth device, after a recent updateI have used my Anker Soundcore A2 Life NC + since the last few months, when the mSBC protocol on Pipewire started working without any hickups. This is on Arch Linux, and I had no problems to use it on handsfree mode for my zoom calls. Bu...I have used my Anker Soundcore A2 Life NC + since the last few months, when the mSBC protocol on Pipewire started working without any hickups. This is on Arch Linux, and I had no problems to use it on handsfree mode for my zoom calls. But, just since the last two days after I updated the system, I am unable to get the bluetooth headset to work. What I see is that the bluetooth menu lists the profiles AAC, SBC, SBC-XQ and no other hsp/hfp profiles. The AAC profile works fine, but when I switch to the SBC or SBC-XQ profile, the device gets disconnected abruptly.
I thought this was because of a strange issue with my config files I used for Pipewire, so I downloaded a Fedora iso (as it has pipewire installed by default) and there everything worked fine, along with the mSBC profile for the handsfree mode. But, I was wrong, as when I updated the system I experienced exactly the same error. And from my logs it seems like it might be an issue with bluetoothd.
Now, the issue is exactly as I described above, and I have the following info from logs. When I initially connect the device I get the following output on Journal logs
```
Dec 18 15:56:17 fedora systemd[1614]: Started app-gnome-gnome\x2dbluetooth\x2dpanel-2604.scope - Application launched by gnome-shell.
Dec 18 15:57:09 fedora systemd[1614]: Reached target bluetooth.target - Bluetooth.
Dec 18 15:57:17 fedora bluetoothd[857]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Dec 18 15:57:20 fedora bluetoothd[857]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
```
Which might somehow link to hsp/hfp protocols not being available for the device. And then, when I try to change the profile from AAC to SBC or SBC-XQ, I have the following message and the device gets disconnected.
```
Dec 18 16:05:28 fedora bluetoothd[3560]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 4C:72:74:01:14:D8: Connection reset by peer (104)
Dec 18 16:05:28 fedora bluetoothd[3560]: profiles/audio/avdtp.c:try_send() send: Connection reset by peer (104)
```
Here is my systeminfo:
```
# uname -a
Linux fedora 6.0.12-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Dec 8 16:58:47 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Installed Packages
bluez.x86_64 5.66-4.fc37
pipewire.x86_64 0.3.63-1.fc37
Bluetooth device:
8087:0029 Intel Corp. AX200 Bluetooth
```
Downgrading pipewire to the last version using the command: `dnf install pipewire-libs-0.3.59-2.fc37.x86_64`, fixed the issue, and everything works as expected. I will be happy to provide any further info to help resolve this issue.
Thank you in advance!https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2897echo-cancel nodes are confusing2022-12-19T16:10:39Zshironekoecho-cancel nodes are confusing<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
/usr/bin/pipewire
Compiled with libpipewire 0.3.63
Linked with libpipewire 0.3.63
- ...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
/usr/bin/pipewire
Compiled with libpipewire 0.3.63
Linked with libpipewire 0.3.63
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: riverwm
- Kernel version (`uname -r`): 6.0.12-arch1-1
## Description of Problem:
The nodes for the echo-cancel module is confusing, even in patchbays. I was really troubled as to why echo cancel is not functioning at all (either there was silence or it seemed the audio is passed verbatim), and it turns out I was just not plumbing the audio into the right ports.
As you can see, right now the module creates 4 "nodes" (not sure if it's the right term) they don't seem to be connected with each other and the node name/port name is really generic
![shot_20221218_150158](/uploads/f18d54f70569df907a5ff8d1aa694ed0/shot_20221218_150158.png)
What I think would be much more clear is if they are in one node, something like in the picture (I couldn't fix the z-order). also it would be helpful if the nodes have useful names like "playback_in" "mic_in" "playback_out" "mic_out" something like that.
![shot_20221218_150253](/uploads/91d0f403e495f14349557a0e8a1dae55/shot_20221218_150253.png)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2896mSBC audio stop working during operation2023-01-22T06:35:34ZmaormSBC audio stop working during operation<!-- 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: 0.3.63
- Arch linux
- Desk...<!-- 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: 0.3.63
- Arch linux
- Desktop Environment: gnome
- Kernel version: 6.0.12
- BlueZ version: 5.65
```
Device 94:DB:56:94:56:FF WH-1000XM4
Device 1C:1A:DF:EA:03:AA Microsoft Sculpt Comfort Mouse
```
## Description of Problem:
During google meet mSBC audio stop arrived to headphone
Only noticeable issue is from logs of kernel with following lines:
Bluetooth: hci0: SCO packet for unknown connection handle 0
Bluetooth: hci0: SCO packet for unknown connection handle 513https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2895Multiple second audio delay with pipewire-alsa application (runelite)2022-12-19T00:34:32Zxo-xo-xo-xoMultiple second audio delay with pipewire-alsa application (runelite)Recently I was playing RuneLite (using the .AppImage build) on Nobara Linux, which was running Pipewire version 0.3.61. I experienced audio delays of a few seconds with exclusively this app, which, according to my volume control in the p...Recently I was playing RuneLite (using the .AppImage build) on Nobara Linux, which was running Pipewire version 0.3.61. I experienced audio delays of a few seconds with exclusively this app, which, according to my volume control in the panel was using Pipewire-Alsa. I believe this is related to a similar audio issue that was happening with Davinci Resolve. Installing the **alsa-plugins-pulseaudio** package fixed the issue, but I was told that this is shouldn't be necessary and to report this as a bug. Let me know if there's any other information that would be helpful.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2893Pipewire or wireplumber not remember last routing2023-01-04T05:18:56ZCsaba R.Pipewire or wireplumber not remember last routingI set routing with pavucontrol, Seren VoIP client via echo cancelation module. It does not remember the signal path during the next boot.
Versions:
wireplumber-0.4.13-1.fc37.x86_64<br />
pipewire-0.3.63-3.fc37.x86_64 (latest build from...I set routing with pavucontrol, Seren VoIP client via echo cancelation module. It does not remember the signal path during the next boot.
Versions:
wireplumber-0.4.13-1.fc37.x86_64<br />
pipewire-0.3.63-3.fc37.x86_64 (latest build from git repo: 9c2b2a64)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2891Pulse tunnel out of sync, overruns2023-01-13T06:11:57ZVladimír DudrPulse tunnel out of sync, overruns<!-- 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.63
Linked with libpipewire 0.3.63
```
- 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.63
Linked with libpipewire 0.3.63
```
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): "Arch Linux"
- Desktop Environment: custom/none, launched by sddm, pipewire started through systemd user unit
- Kernel version (`uname -r`): 6.0.12-arch1-1
## Description of Problem:
Audio coming out of the server gets skewed by cca. 8 seconds during 4 minutes of playback.
There are no noises, reaction to player is immediate this time (manually changing track or pausing, using mpd), but every now and then the stream skips and pipewire logs overrun.
It started today - after upgrade to 0.3.63.
It seems to be follow up on #2548, #2637
## How Reproducible:
Always
### Steps to Reproduce:
1. start mpd with pipewire backend
2. stream with pulse tunnel to pulseaudio on rpi (discovered via zeroconf in my case)
# Additional Info (as attachments):
[pw-dump.log](/uploads/247f3deee2c2e2ea5e137f6909a08b5e/pw-dump.log)
EDIT: add `journalctl --user -bu pipewire`: [pw.log](/uploads/89983dfb116138a94513e55c4992ee31/pw.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2890Can't switch to front panel output on Xonar D12022-12-16T18:28:44ZNikos ChantziarasCan't switch to front panel output on Xonar D1- PipeWire version: 0.3.63
- Distribution and distribution version: Gentoo Linux
- Desktop Environment: KDE Plasma 5.26.4
- Kernel version: 5.15.83-gentoo
## Description of Problem:
There is no way to switch to front panel headphone out...- PipeWire version: 0.3.63
- Distribution and distribution version: Gentoo Linux
- Desktop Environment: KDE Plasma 5.26.4
- Kernel version: 5.15.83-gentoo
## Description of Problem:
There is no way to switch to front panel headphone output through controls exposed by pipewire. I have to use alsamixer and unmute the "Front Panel" element:
![image](/uploads/83d5aee27325273ce6b3fc63f5883bee/image.png)
My sound card is an Asus Xonar D1. The problem does not exist with integrated audio, which offers front panel headphone output as a profile I can switch to. No such profile exists for the Xonar D1.
# Additional Info (as attachments):
[pw-dump](/uploads/ae6b119a80c8803b61db5f295852184a/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2889Ardour (jack) recording is distorted after the first few xruns.2023-08-02T07:46:51ZFeng YuArdour (jack) recording is distorted after the first few xruns.<!-- 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.61
Linked with libpipewire 0.3.61
- Distribu...<!-- 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.61
Linked with libpipewire 0.3.61
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
PRETTY_NAME="Fedora Linux 36 (Workstation Edition)"
- Desktop Environment: GNOME 42.4 (Wayland)
- Kernel version (`uname -r`): 6.0.12-200.fc36.x86_64
## Description of Problem:
After recording for a while and getting the first xrun, the recorded audio is distorted (similar to a 'ring/mod' effect) for a very long time.
Sometimes after more xruns the 'ringing' disappears.
I have attached an audio file to demonstrate the 'ringing' sound:
![Take36_Audio_1-1.1](/uploads/13ba71b4166e6fc46d4d7c0ea04a1bf5/Take36_Audio_1-1.1.wav)
It almost feels like the cursor pointer in the buffer drifted to a random location after an xrun, but I really don't know enough to tell.
## How Reproducible:
This is very reliably reproduced if on my system, which has a low (but non-zero) xrun rate. I tried increasing headroom and period-size to 8192 and 1024, which somewhat mitigated the problem (by reducing the probability of xruns), but after an xrun the ringing still occurs, and xruns will inevitably happen in long sessions.
### Steps to Reproduce:
1. Start Ardour6 with Jack, which connects to pipewire. Pick any buffer size.
2. Arm Input 0/1 for recording (setting up software monitoring can help detect the problem sooner, as the hardware monitoring is not affected by pipewire's recorded audio.)
3. Starting recording till xrun occurs. Before the xrun, the recording is normal.
4. distorted 'ringining' after the xrun.
5. record long enough to experience more xruns, sometimes the ringing disappears.
### Actual Results:
The impact of an xrun (garbled ringing effect in audio) is persistent.
### Expected Results:
The duration of the impact of an xrun should have a reasonable bound.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw.log](/uploads/feb85ed6c4dae91edf76ba3af3612820/pw.log)
This may be hardware related, although seems like the software should at least be able to contain the impact of an xrun.
I am using a Quad Cortex interface produced by Neural DSP, which uses chips similar to ADSP-SC57x and ADSP-2157x (Cortex-A5-ish) from what I could find.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2888Audio ringing in AIMP audio player since 0.3.62 update2022-12-15T11:16:30Zuser1-githubAudio ringing in AIMP audio player since 0.3.62 updateAIMP is a Windows audio player which I currently run through Wine 7.0.1. With 0.3.61, audio was good, but this Sunday I received an update to 0.3.62 on my Fedora 37 install and since this update I started experiencing audible ringing in ...AIMP is a Windows audio player which I currently run through Wine 7.0.1. With 0.3.61, audio was good, but this Sunday I received an update to 0.3.62 on my Fedora 37 install and since this update I started experiencing audible ringing in AIMP.
I currently don't have any other software that I run through Wine, but it would be nice if someone else will also tell how does audio work through Wine with Pipewire 0.3.62 (or if someone also uses AIMP will share his experience as well).https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2887Libpipewire compiled version diferent than linked version2023-09-07T03:47:39ZHunterLibpipewire compiled version diferent than linked versionAfter compiling and installing pipewire 0.3.62 the version check displays two different versions.
Ubuntu 22.10 and kernel 6.1-rc5.
Compiled with libpipewire 0.3.62
Linked with libpipewire 0.3.60After compiling and installing pipewire 0.3.62 the version check displays two different versions.
Ubuntu 22.10 and kernel 6.1-rc5.
Compiled with libpipewire 0.3.62
Linked with libpipewire 0.3.60https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2886Sound just gets lost2022-12-14T10:09:57Zx ySound just gets lost```
pipewire
Compiled with libpipewire 0.3.60
Linked with libpipewire 0.3.60
wireplumber
Compiled with libwireplumber 0.4.12
Linked with libwireplumber 0.4.12
NixOS 23.05 (Stoat)
sway
Linux grid 5.15.82 #1-NixOS SMP Thu Dec 8 10:28:45 ...```
pipewire
Compiled with libpipewire 0.3.60
Linked with libpipewire 0.3.60
wireplumber
Compiled with libwireplumber 0.4.12
Linked with libwireplumber 0.4.12
NixOS 23.05 (Stoat)
sway
Linux grid 5.15.82 #1-NixOS SMP Thu Dec 8 10:28:45 UTC 2022 x86_64 GNU/Linux
```
## Description of Problem:
I don't know which component causes the issue, but sometimes sound just gets lost, while pipewire is responsive, `pavucontrol` shows that the sound is enabled and nothing is muted and the issue gets fixed by `systemctl --user restart pipewire wireplumber.service`. This happens with bluetooth headset and without the headset. This happens when I interact with pipewire in any way, by changing the volume, muting something, starting new application, opening `pavucontrol`, playing new video in firefox, etc.
## How Reproducible:
Several times in a day
### Steps to Reproduce:
Just use pipewire for a while
### Actual Results:
Sound is lost
### Expected Results:
Sound is not lost
# Additional Info (as attachments):
Last log lines.
```journal
Dec 12 00:06:39 grid systemd[2779]: Stopped PipeWire Multimedia Service.
Dec 12 00:06:39 grid systemd[2779]: pipewire.service: Consumed 10.956s CPU time.
Dec 12 00:06:39 grid systemd[2779]: Started PipeWire Multimedia Service.
Dec 12 00:06:39 grid systemd[2779]: Started Multimedia Service Session Manager.
Dec 12 00:06:39 grid wireplumber[8190]: Failed to set scheduler settings: Operation not permitted
Dec 12 00:06:39 grid wireplumber[8190]: [0:58:28.601122015] [8190] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Dec 12 00:06:39 grid wireplumber[8190]: [0:58:28.601454183] [8190] INFO Camera camera_manager.cpp:293 libcamera v0.0.1
Dec 12 00:06:39 grid wireplumber[8190]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
Dec 12 00:06:39 grid pipewire[8189]: default: can't setup properties: No such file or directory
Dec 12 00:06:39 grid pipewire[8189]: default: can't setup properties: No such file or directory
Dec 12 00:06:39 grid pipewire[8189]: default: can't setup properties: No such file or directory
Dec 12 00:06:39 grid pipewire[8189]: [0:58:28.700524338] [8189] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Dec 12 00:06:39 grid pipewire[8189]: [0:58:28.700761589] [8189] INFO Camera camera_manager.cpp:293 libcamera v0.0.1
Dec 12 00:06:39 grid pipewire[8189]: ALSA lib parser.c:1194:(parse_sequence) error: sequence command 'devdisall' is ignored
Dec 12 00:06:52 grid systemd[2779]: Stopping Multimedia Service Session Manager...
Dec 12 00:06:52 grid wireplumber[8190]: stopped by signal: Terminated
Dec 12 00:06:52 grid wireplumber[8190]: disconnected from pipewire
Dec 12 00:06:52 grid systemd[2779]: Stopped Multimedia Service Session Manager.
Dec 12 00:06:52 grid systemd[2779]: Stopping PipeWire Multimedia Service...
Dec 12 00:06:52 grid systemd[2779]: Stopped PipeWire Multimedia Service.
Dec 12 00:06:52 grid systemd[2779]: Started PipeWire Multimedia Service.
Dec 12 00:06:52 grid systemd[2779]: Started Multimedia Service Session Manager.
Dec 12 00:06:52 grid wireplumber[8362]: Failed to set scheduler settings: Operation not permitted
Dec 12 00:06:52 grid wireplumber[8362]: [0:58:41.936777992] [8362] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Dec 12 00:06:52 grid wireplumber[8362]: [0:58:41.937116277] [8362] INFO Camera camera_manager.cpp:293 libcamera v0.0.1
Dec 12 00:06:53 grid wireplumber[8362]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
Dec 12 00:06:53 grid pipewire[8361]: default: can't setup properties: No such file or directory
Dec 12 00:06:53 grid pipewire[8361]: default: can't setup properties: No such file or directory
Dec 12 00:06:53 grid pipewire[8361]: default: can't setup properties: No such file or directory
Dec 12 00:06:53 grid pipewire[8361]: [0:58:42.232550903] [8361] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Dec 12 00:06:53 grid pipewire[8361]: [0:58:42.232829476] [8361] INFO Camera camera_manager.cpp:293 libcamera v0.0.1
Dec 12 00:06:53 grid pipewire[8361]: ALSA lib parser.c:1194:(parse_sequence) error: sequence command 'devdisall' is ignored
Dec 12 00:07:25 grid systemd[2779]: Stopping Multimedia Service Session Manager...
Dec 12 00:07:25 grid wireplumber[8362]: stopped by signal: Terminated
Dec 12 00:07:25 grid wireplumber[8362]: disconnected from pipewire
Dec 12 00:07:25 grid systemd[2779]: Stopped Multimedia Service Session Manager.
Dec 12 00:07:25 grid systemd[2779]: Stopping PipeWire Multimedia Service...
Dec 12 00:07:25 grid systemd[2779]: Stopped PipeWire Multimedia Service.
Dec 12 00:07:25 grid systemd[2779]: Started PipeWire Multimedia Service.
Dec 12 00:07:25 grid systemd[2779]: Started Multimedia Service Session Manager.
Dec 12 00:07:25 grid wireplumber[8571]: Failed to set scheduler settings: Operation not permitted
Dec 12 00:07:25 grid wireplumber[8571]: [0:59:14.631975411] [8571] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Dec 12 00:07:25 grid wireplumber[8571]: [0:59:14.632355173] [8571] INFO Camera camera_manager.cpp:293 libcamera v0.0.1
Dec 12 00:07:25 grid wireplumber[8571]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
Dec 12 00:07:25 grid pipewire[8570]: default: can't setup properties: No such file or directory
Dec 12 00:07:25 grid pipewire[8570]: default: can't setup properties: No such file or directory
Dec 12 00:07:25 grid pipewire[8570]: default: can't setup properties: No such file or directory
Dec 12 00:07:25 grid pipewire[8570]: [0:59:14.752768491] [8570] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Dec 12 00:07:25 grid pipewire[8570]: [0:59:14.752990597] [8570] INFO Camera camera_manager.cpp:293 libcamera v0.0.1
Dec 12 00:07:25 grid pipewire[8570]: ALSA lib parser.c:1194:(parse_sequence) error: sequence command 'devdisall' is ignored
```
[pw-dump.log](/uploads/3b8935ee1397c9ad3e8f5d4922f4fe98/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2885[biscted] Distorted audio since 0.3.622022-12-16T11:40:09ZSefa Eyeoglucontact@scrumplex.net[biscted] Distorted audio since 0.3.62<!-- 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.62 (checked Git master as well, same issue)
- Distribution and distribution vers...<!-- 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.62 (checked Git master as well, same issue)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux testing
- Desktop Environment: Sway
- Kernel version (`uname -r`): 6.0.12-zen1-1-zen
## Description of Problem:
Both my microphone input as well as my headphone output have distorted output/input, since upgrading to 0.3.62.
After bisecting, commit 177479dfd152d8d3ee9f0a84728782e6d8e0dd15 is the one that introduced this.
I will attach some audio samples with and without that commit.
## How Reproducible:
Always
### Steps to Reproduce:
Very unsure about this as it could be hardware specific.
I have this behavior on my integrated HD audio card (Mic input) `Starship/Matisse HD Audio Controller Analog Stereo`, as well as my USB DAC (`Schiit Modi 3+ Analog Stereo`)
### Actual Results:
Distorted audio
### Expected Results:
No distorted audio
# Additional Info (as attachments):
```
# bad: [3a443b4e1c9730675c7de0453a6279ab9ee263fd] 0.3.62
# good: [f038e3f23824f9319daaa9f9a31600fc6df49a39] 0.3.61
git bisect start '0.3.62' '0.3.61'
# bad: [fa799aac8674457a475c30d0c604876143b8d331] libcamera: Implement SPA_META_VideoTransform support
git bisect bad fa799aac8674457a475c30d0c604876143b8d331
# good: [0c50ccac8707248fb3cf7173198080fa82868426] jack: only process valid ports
git bisect good 0c50ccac8707248fb3cf7173198080fa82868426
# good: [4e4d76ccd0419e5e215e18e4273143529376f9f7] audioconvert: use gather in AVX2 code
git bisect good 4e4d76ccd0419e5e215e18e4273143529376f9f7
# bad: [5bda4b6a5704268d5405d5cca2bdcf62e29c303b] audioadapter: only accept PortConfig for the adapter direction
git bisect bad 5bda4b6a5704268d5405d5cca2bdcf62e29c303b
# bad: [177479dfd152d8d3ee9f0a84728782e6d8e0dd15] audioconvert: improve some more AVX2 code
git bisect bad 177479dfd152d8d3ee9f0a84728782e6d8e0dd15
# good: [d6101d73e7b145124475008e78edf5e0d1dbe92c] audioconvert: fix PortConfig enumeration
git bisect good d6101d73e7b145124475008e78edf5e0d1dbe92c
# first bad commit: [177479dfd152d8d3ee9f0a84728782e6d8e0dd15] audioconvert: improve some more AVX2 code
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2884pw-cat/pw-play/pw-record target not working2023-05-15T11:44:03Zbgkillaspw-cat/pw-play/pw-record target not workingpw-cat/pw-play/pw-record with --target seems to change nothing and just selects the default device i tried with the name of the device and the id and even if i type a non existent target it still just selects the default onepw-cat/pw-play/pw-record with --target seems to change nothing and just selects the default device i tried with the name of the device and the id and even if i type a non existent target it still just selects the default onehttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2883Enhancement/Request: Per-Device sample rate control2023-04-17T08:59:24ZEden RoseEnhancement/Request: Per-Device sample rate controlThe Request: My request is "default.clock.rate" and "default.clock.allowed-rates" have per-device restrictions.
Why: In general this behavior follows other OS's per-device defaults, and reduces sample-switching desync that can occur whe...The Request: My request is "default.clock.rate" and "default.clock.allowed-rates" have per-device restrictions.
Why: In general this behavior follows other OS's per-device defaults, and reduces sample-switching desync that can occur when switching destinations mid audio-stream.
Who does this benefit: Everyone who uses multiple devices with a wide range of supported sample rates and needs to force sample rates per-device. Or people who hot-swap audio destinations on-the-fly with sample-rate differences.
---
My personal reasons why id like it:
Several times I've ran into issues switching between my Speaker DAC (CM6631A) and my Front-Panel Onboard Audio (0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller).
The DAC(CM6631A) performs wonderfully at 384khz, however the FPA is capped at 96khz, however resampling occurs in most applications due to pulseaudio incompatibilities at 48khz-96khz, so a default-rate of 48khz is better. But native applications should be able to still request 96khz.
When i leave 44.1khz - 96khz (for FPA) & 192/384khz (for DAC) in "allowed.rates" and leave the default "rate" at 384khz. When switching from DAC to FPA it sets and drops the FPA Sample-Rate initially to 44.1khz. As soon as a audio stream opens from any application(or is wired), regardless of its application-set sample rate. It jumps to 96khz (hardware) and resamples from the applications sample-rate(usually 44.1khz or 48khz) to 96khz. Resulting in clicking and popping. Occasionally with other resampling noises.
This generally doesnt happen with the DAC exclusively. however, i have noticed it when switching back to the DAC on occasion from the FPA, when pipewire was opened/restarted with FPA as the default devices, that it occurs and the DAC refuses to go back to 384khz, remaining locked at 44.1khz.
System:
OS: Linux (Archlinux)
(lib)Pipewire Version: (lib)pipewire 0.3.61
DE: Plasma 5(KDE)
Kernel version (`uname -r`): 6.0.11-AMD-znver2https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2881use after free on deinit2022-12-10T10:02:15ZNaïm Favieruse after free on deinit<!-- 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.62 (3a443b4e1c9730675c7de0453a6279ab9ee263fd)
- Distribution and distribution ve...<!-- 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.62 (3a443b4e1c9730675c7de0453a6279ab9ee263fd)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): NixOS 23.05 (Stoat)
- Desktop Environment: no
- Kernel version (`uname -r`): 6.0.9
## Description of Problem:
Initially reported at mpv, see there for full context: https://github.com/mpv-player/mpv/issues/10959
When running mpv with the pipewire backend (`mpv --ao=pipewire,pulse file`) **on a system without pipewire running**, a crash occurs when waking up from suspend.
Enabling ASan reveals a use-after-free when mpv calls `pw_deinit` after deciding that pipewire isn't available. See attachments.
## How Reproducible:
### Steps to Reproduce:
On a Linux system using PulseAudio, **not** PipeWire:
1. compile mpv and pipewire with `-fsanitize=address,undefined`
1. run `mpv --no-config --ao=pipewire,pulse file.mp4`
1. kaboom
# Additional Info (as attachments):
<details><summary>asan trace</summary>
```
[ao/pipewire] Could not connect to context '(null)': Host is down
=================================================================
==3646909==ERROR: AddressSanitizer: heap-use-after-free on address 0x60c0001667d0 at pc 0x7f9dfea64cbd bp 0x7ffff7138620 sp 0x7ffff7138618
READ of size 8 at 0x60c0001667d0 thread T0
#0 0x7f9dfea64cbc in remove_from_poll ../spa/plugins/support/loop.c:153
#1 0x7f9dfea6f3a3 in loop_destroy_source ../spa/plugins/support/loop.c:794
#2 0x7f9dfea700f0 in impl_clear ../spa/plugins/support/loop.c:873
#3 0x7f9e2384792d in unref_handle ../src/pipewire/pipewire.c:211
#4 0x7f9e2384bea4 in pw_deinit ../src/pipewire/pipewire.c:701
#5 0x47520d in uninit ../audio/out/ao_pipewire.c:300
#6 0x48d193 in init ../audio/out/ao_pipewire.c:564
#7 0x457118 in ao_init ../audio/out/ao.c:218
#8 0x458d18 in ao_init_best ../audio/out/ao.c:339
#9 0x6731f0 in reinit_audio_filters_and_output ../player/audio.c:441
#10 0x676da3 in fill_audio_out_buffers ../player/audio.c:884
#11 0x726ade in run_playloop ../player/playloop.c:1212
#12 0x700842 in play_current_file ../player/loadfile.c:1679
#13 0x702238 in mp_play_files ../player/loadfile.c:1865
#14 0x70e119 in mpv_main ../player/main.c:432
#15 0x4212be in main ../osdep/main-fn-unix.c:5
#16 0x7f9e2182924d in __libc_start_call_main (/nix/store/4nlgxhb09sdr51nc9hdm8az5b08vzkgx-glibc-2.35-163/lib/libc.so.6+0x2924d)
#17 0x7f9e21829308 in __libc_start_main_impl (/nix/store/4nlgxhb09sdr51nc9hdm8az5b08vzkgx-glibc-2.35-163/lib/libc.so.6+0x29308)
#18 0x4211f4 in _start (/nix/store/jd6gw9hwambj9slyk1y9i98232f7bq95-mpv-0.35.0/bin/mpv+0x4211f4)
0x60c0001667d0 is located 80 bytes inside of 128-byte region [0x60c000166780,0x60c000166800)
freed by thread T0 here:
#0 0x7f9e26cb14d7 in free (/nix/store/mdck89nsfisflwjv6xv8ydj7dj0sj2pn-gcc-11.3.0-lib/lib/libasan.so.6+0xb14d7)
#1 0x7f9e238479a7 in unref_handle ../src/pipewire/pipewire.c:215
previously allocated by thread T0 here:
#0 0x7f9e26cb1987 in __interceptor_calloc (/nix/store/mdck89nsfisflwjv6xv8ydj7dj0sj2pn-gcc-11.3.0-lib/lib/libasan.so.6+0xb1987)
#1 0x7f9e2384a14a in load_spa_handle ../src/pipewire/pipewire.c:275
SUMMARY: AddressSanitizer: heap-use-after-free ../spa/plugins/support/loop.c:153 in remove_from_poll
Shadow bytes around the buggy address:
0x0c1880024ca0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
0x0c1880024cb0: 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa fa
0x0c1880024cc0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa
0x0c1880024cd0: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c1880024ce0: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
=>0x0c1880024cf0: fd fd fd fd fd fd fd fd fd fd[fd]fd fd fd fd fd
0x0c1880024d00: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
0x0c1880024d10: 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa fa
0x0c1880024d20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0c1880024d30: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd
0x0c1880024d40: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==3646909==ABORTING
```
</details>
mpv code that calls `pw_deinit`: https://github.com/mpv-player/mpv/blob/25b66256d7ff48254b2055a066e29f260414112f/audio/out/ao_pipewire.c#L285-L303https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2880All audio output gets killed shortly after QEMU is launched via AVD (Android ...2023-01-03T17:25:27ZShoo!All audio output gets killed shortly after QEMU is launched via AVD (Android Studio)**- PipeWire version** : 0.3.61
**- Distribution and distribution version** : Arch Linux
**- Desktop Environment:** Cinnamon
**- Kernel version :** 6.0.11-zen1-1-zen
**## Description of Problem:**
Starting Android Studio AVD Virtual ma...**- PipeWire version** : 0.3.61
**- Distribution and distribution version** : Arch Linux
**- Desktop Environment:** Cinnamon
**- Kernel version :** 6.0.11-zen1-1-zen
**## Description of Problem:**
Starting Android Studio AVD Virtual machine all works ok for a couple of minutes but then all audio output gets killed
- Audio output / input / profiles remain listed in sound settings
- - Switching between audio profiles has no impact, there is no sound
- Active audio streams still run (Youtube/Quod Libet/MPV still show media as playing , but there's no sound
- - Seeking works , but there is no sound
- Multiple audio streams WITHOUT QEMU running work OK.
- Pipewire||machine service needs to be restarted to get the audio back
**## How Reproducible:**
Reproducible 100%
**### Steps to Reproduce:**
1. Start the graphical user session
2. Open Android Studio, Start AVD and start any application that outputs sound
3. Audio stream gets killed for all apps in the user session after approximately 1 minute
**### Actual Results:**
Audio output gets killed a minute or two after AVD Virtual Device is launched
**### Expected Results:**
Audio stream working on QEMU or QEMU + other streams (Firefox, Quod Libet, Whalebird etc)
**# Additional Info (as attachments):**
[p-wireplumber.log](/uploads/431b91ed359f9a3401fbe6cbb8e04514/p-wireplumber.log)
[p-pipewire-pulse.log](/uploads/20e49af96e7a12de97466ed1f63f520c/p-pipewire-pulse.log)
[p-pipewire-dump.log](/uploads/979a9ee983ed09e9d947e74e3c239e59/p-pipewire-dump.log)
[p-pipewire.log](/uploads/aefd8c58b34abf6dd804f8657f7273be/p-pipewire.log)
[inxi.log](/uploads/be82ac800432030bc9d551dc8be08f25/inxi.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2878audio stutter when pavucontrol-qt is open2022-12-11T22:26:57ZRobert Burchamaudio stutter when pavucontrol-qt is open<!-- 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.59
> Linked with libpipewire 0.3.59 ...<!-- 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.59
> Linked with libpipewire 0.3.59
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Gentoo
- Desktop Environment: Plasma 5.26.2
- Kernel version (`uname -r`): 6.0.6-gentoo-x86_64
## Description of Problem:
Any playback stutters intermittently while pavucontrol is open. Sometimes playback is clear, but every so often playback stutters for some time, less than a minute, before clearing again.
## How Reproducible:
Guaranteed to happen whilst pavucontrol-qt is open. Guaranteed NOT to happen if pavucontrol-qt is quit.
### Steps to Reproduce:
1. Start playback from any source (mplayer, vlc, zoom, brave) through any device (bt headphones, analog speaker output)
2. Open pavucontrol-qt and leave it open
3. Playback will be for the most part clear, but every few minutes will stutter for 30-45 seconds.
### Actual Results:
Playback will be for the most part clear, but every few minutes will stutter for 30-45 seconds.
### Expected Results:
Playback should remain clear and stutter free
# Additional Info (as attachments):
Gentoo. media-video/pipewire-0.3.59-r2.
> $ pipewire-pulse --version
> pipewire-pulse
> Compiled with libpipewire 0.3.59
> Linked with libpipewire 0.3.59
This appears similar to https://bbs.archlinux.org/viewtopic.php?id=279470 but seems unresolved in 0.3.59-r2 and instead of being constant, it's intermittent, almost sinusoidal in occurrence.
[pw-dump.log](/uploads/3ad1350829bd3c92ac698a4d14ce998a/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2877Pipewire crashing lately2022-12-17T19:20:20ZMikko HPipewire crashing lately<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version: 0.3.61
- Distribution: Arch Linux
- Desktop Environment: KDE Plasma
- Kernel version: 6.0.11-arch1-1
## De...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version: 0.3.61
- Distribution: Arch Linux
- Desktop Environment: KDE Plasma
- Kernel version: 6.0.11-arch1-1
## Description of Problem:
I have been getting almost daily crashes after a system upgrade 2-4 weeks ago. Before that there were no issues. Crashes usually happen as I'm going through audio samples on websites like junodownload/bandcamp/beatport. Sometimes pipewire doesn't crash but there is no audio after starting playback, clicking pause and then play again fixes that. Both my external DAC and onboard audio have the same issue. All config files are default.
# Additional Info:
Mon 2022-12-05 09:37:36 EET 2766 1000 984 SIGSEGV present /usr/bin/pipewire 789.5K
Signal: 11 (SEGV)
Process 2766 (pipewire) of user 1000 dumped core.
Stack trace of thread 2809:
#0 0x00007f2a2926fd2e n/a (libspa-audioconvert.so + 0x27d2e)
#1 0x00007f2a29258902 n/a (libspa-audioconvert.so + 0x10902)
#2 0x00007f2a2bd25629 n/a (libpipewire-0.3.so.0 + 0x61629)
#3 0x00007f2a2bd25ae7 n/a (libpipewire-0.3.so.0 + 0x61ae7)
#4 0x00007f2a2bda9c77 n/a (libspa-support.so + 0x6c77)
#5 0x00007f2a2bd06177 n/a (libpipewire-0.3.so.0 + 0x42177)
#6 0x00007f2a2bb638fd n/a (libc.so.6 + 0x868fd)
#7 0x00007f2a2bbe4c74 __clone (libc.so.6 + 0x107c74)
Stack trace of thread 2766:
#0 0x00007f2a2bbe5096 epoll_wait (libc.so.6 + 0x108096)
#1 0x00007f2a2bdb75c9 n/a (libspa-support.so + 0x145c9)
#2 0x00007f2a2bda9b2b n/a (libspa-support.so + 0x6b2b)
#3 0x00007f2a2bd22571 pw_main_loop_run (libpipewire-0.3.so.0 + 0x5e571)
#4 0x00005638684c02ee n/a (pipewire + 0x12ee)
#5 0x00007f2a2bb00290 n/a (libc.so.6 + 0x23290)
#6 0x00007f2a2bb0034a __libc_start_main (libc.so.6 + 0x2334a)
#7 0x00005638684c0495 n/a (pipewire + 0x1495)
ELF object binary architecture: AMD x86-64
Edit: more informative backtrace as suggested by Niklāvs
```
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/pipewire'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f2a2926fd2e in impl_node_process (object=<optimized out>) at ../pipewire/spa/plugins/audioconvert/audioconvert.c:2410
Downloading 0.09 MB source file /usr/src/debug/pipewire/build/../pipewire/spa/plugins/audioconvert/audioconvert.c
2410 offs = SPA_MIN(bd->chunk->offset, bd->maxsize);
[Current thread is 1 (Thread 0x7f2a29e916c0 (LWP 2809))]
(gdb) thread apply all bt
Thread 2 (Thread 0x7f2a2baba740 (LWP 2766)):
#0 0x00007f2a2bbe5096 in epoll_wait (epfd=4, events=events@entry=0x7ffe7d0935a0, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x00007f2a2bdb75c9 in impl_pollfd_wait (object=<optimized out>, pfd=<optimized out>, ev=0x7ffe7d093770, n_ev=<optimized out>, timeout=<optimized out>) at ../pipewire/spa/plugins/support/system.c:157
#2 0x00007f2a2bda9b2b in loop_iterate (object=0x563869f4cfe8, timeout=-1) at ../pipewire/spa/plugins/support/loop.c:401
#3 0x00007f2a2bd22571 in pw_main_loop_run (loop=loop@entry=0x563869f4cea0) at ../pipewire/src/pipewire/main-loop.c:148
#4 0x00005638684c02ee in main (argc=<optimized out>, argv=<optimized out>) at ../pipewire/src/daemon/pipewire.c:131
Thread 1 (Thread 0x7f2a29e916c0 (LWP 2809)):
#0 0x00007f2a2926fd2e in impl_node_process (object=<optimized out>) at ../pipewire/spa/plugins/audioconvert/audioconvert.c:2410
#1 0x00007f2a29258902 in impl_node_process (object=0x56386a04d498) at ../pipewire/spa/plugins/audioconvert/audioadapter.c:1436
#2 0x00007f2a2bd25629 in process_node (data=0x56386a06af60) at ../pipewire/src/pipewire/impl-node.c:1128
#3 0x00007f2a2bd25ae7 in node_on_fd_events (source=<optimized out>) at ../pipewire/src/pipewire/impl-node.c:1186
#4 0x00007f2a2bda9c77 in loop_iterate (object=<optimized out>, timeout=<optimized out>) at ../pipewire/spa/plugins/support/loop.c:431
#5 0x00007f2a2bd06177 in do_loop (user_data=0x563869f59750) at ../pipewire/src/pipewire/data-loop.c:81
#6 0x00007f2a2bb638fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007f2a2bbe4c74 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2876PulseAudio + PipeWire: Testing 5.1 speakers results in incorrect speakers firing2022-12-04T09:46:06ZBill BuffaloPulseAudio + PipeWire: Testing 5.1 speakers results in incorrect speakers firingJust fixed an issue with the 5.1 speakers crashing pulse audio when switching to the 5.1 profile. Installing PipeWire seems to have fixed that issue, but I noticed when testing the speakers they 'looked' as if I had hooked them up wrong....Just fixed an issue with the 5.1 speakers crashing pulse audio when switching to the 5.1 profile. Installing PipeWire seems to have fixed that issue, but I noticed when testing the speakers they 'looked' as if I had hooked them up wrong.
Rear Left: Sounds like it is emitting from front left
Subwoofer: Says 'rear center' sounds like it is emitting from front left
Rear Right: Creates subwoofer rumble
I have Windows 7 on the same machine and rebooted into it, I tested using it's Configure Speakers and the speakers are setup correctly in Windows.
The subwoofer in PulseAudio/Pipewire shouldn't say 'rear center' and 'rear right' is missing completely.