11 Dec
2016
11 Dec
'16
8:03 a.m.
On 12/08/2016 01:51 AM, Thomas Howe wrote:
I tried running in non-realtime, and it still happens.
I'll try to get
the debug symbols and run "perf record" in a few days.
At 192kHz that makes sense, but it happens for the same amount of time
at 96kHz which is confusing, but I reckon it's safe to say this is a
frame counter-related bug :)
Is there a way to reduce the size of the frame counter from 32 bits to
something like 20, so I wouldn't have to leave the process running over
6 hours each time I do a test?
You could try initializing it to something close to the max value :)
Maybe even with attaching gdb to it if your executable has debug symbols
(so you don't need to build it yourself).
Flo
--
https://fps.io