Skip to content

alsasrc: Don't use driver timestamp if it's zero

Some alsa interfaces don't provide timestamps and thus always set the timestamp to zero.


This is kind of related to !220 (merged) . But it seems like independent of that MR it would also be useful to check for 0 timestamps here, at least it does not hurt and a 0 timestamp is most certainly completely wrong.

Any opinions?

Merge request reports

Loading