Move reference to timestamp validity bug to more suitable location

This commit is contained in:
mitchmindtree 2020-04-28 17:43:40 +02:00
parent 45977bf837
commit 163f0cc190
1 changed files with 1 additions and 2 deletions

View File

@ -204,6 +204,7 @@ impl Device {
}; };
// Check to see if we can retrieve valid timestamps from the device. // Check to see if we can retrieve valid timestamps from the device.
// Related: https://bugs.freedesktop.org/show_bug.cgi?id=88503
let ts = handle.status()?.get_htstamp(); let ts = handle.status()?.get_htstamp();
let creation_instant = match (ts.tv_sec, ts.tv_nsec) { let creation_instant = match (ts.tv_sec, ts.tv_nsec) {
(0, 0) => Some(std::time::Instant::now()), (0, 0) => Some(std::time::Instant::now()),
@ -741,8 +742,6 @@ fn stream_timestamp(stream: &StreamInner) -> Result<crate::StreamInstant, Backen
None => { None => {
let status = stream.channel.status()?; let status = stream.channel.status()?;
let trigger_ts = status.get_trigger_htstamp(); let trigger_ts = status.get_trigger_htstamp();
// TODO: This is returning `0` on ALSA where default device forwards to pulse.
// Possibly related: https://bugs.freedesktop.org/show_bug.cgi?id=88503
let ts = status.get_htstamp(); let ts = status.get_htstamp();
let nanos = timespec_diff_nanos(ts, trigger_ts) let nanos = timespec_diff_nanos(ts, trigger_ts)
.try_into() .try_into()