27 Jun
2010
27 Jun
'10
2:46 p.m.
On Sat, 2010-06-26 at 18:04 -0400, David Dillow wrote:
When using a timing voice to clock out periods during capture, the driver would slowly loose synchronization and never catch up, eventually reaching a point where it no longer generated interrupts.
This has survived overnight testing at 44.1 kHz/16 bit/mono without issue.
Only to die at 12 hours and ~15 minutes. It did not trip any of the instrumentation I was using to verify operation, so this may be a different problem. I'm looking into it.
Dave