14 Jun
2012
14 Jun
'12
10:15 a.m.
Pierre-Louis Bossart wrote:
As long as you have 2 periods or events per 179s, the wrap-around can be detected without any issues. It's explicitely handled in the code.
AFAICS there is no code that enforces the 179s restriction.
And why are you using a separate wallclock timer instead of the sample count? Does the higher resolution result in a noticeable improvement?
How should userspace detect streams whose sample clock is not synchronous with this wall clock, such as digital inputs?
Regards, Clemens