On Sat, May 19, 2012 at 08:51:42PM +0200, gabor papp wrote: > hi Kas, > > i haven't checked that part of the code, but maybe the values are > not initialized?
I thought that might be it, but when a instance of the midi listener is created the values of bar, beat and pulse are set to 0. It used to work too. I only realised it is broken when my midi sync for Fluxa started acting very weird last night. So far I've been able to trace it to midi-position. I could do something like have (midiin-open n) also reset the midi position and pray that helps but I'd rather figure out what causes this. > > >hard to blame that one. Considering how unreasonably large and how > >apparently random these numbers are I'm inclined to suspect some sort > >of memory issue, where would I start with debugging that? > maybe valgrind would help: > valgrind --leak-check=full --vex-iropt-precise-memory-exns=yes fluxus > It does that sort of check too? Nice, I only once used it to look for leaks. Thanks. Kas.
