Hello there, i hope someone there can give me a hint about the scheduler accuracy in Max!

I am working on a project where I need to get precise coordinate data from a list. The idea is to represent the displacement of GL shape on the space following the path made by the sound. We are planning to use the Wave Field Synthesis System in Leiden, Netherlands, which has 192 speakers placed inside a room. Because we want a particularly good accuracy we were running some tests in order to be sure the data will have as little delay as possible.

The first problem I had was a terrible bad interpolation display between values when I reduced the metro to 1. I ran a test with the cpu clock and i discovered something: if i don't overdrive the scheduler when my metro has 1 millisecond interval, my values of bang go to 2.25 with a mean error between 0.69 to 0.75(sometimes even 0., which seems to be very high and not very accurate at all!. I tried the patch in a friend's computer and in one of my teacher's computer and it seems that their mean absolute error was not over the 0.4. One important issue is that both were running max/msp 5.0.5.

I am running max/msp 5.0.6 in a MCP 2.53 GHz + 4 GB Ram, two video cards NVIDIA(9400+9600 GT).

Any hint how I can improve my scheduler accuracy?

Hello there, i hope someone there can give me a hint about the scheduler accuracy in Max!
I am working on a project where I need to get precise coordinate data from a list. The idea is to represent the displacement of GL shape on the space following the path made by the sound. We are planning to use the Wave Field Synthesis System in Leiden, Netherlands, which has 192 speakers placed inside a room. Because we want a particularly good accuracy we were running some tests in order to be sure the data will have as little delay as possible.
The first problem I had was a terrible bad interpolation display between values when I reduced the metro to 1. I ran a test with the cpu clock and i discovered something: if i don't overdrive the scheduler when my metro has 1 millisecond interval, my values of bang go to 2.25 with a mean error between 0.69 to 0.75(sometimes even 0., which seems to  be very high and not very accurate at all!. I tried the patch in a friend's computer and in one of my teacher's computer and it seems that their mean absolute error was not over  the 0.4. One important issue is that both were running max/msp 5.0.5.
I am running max/msp 5.0.6 in a MCP 2.53 GHz + 4 GB Ram, two video cards NVIDIA(9400+9600 GT).
I attach here the test patch
Any hint how I can improve my scheduler accuracy?
Thank you very much for help!!

accuracy-problem

Scheduler use is much more complex than a control-rate which is how other audio environments handle something like this. The reason why Max allows for this kind of flexibility is to allow people to choose between dedicating CPU to different sets of tasks(either clock-specific, or UI-graphic-specific(you can still choose to be clock-specific and have great UI response if you design your UI wisely, otherwise it simply takes a faster CPU)). 

You are correct, putting the scheduler in overdrive increases accuracy. In addition, putting the scheduler "In audio interrupt" and choosing a signal vector size of 64 or below will give you even better accuracy(the smaller the signal vector the greater the frequency of scheduler event-polls when the scheduler is in audio-interrupt because "audio-interrupt" means that an event poll takes place once every vector of audio samples; much like having a control-rate synced to your audio-rate calculations).

My words, though, fall extremely short of explaining as well as the documentation for it which can be found in Max5. If you go to the "Help" menu, choose the main "Max Help" option from the menu, and on the page that follows, in a panel on the right of the page under the "MSP" section, click the link that says "Audio I/O".... it'll tell you much more.

if you'd prefer the internet version, it's here:

https://cycling74.com/docs/max5/tutorials/msp-tut/mspaudioio.html

Scheduler use is much more complex than a control-rate which is how other audio environments handle something like this. The reason why Max allows for this kind of flexibility is to allow people to choose between dedicating CPU to different sets of tasks(either clock-specific, or UI-graphic-specific(you can still choose to be clock-specific and have great UI response if you design your UI wisely, otherwise it simply takes a faster CPU)). 
You are correct, putting the scheduler in overdrive increases accuracy. In addition, putting the scheduler "In audio interrupt" and choosing a signal vector size of 64 or below will give you even better accuracy(the smaller the signal vector the greater the frequency of scheduler event-polls when the scheduler is in audio-interrupt because "audio-interrupt" means that an event poll takes place once every vector of audio samples; much like having a control-rate synced to your audio-rate calculations).
My words, though, fall extremely short of explaining as well as the documentation for it which can be found in Max5. If you go to the "Help" menu, choose the main "Max Help" option from the menu, and on the page that follows, in a panel on the right of the page under the "MSP" section, click the link that says "Audio I/O".... it'll tell you much more.
if you'd prefer the internet version, it's here:https://cycling74.com/docs/max5/tutorials/msp-tut/mspaudioio.html

Hello RabidRaja. Thank you for the fast answer!

My main fear is that the schedule issue will affect the rendering of the GL objects and the sync with the spatial information is coming from the audio. I will give it a try and see how it works with reducing the signal vector.

Hello RabidRaja. Thank you for the fast answer!
My main fear is that the schedule issue will affect the rendering of the GL objects and the sync with the spatial information is coming from the audio. I will give it a try and see how it works with reducing the signal vector.
I will take a look and see how it works!

accuracy problem?