Strange trigger_htstamp after snd_pcm_drop
alsa-project/alsa-lib issue #387 was reopened from z-s-e:
I have conceptually the following situation (actual code can be found [here](https://gitlab.com/z-s-e/alpe/-/blob/main/src/alpe_alsa.cpp?ref_type=heads#L...)): ``` // sound is currently playing snd_pcm_status(pcm, pcm_status); snd_pcm_status_get_htstamp(pcm_status, &ts1); snd_pcm_drop(pcm); snd_pcm_status(pcm, pcm_status); snd_pcm_status_get_trigger_htstamp(status, &ts2); ``` On my hardware I get a `ts2` timestamp that is earlier than `ts1`. From my understanding that should be impossible, as `ts2` should contain the timestamp of when the drop happened, which should obviously be after `ts1`. Is that a bug or do I misunderstand the meaning of those timestamps?
Issue URL : https://github.com/alsa-project/alsa-lib/issues/387 Repository URL: https://github.com/alsa-project/alsa-lib
participants (1)
-
GitHub issues - reopened