19 Jul
2023
19 Jul
'23
9:27 a.m.
On Wed, 19 Jul 2023 09:10:12 +0200, Carl Klemm wrote:
Hi,
see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3352 htimestamp returns nonesensical values when recording is active on a EMU20k device
The driver doesn't provide any own implementation of PCM tstamp, hence it must be the standard values. That said, the incorrect values are rather the "avail", that is the PCM position, not the timestamp itself, I suppose.
Is it only about recording, i.e. playback doesn't show any wrong values?
In anyway, try to enable the tracing for snd_pcm, get the position and the system timestamp during recording, and verify whether the reported values are reasonable or not.
Takashi