pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2023-09-25T17:10:59Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3526audio latency measurement question2023-09-25T17:10:59ZMike Bradyaudio latency measurement questionHow would you go about getting the instantaneous actual audio latency? In other words, how would you find out how long it would take for a new audio sample to arrive at the output DAC?
Apologies if it's an obvious question. If there was...How would you go about getting the instantaneous actual audio latency? In other words, how would you find out how long it would take for a new audio sample to arrive at the output DAC?
Apologies if it's an obvious question. If there was sample code or documentation to point to, that would be a big help, thanks.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3525Can context.exec be used to run a command on audio stream/source condition ch...2023-09-25T07:30:42ZChris BillheimerCan context.exec be used to run a command on audio stream/source condition change?Is there a condition that can be used to detect when an audio playback stream/source changes? My prospective use case involves using `pkill -SIGRTMIN+2 i3status-rs` to send a signal to i3status-rust to immediately update/refresh the samp...Is there a condition that can be used to detect when an audio playback stream/source changes? My prospective use case involves using `pkill -SIGRTMIN+2 i3status-rs` to send a signal to i3status-rust to immediately update/refresh the sample rate and bit depth information displayed in my custom i3status-rust block.
Can PipeWire's context.exec config handle this, or is this use case more suited to a session manager like pipewire-media-session and/or WirePlumber? I have not been able to find much info about context.exec beyond having it start session managers, and even then, systemd services are recommended to manage the session manager instead of using context.exec for that purpose.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3524Segfault in applications using libjack.so in client_node_transport() since 0....2023-09-24T16:46:36ZChristian LSegfault in applications using libjack.so in client_node_transport() since 0.3.77- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.80
Linked with libpipewire 0.3.80
(same happens in 0.3.77, 0.3.78, 0.3.79)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.80
Linked with libpipewire 0.3.80
(same happens in 0.3.77, 0.3.78, 0.3.79)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
Fedora Linux 38 (KDE Plasma)
- Desktop Environment:
KDE Plasma
- Kernel version (`uname -r`):
6.4.15-200.fc38.x86_64
## Description of Problem:
Applications linked with libjack.so segfault in client_node_transport(), reproducible with e.g. Mumble or Minecraft (Java)
Not using Jack, e.g.
.alsoftrc
[general]
drivers = pulse
for java resolves the issue, as does downgrading to pipewire 0.3.76 (even only downgrading the pipewire-jack-audio-connection-kit* packages is sufficient)
## How Reproducible:
100% on this machine, with a fresh config and a fresh user.
Not reproducible on a different machine, the difference is being the soundcards used; this box (where it is reproducible) has multiple, which might be part of the issue.
### Steps to Reproduce:
1. Upgrade to pipewire >= 0.3.77
2. Run either Mumble or Minecraft (Java)
### Actual Results:
Segfault
### Expected Results:
Application runs
# Additional Info (as attachments):
The downstream bug report including the full backtrace and system info can be found at https://bugzilla.redhat.com/show_bug.cgi?id=2239348
I'll attach the full backtrace to this bug report as well, if you need additional info, e.g. the soundcards and their config, do let me know, since the issue seems to not be reproducible on all my machines, but where it happens it is 100% reproducible.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3523Volume jump to 100% after USB DAC is reset2023-10-23T03:07:12ZMilkii BrewsterVolume jump to 100% after USB DAC is resetI have a DragonFly Cobalt USB DAC.
Every time I unplug it then replug it in again, the volume jumps to 100% from where it was previously, then jumps back to where it was previously on the first move of the fader in pavucontrol.
Sometim...I have a DragonFly Cobalt USB DAC.
Every time I unplug it then replug it in again, the volume jumps to 100% from where it was previously, then jumps back to where it was previously on the first move of the fader in pavucontrol.
Sometimes it jumps to 100% _after_ moving the fader or pressing a media volume key for the first time then where it was previously directly after on continued movement of the mouse-dragged fader.
What's the best way to log? I tried `killall -9 pipewire-pulse && PIPEWIRE_DEBUG=5 pipewire-pulse 2>owie-pw-pulse.log` but Firefox doesn't show up in pavucontrol afterward.
`journalctl` gives
```
Sep 22 04:53:55 red kernel: usb 1-2: USB disconnect, device number 19
Sep 22 04:53:55 red pipewire[1878]: spa.alsa: front:2: snd_pcm_status error: No such device
Sep 22 04:53:55 red pipewire[1878]: spa.alsa: front:2: snd_pcm_recover error: No such device
Sep 22 04:53:55 red pipewire[1878]: spa.alsa: front:2: snd_pcm_drop No such device
Sep 22 04:53:55 red pipewire[1878]: spa.alsa: front:2: close failed: No such device
Sep 22 04:53:55 red wireplumber[1879]: <WpSiStandardLink:0x5627bbd905c0> 2 of 2 PipeWire links failed to activate
Sep 22 04:53:55 red wireplumber[1879]: <WpSiStandardLink:0x5627bbd894b0> 2 of 2 PipeWire links failed to activate
Sep 22 04:53:55 red wireplumber[1879]: <WpSiStandardLink:0x5627bbfb4b60> 2 of 2 PipeWire links failed to activate
Sep 22 04:53:55 red wireplumber[1879]: <WpSiStandardLink:0x5627bbef4840> 2 of 2 PipeWire links failed to activate
Sep 22 04:53:56 red wireplumber[1879]: <WpSiStandardLink:0x5627bbef1dd0> 2 of 2 PipeWire links failed to activate
Sep 22 04:53:56 red wireplumber[1879]: <WpSiStandardLink:0x5627bc03dbc0> 2 of 2 PipeWire links failed to activate
Sep 22 04:53:56 red wireplumber[1879]: <WpSiAudioAdapter:0x5627bbf42ca0> tried to link on last rescan, not retrying
Sep 22 04:54:00 red kernel: usb 1-2: new full-speed USB device number 20 using xhci_hcd
Sep 22 04:54:00 red kernel: usb 1-2: New USB device found, idVendor=21b4, idProduct=0085, bcdDevice= 1.10
Sep 22 04:54:00 red kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 22 04:54:00 red kernel: usb 1-2: Product: AudioQuest DragonFly Cobalt v1.0
Sep 22 04:54:00 red kernel: usb 1-2: Manufacturer: AudioQuest
Sep 22 04:54:00 red kernel: usb 1-2: SerialNumber: AQDFCB0101032045
Sep 22 04:54:05 red kernel: hid-generic 0003:21B4:0085.0009: hiddev97,hidraw2: USB HID v1.11 Device [AudioQuest AudioQuest DragonFly Cobalt v1.0] on usb-0000:00:14.0-2/input2
Sep 22 04:54:05 red mtp-probe[16535]: checking bus 1, device 20: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2"
Sep 22 04:54:05 red mtp-probe[16535]: bus: 1, device: 20 was not an MTP device
Sep 22 04:54:06 red mtp-probe[16567]: checking bus 1, device 20: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2"
Sep 22 04:54:06 red mtp-probe[16567]: bus: 1, device: 20 was not an MTP device
Sep 22 04:54:06 red wireplumber[1879]: <WpSiAudioAdapter:0x5627bbf42ca0> tried to link on last rescan, not retrying
Sep 22 04:54:06 red wireplumber[1879]: <WpSiAudioAdapter:0x5627bbf42ca0> tried to link on last rescan, not retrying
Sep 22 04:54:06 red wireplumber[1879]: <WpSiAudioAdapter:0x5627bbf42ca0> tried to link on last rescan, not retrying
Sep 22 04:54:06 red wireplumber[1879]: <WpSiAudioAdapter:0x5627bbf42ca0> tried to link on last rescan, not retrying
```
On that occasion the volume only jumped to 100% after moving the pavucontrol fader, and it happened after the last log line.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3522Microphone indicator in Xfce4 is no longer visible for telegram-desktop since...2023-09-24T13:49:30ZBłażej SzczygiełMicrophone indicator in Xfce4 is no longer visible for telegram-desktop since 0.3.80Since 13caae49b5067f05d7b5cf8ddeb6d345db8cf557 the microphone indicator is no longer visible in xfce4-pulseaudio-plugin 0.4.7.
It is because of the filter for some other apps https://gitlab.xfce.org/panel-plugins/xfce4-pulseaudio-plugin...Since 13caae49b5067f05d7b5cf8ddeb6d345db8cf557 the microphone indicator is no longer visible in xfce4-pulseaudio-plugin 0.4.7.
It is because of the filter for some other apps https://gitlab.xfce.org/panel-plugins/xfce4-pulseaudio-plugin/-/commit/b42363fb8010a81b31399dbaa4d9d5fc2f14fb8f, but now it affects other apps which should display the microphone indicator.
When I add a `fprintf(stderr, "index: %d, name: %s, source index: %d\n", i->index, i->name, i->source);` into a xfce4-pulseaudio-plugin code, before the 13caae49b5067f05d7b5cf8ddeb6d345db8cf557 I can see for Telegram:
```
index: 87, name: Capture Stream, source index: -1
index: 87, name: Capture Stream, source index: -1
index: 87, name: Capture Stream, source index: -1
index: 87, name: Capture Stream, source index: -1
index: 87, name: Capture Stream, source index: 55
```
but after 13caae49b5067f05d7b5cf8ddeb6d345db8cf557 I can see for Telegram:
```
index: 77, name: Capture Stream, source index: -1
index: 77, name: Capture Stream, source index: -1
index: 77, name: Capture Stream, source index: -1
index: 77, name: Capture Stream, source index: -1
```
I don't get any event after source index appears for Telegram. Adding `SPA_PARAM_Latency` to switch triggers the it.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3521CPU spin in pipewire reading inotify fd -> EAGAIN2023-10-17T16:40:25ZAndrew BartlettCPU spin in pipewire reading inotify fd -> EAGAIN<!-- 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.79
- 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.79
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora Linux 37 (Workstation Edition)
- Desktop Environment: Gnome
- Kernel version (`uname -r`): 6.4.15-100.fc37.x86_64
## Description of Problem:
After a system suspend (which may also involve USB device removal if I've switched my KVM, which switches a camera, to the other laptop), pipewire starts to use 100% CPU.
```
strace:
epoll_wait(4, [{events=EPOLLIN, data={u32=3335551552, u64=93964335086144}}, {events=EPOLLIN, data={u32=3335551632, u64=93964335086224}}], 32, 0) = 2
read(33, 0x7fffd0ce0750, 272) = -1 EAGAIN (Resource temporarily unavailable)
read(34, 0x7fffd0ce0750, 272) = -1 EAGAIN (Resource temporarily unavailable)
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=20, events=POLLIN}, {fd=24, events=POLLIN}], 4, 0) = 2 ([{fd=3, revents=POLLIN}, {fd=4, revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
epoll_wait(4, [{events=EPOLLIN, data={u32=3335551552, u64=93964335086144}}, {events=EPOLLIN, data={u32=3335551632, u64=93964335086224}}], 32, 0) = 2
read(33, 0x7fffd0ce0750, 272) = -1 EAGAIN (Resource temporarily unavailable)
read(34, 0x7fffd0ce0750, 272) = -1 EAGAIN (Resource temporarily unavailable)
FD 4 is the epoll FD:
[abartlet@jesse ~]$ cat /proc/139532/fdinfo/4
pos: 0
flags: 02000002
mnt_id: 15
ino: 2074
tfd: 33 events: 19 data: 5575c6d07a40 pos:0 ino:81a sdev:e
tfd: 30 events: 19 data: 5575c6cbbd88 pos:0 ino:25614e sdev:8
tfd: 28 events: 18 data: 5575c6d70790 pos:0 ino:25614b sdev:8
tfd: 29 events: 19 data: 5575c6d70830 pos:0 ino:25614b sdev:8
tfd: 26 events: 19 data: 5575c6d6e3b0 pos:0 ino:81a sdev:e
tfd: 32 events: 19 data: 5575c6cbbdb8 pos:0 ino:81a sdev:e
tfd: 19 events: 19 data: 5575c6bf01c0 pos:0 ino:25613a sdev:8
tfd: 10 events: 19 data: 5575c6b9ae10 pos:0 ino:81a sdev:e
tfd: 35 events: 19 data: 5575c6d07a40 pos:0 ino:81a sdev:e
tfd: 36 events: 19 data: 5575c6d07a90 pos:0 ino:81a sdev:e
tfd: 34 events: 19 data: 5575c6d07a90 pos:0 ino:81a sdev:e
tfd: 37 events: 19 data: 5575c6d08d90 pos:0 ino:255eaa sdev:8
tfd: 5 events: 19 data: 5575c6b87a70 pos:0 ino:81a sdev:e
tfd: 23 events: 19 data: 5575c6bfd2e0 pos:0 ino:25613b sdev:8
tfd: 31 events: 19 data: 5575c6d71df0 pos:0 ino:81a sdev:e
tfd: 40 events: 39 data: 5575c6da4510 pos:0 ino:3dc sdev:5
FD 33 and 34 are Inotify FDs:
[abartlet@jesse ~]$ cat /proc/139532/fdinfo/34
pos: 0
flags: 02004000
mnt_id: 15
ino: 2074
inotify wd:1 ino:b18 sdev:5 mask:c ignored_mask:0 fhandle-bytes:c fhandle-type:1 f_handle:08ed941d180b000000000000
[abartlet@jesse ~]$ cat /proc/139532/fdinfo/33
pos: 0
flags: 02004000
mnt_id: 15
ino: 2074
inotify wd:1 ino:b17 sdev:5 mask:c ignored_mask:0 fhandle-bytes:c fhandle-type:1 f_handle:2dbaf745170b000000000000
Each read call returns -1 and EAGAIN:
Thread 1 "wireplumber" hit Breakpoint 5.1, __GI___libc_read (fd=34, buf=buf@entry=0x7fffd0ce0750, nbytes=nbytes@entry=272) at ../sysdeps/unix/sysv/linux/read.c:25
25 {
(gdb) fin
Run till exit from #0 __GI___libc_read (fd=34, buf=buf@entry=0x7fffd0ce0750, nbytes=nbytes@entry=272) at ../sysdeps/unix/sysv/linux/read.c:25
Thread 1 "wireplumber" hit Breakpoint 5.2, __GI___libc_read (nbytes=272, buf=0x7fffd0ce0750, fd=34) at ../sysdeps/unix/sysv/linux/read.c:26
26 return SYSCALL_CANCEL (read, fd, buf, nbytes);
(gdb) fin
Run till exit from #0 __GI___libc_read (nbytes=272, buf=0x7fffd0ce0750, fd=34) at ../sysdeps/unix/sysv/linux/read.c:26
__GI___libc_read (fd=34, buf=buf@entry=0x7fffd0ce0750, nbytes=nbytes@entry=272) at ../sysdeps/unix/sysv/linux/read.c:24
24 __libc_read (int fd, void *buf, size_t nbytes)
(gdb) fin
Run till exit from #0 __GI___libc_read (fd=34, buf=buf@entry=0x7fffd0ce0750, nbytes=nbytes@entry=272) at ../sysdeps/unix/sysv/linux/read.c:24
impl_on_notify_events (source=0x5575c6d07a90) at ../spa/plugins/v4l2/v4l2-udev.c:429
429 if (len < 0 && errno != EAGAIN)
Value returned is $14 = -1
(gdb) p errno
$15 = 11
```
(11 is EAGAIN on this host)
## How Reproducible:
Happens every now and then, started happening about 3 months ago.
### Steps to Reproduce:
(roughly)
1. suspend laptop
2. switch USB
3. resume laptop
### Actual Results:
pipewire in CPU spin, applications using audio hang
### Expected Results:
Good audio, no hang
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3520Desktop apps become unresponsive when audio is played2023-09-25T09:25:50ZAllan DayDesktop apps become unresponsive when audio is playedOn my laptop, when desktop apps play audio, they become unresponsive - their UIs freeze and can't be interacted with, and the "unresponsive app" dialog pops up shortly afterwards.
I've been experiencing this issue since I installed Fedo...On my laptop, when desktop apps play audio, they become unresponsive - their UIs freeze and can't be interacted with, and the "unresponsive app" dialog pops up shortly afterwards.
I've been experiencing this issue since I installed Fedora 39. There are periods when the bug doesn't happen (possibly for a time after a reboot), but most of the time it does, and when it is active it affects all apps. Examples of affected apps include:
* Firefox, when Whatsapp plays a notification bell
* Settings, when using the sound test window
* Rhythmbox, when playing music
* Totem, when playing a video
* Spotify doesn't play audio, but it doesn't become unresponsive
Pipewire version: 0.3.79
I captured this backtrace while reproducing the issue with gnome-control-center's sound test feature: [backtrace.log](/uploads/e97ba6f2cc371dead704f99ac6d93d7e/backtrace.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3519Question: Simplest way to receive events from pipewire2023-09-20T09:06:34ZAlessandro PeverelliQuestion: Simplest way to receive events from pipewireI'm writing an application in where I would like to know when a input device starts to receive audio. Which could be the better way to reach the goal? And also, are there any examples to take a look?
Thanks for any answer.I'm writing an application in where I would like to know when a input device starts to receive audio. Which could be the better way to reach the goal? And also, are there any examples to take a look?
Thanks for any answer.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3518Skype, voice level of my contact is very low2023-09-21T09:13:28ZpromeneurSkype, voice level of my contact is very low<!-- 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.79
- 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.79
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): openSUSE Tumbleweed
- Desktop Environment: KDE 23.08.1
- Kernel version (`uname -r`): 6.5.3
## Description of Problem:
Since about a week,the voice level of my contact is very low.
Other sound level as call sound are good.
I sent a report to Skype team via the app. But I get no hope to get any answer.
## How Reproducible:
Just use Skype to make a video call
skype 8.103.0.208
### Actual Results:
I hardly listen to the voice of my contact.
All the controls are equal to 100 %
Web.skype.com, there is no problem.
### Expected Results:
I can listen to my contact
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw-dump.log](/uploads/42367959fc5d41fdea71905f656b9b64/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3517Audio randomly cuts out2024-01-14T15:49:50ZCameron JacksonAudio randomly cuts out- PipeWire version (`pipewire --version`): 0.3.80
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Void Linux
- Desktop Environment: Sway
- Kernel version (`uname -r`): 6.3.13
## Description of Problem:
#...- PipeWire version (`pipewire --version`): 0.3.80
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Void Linux
- Desktop Environment: Sway
- Kernel version (`uname -r`): 6.3.13
## Description of Problem:
## How Reproducible:
### Steps to Reproduce:
1. Set Pipewire volume set to 15% - 25%
2. Listen to an audio track that has lots of quiet sections in it
3. This is random, but the most reliable way of reproducing this issue is to listen to the Hans Zimmer Intersteller album on Spotify
### Actual Results:
Audio randomly cuts out sometimes when starting a song and or part-way through a song. Tends to happen during quiet parts. When this happens the audio temporarily cuts out or becomes very very quiet for an unspecified amount of time.
### Expected Results:
Audio plays without interruption
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw-dump.log](/uploads/74c8dc675da7e0add4fcabb57872bc7e/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3516No audio upon resuming playback after pause2023-12-30T22:18:40ZOleksandr KnyshukNo audio upon resuming playback after pause- PipeWire version (`pipewire --version`): 1.0.0
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: GNOME 45.2 (Wayland)
- Kernel version (`uname -r`): 6.6.4-1-clear
## Desc...- PipeWire version (`pipewire --version`): 1.0.0
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: GNOME 45.2 (Wayland)
- Kernel version (`uname -r`): 6.6.4-1-clear
## Description of Problem:
When I listen to music on Spotify, then switch to Firefox to watch YouTube, maybe watch a video in Telegram Desktop, and then return - I have no sound in Spotify when unpausing. The solution is to pause, wait 5 seconds, and unpause the music in the app. I can also kill Spotify, wait ~5 seconds and then open it. This fix doesn't work when I wait less than 5 seconds. It has been happening for about three months. It is worth mentioning that I use [JamesDSP](https://github.com/Audio4Linux/JDSP4Linux).
## How Reproducible:
### Steps to Reproduce:
1. Listen to some music on Spotify
2. Pause it and play some audio in Firefox/Telegram Desktop
3. Come back to Spotify, unpause the music
### Actual Results: No sound
### Expected Results: Sound plays instantly
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/e814d7be9c1201349df20b96eede3960/pw-dump.log)
- `systemctl --user status pipewire.service | curl -F'file=@-' https://0x0.st`: https://0x0.st/HOMM.txthttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3515FFADO device name wrong in example config2023-09-24T13:49:30ZNicolas GoyFFADO device name wrong in example configI am not sure if this is a documentation problem, or a pipewire ffado bug, but on this page
https://docs.pipewire.org/page_module_ffado_driver.html
the example says ` #ffado.devices = [ hw:0 ]`
But I had to use `[ "hw:0" ]`...I am not sure if this is a documentation problem, or a pipewire ffado bug, but on this page
https://docs.pipewire.org/page_module_ffado_driver.html
the example says ` #ffado.devices = [ hw:0 ]`
But I had to use `[ "hw:0" ]` for it to actually work (with quotes).https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3514Exported files in Ardour are silent2023-10-24T09:14:59ZBruno UnnaExported files in Ardour are silent- PipeWire version (`pipewire --version`): 0.3.80
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Cinnamon 5.8.4-1
- Kernel version (`uname -r`): 6.5.3-zen1-1-zen
## Desc...- PipeWire version (`pipewire --version`): 0.3.80
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Cinnamon 5.8.4-1
- Kernel version (`uname -r`): 6.5.3-zen1-1-zen
## Description of Problem:
Export of audio files from Ardour renders them silent. The process doesn't fail, there are no errors nor warnings in Ardour's message log. Only this informational one:
`2023-09-16T08:27:09 [INFO]: Encode command: { /usr/bin/ffmpeg_harvid -f f32le -acodec pcm_f32le -ac 2 -ar 48000 -i pipe:0 -f mp3 -acodec mp3 -q:a 2 -metadata comment=Created with Ardour -y /home/bruno/Music/ardour/black rose/export/black rose_2023-09-16.mp3 }`
The produced files can be opened in other programs (audio players), but they are completely silent for the length of the song. Tried to produce MP3 and Ogg vorbis formats, with the same result.
This same process works flawlessly with pipewire 0.3.77.
## How Reproducible:
Create a song, add some audio to it, then go to "Session->Export->Export to Audio File(s)".
# Additional Info (as attachments):
- [pw-dump.log](/uploads/38e778c79f3d97eefb62aa5653ae3020/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3513Question about device name of USB headsets2024-03-03T13:48:08ZLuca WeissQuestion about device name of USB headsetsHi,
I'm wondering why pipewire seems to not pick the name (`device.product.name`) from the USB product that it reports (so `iProduct` value) but seemingly picks the name from the hwdata database (with USB VID/PID) which is basically jus...Hi,
I'm wondering why pipewire seems to not pick the name (`device.product.name`) from the USB product that it reports (so `iProduct` value) but seemingly picks the name from the hwdata database (with USB VID/PID) which is basically just describing the USB audio controller, not the name of the device you have plugged in.
The `device.nick` is actually set to the correct name but e.g. via pulseaudio only the other "generic"/ugly name is shown.
Is there a logic to this or some way to override it for a device, or is the solution e.g. that the USB VID/PID *needs* to be unique for this specific product?https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3512Pipewire-jack: Audio stuttering/crackling and Ardour crash when adjusting sys...2023-12-22T18:48:16ZSkyggePipewire-jack: Audio stuttering/crackling and Ardour crash when adjusting system volume<!-- 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.79 (tried also with compiled current master "pw-uninstalled")
- Distribution and...<!-- 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.79 (tried also with compiled current master "pw-uninstalled")
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):"Ubuntu 23.04"
- Desktop Environment: KDE Plasma 5.27.4
- Kernel version (`uname -r`): 6.2.0-1012-lowlatency
## Description of Problem:
If I open a large session with many tracks in Ardour (let's say 20 tracks), and if Ardour is using JACK backend (Pipewire-jack in this case), then if I adjust the system global volume I get
distorted, popping, crackling audio playback. If I'm adjusting volume long enough - Ardour crashes.
I know. You probably are going to say: "This is Ardour issue". I reported this error already here: https://tracker.ardour.org/view.php?id=9447
And they say "this is Pipewire bug".
Short video illustrating this problem: https://youtu.be/l-GYdu2_RpU
## How Reproducible: Always
### Steps to Reproduce:
1. Open Ardour (7.5 or current master, it doesn't matter) under Pipewire-Jack,
2. Load heavy session or create 20 audio tracks,
3. Play something, not necessary in Ardour, it can be media player (Clementine, for example, or youtube video in a browser),
4. Try to play with system volume.
### Actual Results:
Sound playback distortion/crackling. After a while - Ardour crashes.
### Expected Results:
Sound volume change with no influence on playback smoothness.
# Additional Info (as attachments):
The version 0.3.78, which had other bugs like #3475 and #3477 was really better in this matter.
Really and significantly better. But the other issues were much worse.
Thaks!
Skyggehttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/35111.0 release / pipewire versioning2023-10-14T14:49:46ZArtem S. Tashkinov1.0 release / pipewire versioningPipeWire has been production ready for quite some time already.
Can we change its versioning to something more appropriate, i.e. name the next release 1.0.0 or something?
Actually, I don't like plain digits any longer.
It would be gre...PipeWire has been production ready for quite some time already.
Can we change its versioning to something more appropriate, i.e. name the next release 1.0.0 or something?
Actually, I don't like plain digits any longer.
It would be great if PipeWire adopted the YEAR.RELEASE numbering scheme, i.e. the first release in 2023 would be 2023.1, the second 2023.2, etc. etc. etc. This way it's easy to understand whether your PipeWire release is fresh/up to date or not. Or maybe if 2023 sounds too big, you could use 23.1, 23.2, etc. It's unlikely that we'll be using PipeWire in the 22nd century.
So, I'm looking forward to PipeWire adopting it as well.
Ultimately it's up to you, so you may as well dismiss this proposal altogether :smile:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3510Pipewire won't start2023-09-15T11:54:28ZMoo SekaPipewire won't startI'm on Artix, with runit. I'm using Sway as my WM.
I've installed all the necessary packages, like pipewire, pipewire-pulse, wireplumber...
When starting pipewire from the terminal I get nothing, but when doing it from a bash script I ge...I'm on Artix, with runit. I'm using Sway as my WM.
I've installed all the necessary packages, like pipewire, pipewire-pulse, wireplumber...
When starting pipewire from the terminal I get nothing, but when doing it from a bash script I get all these errors:
```
W 19:05:27.794710 pw ../pipewire/spa/plugins/bluez5/upower.c:54:upower_get_percentage_properties_reply: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
[0:09:37.009062706] [2701] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
[0:09:37.009076884] [2701] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
[0:09:37.009097068] [2701] INFO Camera camera_manager.cpp:284 libcamera v0.1.0
W 19:05:27.916367 spa.bluez5 ../pipewire/spa/plugins/bluez5/bluez5-dbus.c:5254:get_managed_objects_reply: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
M 19:05:27.958049 wp-device ../wireplumber/lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.alsa.acp.device' could not be loaded; is it installed?
W 19:05:27.958075 script/alsa alsa.lua:205:createDevice: Failed to create 'api.alsa.acp.device' device
W 19:05:28.096881 spa.alsa ../pipewire/spa/plugins/alsa/acp/alsa-ucm.c:976:probe_volumes: Path Mic ACP LED is not a volume or mute control
[0:09:37.320369342] [2699] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
[0:09:37.320382263] [2699] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
[0:09:37.320409431] [2699] INFO Camera camera_manager.cpp:284 libcamera v0.1.0
W 19:05:28.120053 m-portal-permissio ../wireplumber/modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x557750057730> Failed to call Lookup: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
W 19:05:28.120659 m-portal-permissio ../wireplumber/modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x557750057730> Failed to call Lookup: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
^CM 19:11:35.043456 wireplumber ../wireplumber/src/main.c:372:signal_handler: stopped by signal: Interrupt
M 19:11:35.046788 wireplumber ../wireplumber/src/main.c:364:on_disconnected: disconnected from pipewire`
```
I'd really appreciate some help. Thank you for your timehttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3509A single frozen application blocks audio output on the entire system2024-03-22T08:52:38Zsfan5A single frozen application blocks audio output on the entire system- PipeWire version (`pipewire --version`): 0.3.79
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Xfce
- Kernel version (`uname -r`): 6.5.2-arch1-1
## Description of Prob...- PipeWire version (`pipewire --version`): 0.3.79
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: Xfce
- Kernel version (`uname -r`): 6.5.2-arch1-1
## Description of Problem:
A single frozen application will cause all audio output to freeze.
## How Reproducible:
OpenAL makes this very easy to reproduce and has [a native PW backend](https://github.com/kcat/openal-soft/blob/master/alc/backends/pipewire.cpp) in case it matters.
```c
#include <stddef.h>
#include <assert.h>
#include <signal.h>
#include <AL/al.h>
#include <AL/alc.h>
int main()
{
ALCdevice *dev = alcOpenDevice(NULL);
assert(dev);
ALCcontext *ctx = alcCreateContext(dev, NULL);
assert(ctx);
ALCboolean ok = alcMakeContextCurrent(ctx);
assert(ok);
kill(0, SIGSTOP);
alcMakeContextCurrent(NULL);
alcDestroyContext(ctx);
alcCloseDevice(dev);
return 0;
}
```
compile with `gcc test.c -o test $(pkg-config --libs openal)`
### Steps to Reproduce:
1. Use a music player or anything else to output audio
2. Run `./test`
### Actual Results:
3. Notice that all audio output has frozen
Once test is resumed (or terminated) audio output instantly works again.
### Expected Results:
3. Nothing happens
# Additional Info (as attachments):
[pw-dump.log](/uploads/a7a47caaa4d8bfa4d14745bc24e93e0e/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3508Disconnection after a removal event on Redmi Buds 3 Pro2023-09-15T08:56:25ZMarco RodolfiDisconnection after a removal event on Redmi Buds 3 Pro<!-- 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...<!-- 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.79
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora Linux 38.20230912.0 (Bazzite)
- Desktop Environment: KDE Plasma
- Kernel version (`uname -r`): 6.4.14-200.fc38.x86_64
- BlueZ version (`bluetoothctl --version`): 5.69
- `lsusb`:
```
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 13d3:3553 IMC Networks Bluetooth Radio
Bus 003 Device 002: ID 28de:1205 Valve Software Steam Deck Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 004: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 28de:2001 Valve Software USB Billboard Device
Bus 001 Device 004: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
- Bluetooth devices:
```
Device F4:73:35:83:99:20 Keyboard K480
Device 6C:D3:EE:31:A3:3F Redmi Buds 3 Pro
Device C4:0A:CF:61:6F:5B MX Master 3 Mac
```
## Description of Problem:
I think I've found a Bluetooth multipoint audio bug, but I'm not sure if the issue is in Bluez or here, so this has an equivalent post on the bluez bugtracker with packet captures [here](https://github.com/bluez/bluez/issues/585).
I have basically two issues with this audio buds, but I have the feeling that they are interlinked together (the cause of both issues stems from the same root cause).
Issues:
1. After a random time interval (usually between one hour and four hours), the buds stop reproducing audio for 10 seconds before disconnecting and then sometimes reconnecting fine (typically one of the two sync first and the other then sync back). Other times they begin a dance of one connects and not the other and then the two swaps roles, until the end state which can be one of this two:
- The two buds resync and resume playback fine
- Both buds disconnect and no audio comes out even forcing a reconnect. This is usually fixed by either cycling the host bluetooth adapter or by putting them inside the case and pulling them out again.
2. If I pull one of the two buds out, sometimes the above trigger in the same way. If I only use one of the two this doesn't seems to happen (after 10 events of removal and reinsert nothing happens, this usually is triggered after one of two tries).
3. Regardless of the issues above, no events for audio pause and resume are generated on removal.
## How Reproducible:
Quite easily reproducible on my Steam Deck (and this do not happens on my Qualcomm Android Device).
### Steps to Reproduce:
1. Buy a pair of Redmi Buds 3 Pro
2. Connect to a computer
3. Play music while wearing both
4. Try to pull one out of your ear a couple of times
### Actual Results:
Audio stop playing and the buds disconnect from the host
### Expected Results:
The music pauses correctly and resume on reinsertion.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:[pw-dump.tar.gz](/uploads/5a364d399f07c0442a645b8b0a331dbc/pw-dump.tar.gz)
- Bluetooth debug log, see [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth):[pipewire-bluez.tar.gz](/uploads/34338524a51e475f02f97e959c7082ea/pipewire-bluez.tar.gz)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3507[Feature request] Improvements of opus support in module-rtp2023-09-13T15:33:01ZMatthias Larisch[Feature request] Improvements of opus support in module-rtpDear community,
I am evaluating usage of module-rtp-sink in a setup to forward audio streams to clients via WebRTC. A really simple stack could consist of pipewire -> module-rtp-sink -> janus (WebRTC Server) -> clients.
Unfortunately, ...Dear community,
I am evaluating usage of module-rtp-sink in a setup to forward audio streams to clients via WebRTC. A really simple stack could consist of pipewire -> module-rtp-sink -> janus (WebRTC Server) -> clients.
Unfortunately, module-rtp-sink does not yet provide any means to control the opus encoder despite from sample rate (which I suspect might not be working, as in https://gitlab.freedesktop.org/pipewire/pipewire/-/blame/master/src/modules/module-rtp/opus.c#L326 there are hard coded frame counts that only match for 48 kHz sample rate (see https://opus-codec.org/docs/opus_api-1.2/group__opus__multistream.html#gaff832211e572536941b9d6094f9f42ce) ) and channel count.
In my application, I would like to enable FEC encoding.
Is it feasible to develop module-rtp further or should I rely on other means e.g. use gstreamer to forward audio from pipewire to RTP?