Hello, I am working on a number of patches but my main issue seems to be to do with timing problems.

In some cases it is a problem because different modules that are supposed to run in a quantised fashion slowly start to go in and out of snyc. For these i would like to know if the is something in the way Max works where it rounds really detailed numbers up/down, (such as 7.8125 which in my patches keeps being converted to 7.8005 so when it repeats it begins to drift out of sync)

It sounds like I have either done something stupid in designing the patch but as far as I can tell the maths, connections, bpm settings, metro etc are all set up just fine so all i can think of is it 'might' be something to do with Max itself.

Secondly when reading a matrix with a metro and jit.peek object again (i have made the matrix audible) the sounds the matrix 'plays' begin to drift in/out of sync with each revolution (oscillation)

Perhaps there is a specific way to keep all timing objects ins snyc i don;t know about (everything is triggered with the same bang so sounds great for a second or so then drifting occurs...always

perhaps it is an update issue such as using numbers, floating point numbers, signals and non signals having boxes in the patch that update and therefore 'take' a millisecond out or something....

If anyone has an answer please let me know, if you wish me to post any patches also please let me know,

Hello,  I am working on a number of patches but my main issue seems to be to do with timing problems.  

In some cases it is a problem because different modules that are supposed to run in a quantised fashion slowly start to go in and out of snyc.  For these i would like to know if the is something in the way Max works where it rounds really detailed numbers up/down, (such as 7.8125 which in my patches keeps being converted to 7.8005 so when it repeats it begins to drift out of sync)  

a question about the max time format