I am experiencing some problems with the counters inside max. Herewith I attach a simple example. Hopefully most of the people trying it out won't notice nothing in particular, however, when i run it on my computer the first int box generates the values in a rather unpredictable fashion. An example can be something like: 10 20 30 43 50 65. When using float boxes the problem even gets worse. I already experienced something similar before migrating from Leopard to Snow Leopard so I assume that this might be a system-independent issue. Any suggestions how to put order within the max scheduler?, is it a common place to have problems with the scheduling inside max?

Hello!
I am experiencing some problems with the counters inside max. Herewith I attach a simple example. Hopefully most of the people trying it out won't notice nothing in particular, however, when i run it on my computer the first int box generates the values in a rather unpredictable fashion. An example can be something like: 10 20 30 43 50 65. When using float boxes the problem even gets worse. I already experienced something similar before migrating from Leopard to Snow Leopard so I assume that this might be a system-independent issue. Any suggestions how to put order within the max scheduler?, is it a common place to have problems with the scheduling inside max?
Thank you!
Emmanuel


suggestions-for-schedule-optimization

Do you know the difference between a metro and a qmetro object? That might be one possible source of your problem.

If you want tighter counting, run stuff at audio rates.

Do you know the difference between a metro and a qmetro object? That might be one possible source of your problem. 

If you want tighter counting, run stuff at audio rates.


suggestions for schedule optimization