pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2024-03-04T21:23:02Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2027Music over bluetooth stop after some time (~30s)2024-03-04T21:23:02ZWillowMusic over bluetooth stop after some time (~30s)Seems to happen when the sound is over bluetooth devices. Pipewire then looks frozen. Not able to play any sound. It then does not reply anymore to pulsemixer or pavucontroll "Connection to pulseaudio failed"
I also got this in my logs ...Seems to happen when the sound is over bluetooth devices. Pipewire then looks frozen. Not able to play any sound. It then does not reply anymore to pulsemixer or pavucontroll "Connection to pulseaudio failed"
I also got this in my logs :
```
[W][00093.741378] mod.protocol-pulse | [ reply.c: 73 reply_error()] client 0xffff84a32030 [Music Player Daemon]: ERROR command:-1 (invalid) tag:3 erro
r:25 (I/O error)
```
Logs continiously output :
```
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:44 command 'setvol' failed: problems setting volume
2022/01/16 18:11:44 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:45 Volume changed to 0
2022/01/16 18:11:45 command 'setvol' failed: problems setting volume
2022/01/16 18:11:46 Volume changed to 0
2022/01/16 18:11:46 command 'setvol' failed: problems setting volume
2022/01/16 18:11:46 Volume changed to 0
2022/01/16 18:11:46 command 'setvol' failed: problems setting volume
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3555pipewire-pulse: rename card's ports2024-03-04T19:23:09Zdyegoaureliopipewire-pulse: rename card's portsIs it possible to define a name to pulseaudio card's that were provided by pipewire?
for example, pipewire pulse server creates this card, with the following profiles and ports
I'd like to know if it's possible to rename them.
```
Ca...Is it possible to define a name to pulseaudio card's that were provided by pipewire?
for example, pipewire pulse server creates this card, with the following profiles and ports
I'd like to know if it's possible to rename them.
```
Card #47
Name: alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic
[...]
Profiles:
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
HiFi: Play HiFi quality Music (sinks: 4, sources: 2, priority: 8000, available: yes)
pro-audio: Pro Audio (sinks: 5, sources: 3, priority: 1, available: yes)
Active Profile: HiFi
Ports:
[Out] HDMI3: HDMI / DisplayPort 3 Output (type: HDMI, priority: 700, latency offset: 0 usec, availability group: HDMI/DP,pcm=5, not available)
Properties:
port.type = "hdmi"
port.availability-group = "HDMI/DP,pcm=5"
card.profile.port = "0"
Part of profile(s): HiFi
[Out] HDMI2: HDMI / DisplayPort 2 Output (type: HDMI, priority: 600, latency offset: 0 usec, availability group: HDMI/DP,pcm=4, not available)
Properties:
port.type = "hdmi"
port.availability-group = "HDMI/DP,pcm=4"
card.profile.port = "1"
Part of profile(s): HiFi
[Out] HDMI1: HDMI / DisplayPort 1 Output (type: HDMI, priority: 500, latency offset: 0 usec, availability group: HDMI/DP,pcm=3, not available)
Properties:
port.type = "hdmi"
port.availability-group = "HDMI/DP,pcm=3"
card.profile.port = "2"
Part of profile(s): HiFi
[Out] Speaker: Speaker (type: Speaker, priority: 100, latency offset: 0 usec, availability unknown)
Properties:
port.type = "speaker"
card.profile.port = "3"
Part of profile(s): HiFi
[Out] Headphones: Headphones (type: Headphones, priority: 200, latency offset: 0 usec, availability group: Headphone Mic, not available)
Properties:
port.type = "headphones"
port.availability-group = "Headphone Mic"
card.profile.port = "4"
Part of profile(s): HiFi
[In] Headset: Headset Mono Microphone (type: Headset, priority: 300, latency offset: 0 usec, availability group: Headphone Mic, not available)
Properties:
port.type = "headset"
port.availability-group = "Headphone Mic"
card.profile.port = "5"
Part of profile(s): HiFi
[In] Mic2: Headphones Stereo Microphone (type: Mic, priority: 200, latency offset: 0 usec, availability group: Headphone Mic, not available)
Properties:
port.type = "mic"
port.availability-group = "Headphone Mic"
card.profile.port = "6"
Part of profile(s): HiFi
[In] Mic1: Digital Microphone (type: Mic, priority: 100, latency offset: 0 usec, availability unknown)
Properties:
port.type = "mic"
card.profile.port = "7"
Part of profile(s): HiFi
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3893Audio stops when starting pavucontrol - only on CM106-like devices2024-03-04T08:25:23ZFabien DevauxAudio stops when starting pavucontrol - only on CM106-like devicesFirst, sorry if the description sounds ridiculous. Since a month or more I experience such issue after a soundcard change.
Using bluetooth speakers don't expose the problem(s).
I'm not sure where to start but I figured that clearing wire...First, sorry if the description sounds ridiculous. Since a month or more I experience such issue after a soundcard change.
Using bluetooth speakers don't expose the problem(s).
I'm not sure where to start but I figured that clearing wireplumber's state & restarting it sometimes fixed my problem, then it happens agian after some time.
In short, as soon as I open pavucontrol the audio stops, if I'm playing it on CM106 soundcard (using bluetooth speakers I get no issue).
3 seconds after closing pavucontrol, the audio is back.
When I run pavucontrol, the following events are emitted:
```
Event 'new' on client #644
Event 'new' on source-output #645
Event 'new' on source-output #646
Event 'new' on source-output #647
Event 'change' on source-output #645
Event 'change' on source-output #646
Event 'change' on source-output #647
Event 'new' on source-output #648
Event 'change' on source-output #645
Event 'change' on source-output #646
Event 'change' on source-output #647
Event 'change' on source-output #646
Event 'change' on source-output #648
Event 'change' on source #65
Event 'change' on card #53
Event 'change' on source-output #645
Event 'change' on source-output #646
Event 'change' on source-output #648
Event 'change' on sink #338
Event 'change' on source #338
Event 'change' on card #51
Event 'change' on source-output #647
Event 'change' on source-output #648
```
When I close it:
```
Event 'remove' on source-output #645
Event 'remove' on source-output #646
Event 'remove' on source-output #647
Event 'remove' on source-output #648
Event 'remove' on client #644
Event 'change' on source #65
```
After some time when the audio is recovered:
```
Event 'change' on source #65
Event 'change' on sink #338
Event 'change' on source #338
```
I'm also attaching the dumps "before" starting pavucontrol and "after" (when it's running, and audio is "muted")
- [before](/uploads/4605c725b35807e141803909f7a75cfa/before)
- [after](/uploads/cda3a864fd9a215e709552401156a18d/after)
Note that I experience other problems since the same date when using discord: I can hear the UI's sounds but not the voice chats, sometimes I can hear it for a fraction of second when the discussion starts.
I'll try to find a software version combination which isn't exposing the issue but I experience this problem for a while and still didn't managed to do so.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3876If a filter-chain is loaded SPDIF no longer works.2024-03-04T08:20:10ZAdolfo RodriguesIf a filter-chain is loaded SPDIF no longer works.Unless I remove my filter-chain spdif does not work. I have my convolver config in ~/.config/pipewire/pipewire.conf.d/convolver.conf ,
If I remove convolver.conf and restart pipewire service, spdif starts working again.
![image](/uploa...Unless I remove my filter-chain spdif does not work. I have my convolver config in ~/.config/pipewire/pipewire.conf.d/convolver.conf ,
If I remove convolver.conf and restart pipewire service, spdif starts working again.
![image](/uploads/65e4145c214717e4531508b4413115ce/image.png)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3865Bluetooth audio stutter - regression2024-03-04T03:15:57ZShaked8374Bluetooth audio stutter - regression<!-- 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`):
1.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`):
1.0.3
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
Arch Linux
- Desktop Environment:
Gnome 45.4
- Kernel version (`uname -r`):
6.7.5-arch1-1
- BlueZ version (`bluetoothctl --version`):
5.72
- `lsusb`:
```
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 056a:51b7 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 003: ID 5986:114e Bison Electronics Inc. Integrated Camera
Bus 001 Device 007: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 012: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader
Bus 002 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
```
- Bluetooth devices:
```
Device 88:C9:E8:CF:1C:36 WH-1000XM5
Device F0:AE:66:9A:EE:25 soundcore P20i
```
## Description of Problem:
Bluetooth audio started to stutter frequently a few weeks ago (was perfect before).
Tested 2 headsets (Soundcore P20, Sony WH-1000XM5) with BT various codecs (SBC, AAC, LDAC).
Does not happen in "hands free" mode or when playing to the internal speakers.
During playing CPUs seems in low levels and the system is not under any load
RTkit installed and seems to work (set pipewire and wireplumber processed to -11)
Tried to change various params (clock rate, allowed rates...) with no improvment.
## How Reproducible:
Happens almost all the time.
Simply start playing audio file locally or from the internet (Youtube, Soundcloud, etc...)
### Actual Results:
Frequent stutter of the audio
### Expected Results:
Should play smooth without interruptions.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw-dump.log](/uploads/05d697da6c7c742ed8d9b90326dd367c/pw-dump.log)
- BT debug
[p20-pipewire-bluez.log](/uploads/0fc0f3743934d141dcf05d9f2a32d72a/p20-pipewire-bluez.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/3885cannot set freq 192000 (v2/v3): err -32 after susped resume with sound blaste...2024-03-03T10:53:23ZMarc Debruynecannot set freq 192000 (v2/v3): err -32 after susped resume with sound blaster x g6- PipeWire version (`pipewire --version`): media-video/pipewire-9999::gentoo
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): PRETTY_NAME="Gentoo Linux"
- Desktop Environment: Gnome
- Kernel version (`uname...- PipeWire version (`pipewire --version`): media-video/pipewire-9999::gentoo
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): PRETTY_NAME="Gentoo Linux"
- Desktop Environment: Gnome
- Kernel version (`uname -r`): 6.6.13-gentoo-x86_64
## Description of Problem: journalctl msg cannot set freq 192000 (v2/v3): err -32 after susped resume with sound blaster x g6
no sound, audacious stops playing 96000 flacs play ok on Panasonic SA-PMX152 all freq ok
## How Reproducible:
suspend resume and play 192000hz flac
### Steps to Reproduce:
1. Start system, play a 192000hz flac on soundblaster: ok
2. Suspend Resume, play a 192000hz flac on soundblaster: NOK
3.
### Actual Results:
msg cannot set freq 192000 (v2/v3): err -32 after susped resume with sound blaster x g6, no sound
### Expected Results:
Sound should play
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`
[pw-dump.log](/uploads/8f9be72573de413809f073d5ee10e263/pw-dump.log)
- cat /proc/asound/card0/stream0:
from Panasonic
[stream0](/uploads/e0236ceb9255f4bf0f454203ff5c90ea/stream0)
- cat /proc/asound/card1/stream0:
- from soundblaster
- [stream1](/uploads/e988ac43db31e4bdc56b172ad35906a2/stream1)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3890Audio normalization with ladspa and a filter chain2024-03-02T23:24:51ZHaden PikeAudio normalization with ladspa and a filter chain* PipeWire version: libpipewire 1.0.3
* Distribution: Arch Linux
* Desktop Environment: Stump WM
* Kernel version: 6.7.6
## Description of Problem:
I am new to filter chains. When attempting to setup volume normalizing using ladspa in ...* PipeWire version: libpipewire 1.0.3
* Distribution: Arch Linux
* Desktop Environment: Stump WM
* Kernel version: 6.7.6
## Description of Problem:
I am new to filter chains. When attempting to setup volume normalizing using ladspa in a filter chain, the Sink gets created, but the Sink does nothing.
Running:
```
pactl load-module module-ladspa-sink sink_name=Normalizer plugin=sc4_1882 label=sc4 control=1,1.5,401,-12,6,5,12
pactl load-module module-ladspa-sink sink_name=Normalized master=Normalizer plugin=fast_lookahead_limiter_1913 label=fastLookaheadLimiter control=5,-10,0.8
```
works as expected.
PIPEWIRE_DEBUG=3 doesnt give me any errors. Am I missing something, or is this a bug?
## How to Reproduce:
Put normalize.conf in pipewire.conf.d.
normalize.conf:
```
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 ]
}
}
}
]
```
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 normalized.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3835`libpipewire-module-roc-source` module fails to load on boot (`EADDRINUSE`)2024-03-02T21:32:21Zmisuzu`libpipewire-module-roc-source` module fails to load on boot (`EADDRINUSE`)<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 1.0.1
- 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`): 1.0.1
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): NixOS 24.05.20240131.b8b232a
- Desktop Environment: hyprland
- Kernel version (`uname -r`): 6.6.14
## Description of Problem:
`libpipewire-module-roc-source` module fails to load on boot with `address already in use` message, but manual restart fixes the issue (`systemctl --user restart pipewire.service`). Changing ports doesn't help.
## How Reproducible:
### Steps to Reproduce:
1. [Configure](https://gitlab.com/misuzu/nixos-configuration/-/blob/d94ece5826c852e851adb707c0ac3b1b30d17050/common/desktop/default.nix#L4) [`libpipewire-module-roc-source`](https://gitlab.com/misuzu/nixos-configuration/-/blob/d94ece5826c852e851adb707c0ac3b1b30d17050/common/pipewire-roc-source.nix)
2. Reboot
3. `libpipewire-module-roc-source` fails to load, manual restart is needed
### Actual Results:
```
% journalctl --user -u pipewire.service
-- Boot 32645ccf0a034c0b925d0ae92c70ffe4 --
Feb 04 13:56:15 erika systemd[3569]: Started PipeWire Multimedia Service.
Feb 04 13:56:15 erika pipewire[3858]: 13:56:15.909 [3943] [err] roc_netio: udp receiver: <udprecv 0x7fc4e0000b88 bind=0.0.0.0:10001>: uv_udp_bind(): [EADDRINUSE] address already in use
Feb 04 13:56:15 erika pipewire[3858]: 13:56:15.910 [3943] [err] roc_netio: network loop: can't add udp receiver port 0.0.0.0:10001: can't start udp receiver
Feb 04 13:56:15 erika pipewire[3858]: 13:56:15.910 [3858] [err] roc_node: receiver node: can't bind audiosrc interface of slot 0: can't bind interface to local port
Feb 04 13:56:15 erika pipewire[3858]: 13:56:15.910 [3858] [err] roc_node: receiver node: marking slot 0 as broken, it needs to be unlinked
Feb 04 13:56:15 erika pipewire[3858]: 13:56:15.910 [3858] [err] roc_api: roc_receiver_bind(): operation failed
Feb 04 13:56:15 erika pipewire[3858]: mod.roc-source: can't connect roc receiver to local source address
Feb 04 13:56:15 erika pipewire[3858]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Feb 04 13:56:16 erika pipewire[3858]: [0:00:30.797927116] [3858] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Feb 04 13:56:16 erika pipewire[3858]: [0:00:30.798203618] [3858] INFO Camera camera_manager.cpp:284 libcamera v0.1.0
Feb 04 13:56:28 erika pipewire[3858]: mod.x11-bell: X11 I/O error handler called on display :0
Feb 04 13:56:28 erika pipewire[3858]: mod.x11-bell: X11 display (:0) has encountered a fatal I/O error
Feb 04 13:56:54 erika systemd[3569]: Stopping PipeWire Multimedia Service...
Feb 04 13:56:54 erika systemd[3569]: Stopped PipeWire Multimedia Service.
Feb 04 13:56:54 erika systemd[3569]: Started PipeWire Multimedia Service.
Feb 04 13:56:54 erika pipewire[5701]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Feb 04 13:56:54 erika pipewire[5701]: [0:01:09.150798834] [5701] INFO IPAManager ipa_manager.cpp:143 libcamera is not installed. Adding '/nix/store/src/ipa' to the IPA search path
Feb 04 13:56:54 erika pipewire[5701]: [0:01:09.150935593] [5701] INFO Camera camera_manager.cpp:284 libcamera v0.1.0
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: stream error: no target node available
Feb 04 13:56:54 erika pipewire[5701]: mod.roc-source: error id:2 seq:7 res:-2 (No such file or directory): no target node available
Feb 04 13:57:04 erika pipewire[5701]: mod.x11-bell: X11 I/O error handler called on display :0
Feb 04 13:57:04 erika pipewire[5701]: mod.x11-bell: X11 display (:0) has encountered a fatal I/O error
% cat /etc/pipewire/pipewire.conf.d/*
{
"context.modules": [
{
"args": {
"fec.code": "ldpc",
"source.name": "PipeWire ROC source",
"source.props": {
"node.name": "roc-source"
}
},
"flags": [
"nofail"
],
"name": "libpipewire-module-roc-source"
}
]
}
```
### Expected Results:
Manual restart is not needed.
Maybe https://github.com/roc-streaming/roc-toolkit/pull/520 could fix this?
# Additional Info (as attachments):
- [pw-dump.log](/uploads/a17e54e185cfa912605a4ddac9de881d/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3889Tikk Sound at the Start of the Voice with handsfree on debian2024-03-02T19:14:58Zmasume dehghanTikk Sound at the Start of the Voice with handsfree on debianAt the beginning of the sound with handsfree، a Tikk sound is played.
This happens only once in each import of handsfree.
This happens only with handsfree.
Speaker is good.
I use PipeWire.
`Audio:
Device-1: Intel Haswell-ULT HD Audio...At the beginning of the sound with handsfree، a Tikk sound is played.
This happens only once in each import of handsfree.
This happens only with handsfree.
Speaker is good.
I use PipeWire.
`Audio:
Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel
Device-2: Intel 8 Series HD Audio driver: snd_hda_intel
API: ALSA v: k6.6.15-amd64 status: kernel-api
Server-1: PipeWire v: 1.0.3 status: active
`https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3887Soundblaster AE-7 no Sound on many distros.2024-03-02T18:46:56ZPeter SchnitzlerSoundblaster AE-7 no Sound on many distros.<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):1.0.3
- 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`):1.0.3
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):Fedora 39
- Desktop Environment: GNOME 45
- Kernel version (`uname -r`): 6.5
## Description of Problem:
I tried various distros for my gaming PC and could get the sound only with Ubuntu after jumping through some hoops. I suspect that this is because Ubuntu only has PipeWire Version 0.3.79.
P.S. You need to plug something in the speaker output to make the headphone output available. An old adapter plug works, which is weird. Alternatively, switch between outputs in Alsamixer.
P.P.S. Found a recommendation to switch to PulseAudio on the Fedora forum. That did not work either.
## How Reproducible:
Always reproducible
### Steps to Reproduce:
1. Have a Creative Soundblaster AE-7
2. Do the out-of-the-box installation of Fedora\Ubuntu
3. Go to Sound settings.
4. Fail to find the headphone output.
5. Plug your old headphones into the speaker output while the new headphones stay in the headphone output.
6. Select the headphone output.
### Actual Results:
There is no sound on Fedora on either output\Sound on Ubuntu on both outputs
### Expected Results:
Sound
# Additional Info (as attachments):grinning:
[pwdump_fedora.json](/uploads/dd6ab05e6a8fe6efc2652b3addf89a10/pwdump_fedora.json)
[pwdumpUbuntu_1_.json](/uploads/62bbe7ff2efd8e55ff2ca36668b5a438/pwdumpUbuntu_1_.json)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2240`pipewiresink` runs out of buffers?2024-03-01T17:13:29ZSimonas Kazlauskas`pipewiresink` runs out of buffers?- PipeWire version (`pipewire --version`): 0.3.48
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): NixOS 22.05 (Quokka)
- Desktop Environment: N/A
- Kernel version (`uname -r`): 5.15.22
## Description of P...- PipeWire version (`pipewire --version`): 0.3.48
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): NixOS 22.05 (Quokka)
- Desktop Environment: N/A
- Kernel version (`uname -r`): 5.15.22
## Description of Problem:
Playing certain tracks in a media player that uses `playbin` and a `pipewiresink` produces audio that stutters at a rate of, I don't know, 10Hz or so, as if somebody was holding a play-pause button.
The `pipewiresink` element keeps reporting
```
0:00:01.312268926 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.397642242 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.483041757 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.568368025 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.653750805 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.739049187 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.824434999 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
0:00:01.909794377 3365414 0x7f365c040d20 WARN pipewirepool gstpipewirepool.c:184:acquire_buffer: queue empty
```
every time a stutter event occurs. These log messages and the stutters go away as soon as I connect the output's `monitor_*` endpoints to audacity, but remain if they are connected to easyeffects or pw-record. Here's a recording: ![yuck](/uploads/9d6c57074ac2a75d5462b87422a312e4/yuck.mp3)
Attaching a `GST_DEBUG=5` log excerpt: [log](/uploads/68c9d171d7abaed2d77dddf661cac34a/log)
## How Reproducible:
Sometimes. Seems to require a specific media file, and a specific pipewire connections. Probably depends on hardware as well (Intel Corporation Comet Lake PCH-LP cAVS.)
### Steps to Reproduce:
I'm not entirely sure! This comes up occasionally when I'm listening to music with quodlibet. I can see some symptoms when using `gst-launch` too:
```
env GST_DEBUG=3 gst-launch-1.0 playbin uri="file://$PWD/some.mp3" audio-sink=pipewiresink
```
but without the stutters.
### Actual Results:
See Description of the Problem section above.
### Expected Results:
`pipewiresink` delivers audio properly at all times (just like it does when I use the patchbay to connect the audio device's monitor into audacity)
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [dump.log](/uploads/10cf1cf403680830c8d2a5c7875b2a9d/dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3884pipewiresrc timeout with no connections (autoconnect = false)2024-03-01T17:09:30ZDouglas Cooperpipewiresrc timeout with no connections (autoconnect = false)<!-- 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.81
- 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.81
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): yocto
- Desktop Environment: none
- Kernel version (`uname -r`): 6.4.0-linaro-lt-qcom+
## Description of Problem:
when creating a gst pipeline using `pipewiresrc` the element never pre-rolls and then times out if i dont connect in a short period of time. ideally, the app would stay alive indefinitely without a connection. if i make a connection shortly after I launchthe app, the element behaves as expected. on a related note, if i make a connection but then disconnect and reconnect, the element no longer processes buffers and i have to restart the app.
## How Reproducible:
`gst-launch-1.0 pipewiresrc client-name=sender autoconnect=false ! audioconvert ! audioresample ! mulawenc ! rtppcmupay ! .send_rtp_sink rtpsession name=session .send_rtp_src ! udpsink host=127.0.0.1 port=50000`
### Steps to Reproduce:
1. launch the app and wait
### Actual Results:
```
Setting pipeline to PAUSED ...
Failed to set pipeline to PAUSED.
Setting pipeline to NULL ...
Freeing pipeline ...
```
### Expected Results:
this is the output of `pipewiresink` when i pass it `stream-properties="stream-properties,node.autoconnect=false"`.
```
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
```
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3878Pipewire BlueZ LE Audio - Pipewire on Sink didn't receive data2024-03-01T10:49:57ZAnjaneyulu SanaPipewire BlueZ LE Audio - Pipewire on Sink didn't receive data<!-- 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`): com...<!-- 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`): commit id 84699032b (built from source)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu 22.04.3 LTS
- Desktop Environment:
- Kernel version (`uname -r`): 6.5.0-21-generic
- BlueZ version (`bluetoothctl --version`): bluetoothctl: 5.72 (built from source)
- `lsusb`:
```
# paste the output of "lsusb" here
```
- Bluetooth devices:
On Sink
- 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 005: ID 8087:0026 Intel Corp. AX201 Bluetooth
- Bus 001 Device 004: ID 0c45:6a09 Microdia Integrated_Webcam_HD
- Bus 001 Device 003: ID 0a5c:5843 Broadcom Corp. 58200
- Bus 001 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- On Source
- Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 003 Device 004: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
- Bus 003 Device 003: ID 413c:2106 Dell Computer Corp. QuietKey Keyboard
- Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth
- Bus 003 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth
- 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
```
# paste the output of "bluetoothctl devices" here
```
## Description of Problem:
We are trying to establish LE audio streaming between two Ubuntu devices.
These devices have Intel AX210 controllers, Bluez 5.72 (built from Source), pipewire (built from source).
After establishing connection between these two devices, stream data using pw-play.
It is observed that source is transmitting data (confirmed with wireshark), Sink is receiving data at ISO socket level (confirmed with wireshark). But on Sink, transport state did not update from pending to active.
## How Reproducible:
Everytime
### Steps to Reproduce:
1. Run (on both devices) 5.72 version of bluetoothd with following changes in main.conf
ControllerMode = le
Experimental = true
KernelExperimental = 6fbaf188-05e0-496a-9885-d6ddfdb4e03e
2. Run pipewire (built from source) on both devices
3. Advertise on Sink and Connect from Source using bluetoothctl
On Sink
select <controller>
power on
advertise on
On Source
select <controller>
power on
scan le
scan off (once the device is found)
connect <remote device>
### Actual Results:
Transport of sink is in pending state forever
### Expected Results:
Transport should be active and pipewire should be receiving LE audio data
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:[pipewire_logs_src_26_02_2024.txt](/uploads/e9b1b00d75a4291ba7ad4b04151ab5bc/pipewire_logs_src_26_02_2024.txt)
[pipewire_sink_logs_26_02_2024.txt](/uploads/23c1a3a3a51cdda7a0af8308af195e28/pipewire_sink_logs_26_02_2024.txt)
- Bluetooth debug log, see [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth):[bluez_logs_sink_26_02_2024.txt](/uploads/3256fa9a49f3464723836c03d8103d9f/bluez_logs_sink_26_02_2024.txt)
[bluez_logs_src_26_02_2024.txt](/uploads/f46333c0696d09a5af56cc59c15b4434/bluez_logs_src_26_02_2024.txt)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3861Popping/crackling/skipping audio while recording multiple virtual sources / s...2024-03-01T09:51:56ZA1R M4XPopping/crackling/skipping audio while recording multiple virtual sources / sinks [UMC404HD]- PipeWire version (`pipewire --version`): 1.0.3 (Compiled & linked with 1.0.3)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): CachyOS (Arch)
- Desktop Environment: KDE Plasma 5.27.10 on X11
- Kernel vers...- PipeWire version (`pipewire --version`): 1.0.3 (Compiled & linked with 1.0.3)
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): CachyOS (Arch)
- Desktop Environment: KDE Plasma 5.27.10 on X11
- Kernel version (`uname -r`): 6.7.5-2-cachyos (reproducible on 6.8.rc5-1)
- OBS Flatpak / OBS package from Arch / OBS git
- Sound device: UMC404HD
## Description of Problem:
Sound popping/crackling/skipping while recording multiples sources in OBS. One source works correctly (no sound issue) but all the others are stuttering / crackling / skipping.
If disabling pro audio & virtual devices, moving to the "direct UMC404HD profile" => sound get recorded properly in OBS (but I can´t differentiate the sources).
## How Reproducible:
100%. One of my buddy with the same audio device reproduced the issue.
### Steps to Reproduce:
1. Created Virtual sinks / sources for my UMC404HD by following this wiki https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#virtual-sinks (my acutal config in the dump might differ a little bit, tried to debug on my own for 1 week before posting here)
2. Launch OBS and add each source separately
3. Record
### Actual Results:
Unusable sound from 3/4 of sources from my UMC404HD sound device.
### Expected Results:
All virtual sinks / sources should be usable.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:[pw-dump.log](/uploads/e8d70728a25467008367486435041c0d/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3867Corrupted sound when switching output, Rpi 4B, debian sid2024-03-01T05:04:30ZMatt FellenzCorrupted sound when switching output, Rpi 4B, debian sid<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 1.0.3-1
- 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`): 1.0.3-1
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Debian sid
- Desktop Environment: N/A
- Kernel version (`uname -r`): Not sure, can add if necessary
## Description of Problem:
When playing audio and switching the output between two USB audio devices, the audio switches output but is corrupted for a couple seconds before fixing itself. Example:
Playing correctly on Output A.
Switch to B, immediately playing corrupted on B.
After a few seconds, playing correctly on B.
Switch to A, immediately corrupted on A.
Switch to B, still playing on A, even more corrupted.
After a few seconds, switch to B and play correctly immediately upon switching.
## How Reproducible:
100%
### Steps to Reproduce:
1. Plug in two USB audio devices to the RPi 4B.
2. Use pw-play to play a simple sine wave track or similar on one of the USB devices.
3. Use pw-metadata to set target.object and make Wireplumber switch the output to the other USB device.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3202[pipewire-jack] Hydrogen transport issues: As slave outputs no sound, as mast...2024-02-29T17:16:32ZJeppe Zapp[pipewire-jack] Hydrogen transport issues: As slave outputs no sound, as master sends corrupted data<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version: 0.3.70
- Distribution: Arch Linux
- Desktop Environment: GNOME
- Kernel version: 6.2.13-zen
## Description...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version: 0.3.70
- Distribution: Arch Linux
- Desktop Environment: GNOME
- Kernel version: 6.2.13-zen
## Description of Problem:
**NOTE:** The problems below do not occur with a plain JACK server.
When running Hydrogen as transport slave, the output audio is gone.
When running Hydrogen as transport master, the JACK position struct has unusable values:
- [ ] The `bar` is just a constant 1, switching to 0 for a single tick
- [ ] The `beat` has a similar issue, it's just -2 most of the time, occasionally flipping to 1
- [ ] The `tick` is always negative or 0
- [ ] The `bar_start_tick` is sometimes < 0
These are the values picked up by a simple Python JACK client:
```
{'usecs': 49088424042, 'frame_rate': 48000, 'frame': 16126976, 'bar': 1, 'beat': -2, 'tick': -30, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088445377, 'frame_rate': 48000, 'frame': 16128000, 'bar': 0, 'beat': 1, 'tick': 0, 'bar_start_tick': -7680.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088466712, 'frame_rate': 48000, 'frame': 16129024, 'bar': 1, 'beat': -2, 'tick': -1900, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088488047, 'frame_rate': 48000, 'frame': 16130048, 'bar': 1, 'beat': -2, 'tick': -1879, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088509381, 'frame_rate': 48000, 'frame': 16131072, 'bar': 1, 'beat': -2, 'tick': -1860, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088530717, 'frame_rate': 48000, 'frame': 16132096, 'bar': 1, 'beat': -2, 'tick': -1840, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088552051, 'frame_rate': 48000, 'frame': 16133120, 'bar': 1, 'beat': -2, 'tick': -1819, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
{'usecs': 49088573386, 'frame_rate': 48000, 'frame': 16134144, 'bar': 1, 'beat': -2, 'tick': -1800, 'bar_start_tick': 0.0, 'beats_per_bar': 4.0, 'beat_type': 4.0, 'ticks_per_beat': 1920.0, 'beats_per_minute': 120.0}
```
These are the values actually sent by Hydrogen:
```
[Hydrogen] [JACK transport] frame: 4607488, frame_rate: 48000, valid: 0x10, bar: 48, beat: 1, tick: 190, bar_start_tick: 9024, beats_per_bar: 4, beat_type: 4, ticks_per_beat: 192, beats_per_minute: 120, frame_time: 1.02509e-312, next_time: 4.63642e-310
[Hydrogen] [JACK transport] frame: 4607744, frame_rate: 48000, valid: 0x10, bar: 48, beat: 1, tick: 191, bar_start_tick: 9024, beats_per_bar: 4, beat_type: 4, ticks_per_beat: 192, beats_per_minute: 120, frame_time: 1.02509e-312, next_time: 4.63642e-310
[Hydrogen] [JACK transport] frame: 4608000, frame_rate: 48000, valid: 0x10, bar: 49, beat: 1, tick: 0, bar_start_tick: 9216, beats_per_bar: 4, beat_type: 4, ticks_per_beat: 192, beats_per_minute: 120, frame_time: 1.02509e-312, next_time: 4.63642e-310
[Hydrogen] [JACK transport] frame: 4608256, frame_rate: 48000, valid: 0x10, bar: 49, beat: 1, tick: 0, bar_start_tick: 9216, beats_per_bar: 4, beat_type: 4, ticks_per_beat: 192, beats_per_minute: 120, frame_time: 1.02509e-312, next_time: 4.63642e-310
```
## How Reproducible:
Very.
### Steps to Reproduce:
1. Run Hydrogen through `pipewire` jack
2. Start the transport
3. View the JACK position struct
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/455dfbe0a2c15b05aae1a0b6709acba5/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3656JACK transport is lost/not migrated when moving between driver nodes.2024-02-29T17:14:01ZDaniel LundqvistJACK transport is lost/not migrated when moving between driver nodes.As talked about in #3562, transport is per node and moving applications between nodes the transport is lost/not migrated. This is a problem when there's a mix of MIDI-only JACK applications and JACK applications with audio as well. Since...As talked about in #3562, transport is per node and moving applications between nodes the transport is lost/not migrated. This is a problem when there's a mix of MIDI-only JACK applications and JACK applications with audio as well. Since bafa890aefbadb0535047fa1b4ab3846acc7cef1 JACK applications are scheduled togeher, and if starting/stopping JACK application with audio ports the MIDI-only JACK applications may be moved to/from Midi-Bridge node.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3850MIDI clock/sync issues2024-02-29T17:12:45ZMarcin KoziołMIDI clock/sync issuesHere's my test setup:
- Behringer pro-800
- Roland T-8
both connected via USB to the computer
- 6.2.0-1018-lowlatency, Ubuntu 23.04 + Ubuntu studio repos
- pipewire from master
I'm trying to get synchronized sequence playback using jack...Here's my test setup:
- Behringer pro-800
- Roland T-8
both connected via USB to the computer
- 6.2.0-1018-lowlatency, Ubuntu 23.04 + Ubuntu studio repos
- pipewire from master
I'm trying to get synchronized sequence playback using jack_midi_clock and jack/pipewire transport
Patchbay:
![Zrzut_ekranu_z_2024-02-15_09-27-58](/uploads/5a6d9ad289b0242b859e4774c67012d3/Zrzut_ekranu_z_2024-02-15_09-27-58.png)
And the result (after few transport restarts, sequencers are playing off-beat)
![clock](/uploads/c2766005f378b08f8ed998e5e28a0a35/clock.mp3)
Please indicate what I am doing wrong or what I could do better, or what else should I provide?
[pipewire.conf](/uploads/b5aa55e81a96e0599cfd9b9b994ec26d/pipewire.conf)
[jack.conf](/uploads/116a2e8c7aeff35ac6f94fd81970d10e/jack.conf)
[pipewire-pulse.conf](/uploads/26e29d08e956a0c792e52dff64e41e46/pipewire-pulse.conf)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3882ubuntu22.04 wayland use xdg-desktop-por connect to PipeWire fail2024-02-29T03:36:20Zjiangjiang huubuntu22.04 wayland use xdg-desktop-por connect to PipeWire fail<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
- De...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
- Desktop Environment:
- Kernel version (`uname -r`):
```
pipewire --version
pipewire
Compiled with libpipewire 0.3.48
Linked with libpipewire 0.3.48
```
```
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"
```
Desktop Environment:Wayland
```
uname -r
5.15.78
```
## Description of Problem:
xdg-desktop-por connect to PipeWire fail
log:
```
systemctl --user status xdg-desktop-portal
● xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: active (running) since Thu 2024-02-29 10:35:42 CST; 13min ago
Main PID: 2574 (xdg-desktop-por)
Tasks: 5 (limit: 7736)
Memory: 3.0M
CPU: 285ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/xdg-desktop-portal.service
└─2574 /usr/libexec/xdg-desktop-portal
Feb 29 10:35:30 amlbian systemd[1473]: Starting Portal service...
Feb 29 10:35:42 amlbian xdg-desktop-por[2574]: PipeWire roundtrip timed out waiting for events
Feb 29 10:35:42 amlbian xdg-desktop-por[2574]: Failed connect to PipeWire: No node factory discovered
Feb 29 10:35:42 amlbian systemd[1473]: Started Portal service.
```
```
systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2024-02-29 10:48:14 CST; 10min ago
TriggeredBy: ● pipewire.socket
Main PID: 3952 (pipewire)
Tasks: 2 (limit: 7736)
Memory: 2.1M
CPU: 10min 11.988s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─3952 /usr/bin/pipewire
Feb 29 10:48:14 amlbian systemd[1473]: Started PipeWire Multimedia Service.
```
Manually restarting the pipewire service and xdg-desktop-portal service doesn't work also
## How Reproducible:
### Steps to Reproduce:
1.apt install pipewire xdg-desktop-portal xdg-desktop-portal-wlr
2.reboot
3.see log
### Actual Results:
xdg-desktop-portal can not work right
### Expected Results:
xdg-desktop-portal can work right , and i can use chromium screenshare function
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: