3 Aug
2009
3 Aug
'09
6:55 a.m.
Christopher Arndt wrote:
I've tested this now and encountered a very strange bevahior of the event time set by the queue:
a) SeqEvent.time seems to be in milliseconds instead of seconds as would be expected by the ALSA documentation and looking at the source of pyalsa.alsaseq.
- Consecutive timestamp go up to ~1000,00 and then seem to wrap around
and start from zereo again.
Apparently, you are the first one who tried to use this. Fixed now: http://git.alsa-project.org/?p=alsa-python.git;a=commitdiff;h=9a7dea33dddeb2...
HTH Clemens