[pipewire-jack] Systematic delay in recording using REAPER of 0.07 to 0.08 seconds
- PipeWire version (
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
): ArchLinux - Desktop Environment: KDE Plasma 5.26.1
- Kernel version (
uname -r
): 6.0.2-arch1-1
Description of Problem:
In the past I used pipewire-jack to record professional audio using REAPER with no problem After a few months of inactivity I am trying to record again (using the same hardware setup as before) but I am getting systematic delay of about 0.07 to 0.08 seconds -- at 96bpm this is about 1/8 of a bar.
I use:
- pipewire-jack
- wireplumber
- latest REAPER for linux
- Focusrite Saffire 14 PRO (firewire), profile is ProAudio in KDE settings
- AMD 5900x 32 GB Ram
- Archlinux
The issue does not appear if I connect REAPER using ALSA (pipewire-alsa) -- same settings in REAPER except the audio driver To do so I need to swap wireplumber with pipewire-media-session due to: (https://archlinux.org/news/undone-replacement-of-pipewire-media-session-with-wireplumber/)
I installed package 'pulseaudio-alsa' as discussed in: (#1697 (closed)) but without any resolution of the issue
I disabled suspend as discussed in: (https://wiki.archlinux.org/title/PipeWire#Noticeable_audio_delay_or_audible_pop/crack_when_starting_playback) but without any resolution of the issue
Please note that I have the following settings in my .config folder:
`
cat .config/pipewire/jack.conf.d/10-reaper.conf
jack.rules = [
{
matches = [
{
client.name = "REAPER"
}
]
actions = {
update-props = {
node.latency = 256/48000
node.rate = 1/48000
node.quantum = 256/48000
node.lock-quantum = true
node.force-quantum = 256
}
}
}
]
`
How Reproducible:
The issue appears every time
Steps to Reproduce:
- Open Reaper
- connect to jack (pipewire-jack)
- record audio
Actual Results:
systematic delay of 0.07 to 0.08 of the recording
Expected Results:
no delay in recording
Additional Info (as attachments):
Note that the delay could be caused either/both by delay in playback or delay in recording
pw-dump > pw-dump.log
series of svg files captured with pw-profiler while recording audio