hi Kas,i haven't checked that part of the code, but maybe the values are not initialized?
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 best, gabor
