GNOME Bugzilla – Bug 796109
alsasrc: Don't use driver timestamp if it's zero
Last modified: 2018-11-03 12:07:19 UTC
Some alsa sources (like dsnoop) have always zero in their timecode field. In that case, use gstreamer's own timestamping.
Created attachment 372026 [details] [review] alsasrc: Don't use driver timestamp if it's zero
Comment on attachment 372026 [details] [review] alsasrc: Don't use driver timestamp if it's zero You probably want to directly set driver_timestamps=FALSE in that case. If it reports once 0, it probably is not reliable ever
There is bunch of timestamp related information you can retrieve in ALSA API, which I'm not very familiar with. Have you made sure it's impossible to just ask the driver instead of just implementing this hack ?
I'm also not familiar with them. There is a bunch of different timestamps, but documentation is not at all clear what's the difference between them. At least for get_htstamp() used by alsasrc, I didn't figure out how to check if they are valid. There is a snd_pcm_status_get_audio_htstamp_report(), but I have now idea how many thinks will break if I use get_audio_htstamp() instead of get_htstamp().
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/453.