Closed grinness closed 1 year ago
Hi,
to make sure that the information above were correct, I re-checked the latency of snd-dice via jack2 (Cadence), the latency is smaller than previously reported, but still almost 1 order of magnitude higher than FFADO(same settings-- buffer size 512 and 2 periods/buffers):
>jack_iodelay
new capture latency: [0, 0]
new playback latency: [0, 0]
Signal below threshold...
Signal below threshold...
Signal below threshold...
Signal below threshold...
new capture latency: [512, 512]
Signal below threshold...
Signal below threshold...
Signal below threshold...
Signal below threshold...
Signal below threshold...
new playback latency: [1024, 1024]
2634.732 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.732 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.731 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.731 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.732 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.732 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.731 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
2634.731 frames 54.890 ms total roundtrip latency
extra loopback latency: 1098 frames
use 549 for the backend arguments -I and -O Inv
Again, please let me know if this is not the right place to report the issue.
Thanks
Let me close the issue since it is not an issue of alsa-lib.
Hi,
I hope this is the right place to report this (please let me know if it is not) On a 5900x, 32 GB RAM, Archlinux (kernel 6.0.2), I have been investigating crazy high latency using a pipewire-jack, see:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2790
I ended up testing jack_iodelay with jack2, comparing snd-dice and FFADO
Running qjackctl jack2, ALSA backed (snd-dice) 48000Hz, 1024 samples, 2 periods:
Running qjackctl jack2, firewire backend (FFADO) 4800, 512 samples, 2 periods:
Note that qjackctl seems to not set the number of periods correctly with firewire backend, the above playback latency suggests 3 periods instead of 2. It seems that Cadence fixes the issue, but the extra loopback latency stays at 162 frames with FFADO:
Please note that the pipewire developer pointed out that:
"My problem is that the period size in the driver is set to 1024. For batch devices and a quantum of 256 this should be set to 128 to get decent latency. So, either the driver does not report itself as batch, or something else started the nodes with a higher quantum. I'm betting it's the batch thing."
I also reported this in the following: https://github.com/takaswie/snd-firewire-improve/issues/47
thanks