[BUG REPORT] sound: pci: ctxfi: htimestamp dose not work on EMU20k during recording
Hi,
see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3352 htimestamp returns nonesensical values when recording is active on a EMU20k device
lspci: 03:00.0 Audio device: Creative Labs EMU20k2 [Sound Blaster X-Fi Titanium Series] (rev 03) Subsystem: Creative Labs EMU20k2 [Sound Blaster X-Fi Titanium Series] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at d1200000 (64-bit, non-prefetchable) [size=64K] Memory at d1000000 (64-bit, non-prefetchable) [size=2M] Memory at d0000000 (64-bit, non-prefetchable) [size=16M] Capabilities: <access denied> Kernel driver in use: snd_ctxfi Kernel modules: snd_ctxfi
With regards, Carl Klemm
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
participants (2)
-
Carl Klemm -
Takashi Iwai