Forums > MaxMSP

What is the exact effect of adjusting the Scheduler Slop setting?

February 13, 2008 | 4:18 pm

Hi Guru’s,

There’s a bug in my patch. When a lot of midi events are entering my patch, it looks like occasionally an event simply disappears.

Just to be sure I understood everything correctly: if the Scheduler Slop setting in the Performance Options is set to 25 ms, every event that is 25 ms behind its intended execution time will be deleted. Is that correct?

I thoroughly read jkc’s article Event Priority in Max (Scheduler vs. Queue) (http://www.cycling74.com/story/2005/5/2/133649/9742) but I can’t find the answer to this question there.

If there’s anyone who can confirm (or contradict) my understanding of the scheduler system, please let me know!

Thanks,
Mattijs


February 13, 2008 | 7:17 pm

> Just to be sure I understood everything correctly: if the Scheduler Slop setting in the Performance Options is set to 25 ms, every event that is 25 ms behind its intended execution time will be deleted. Is that correct?
>

That’s it exactly. Events inside the slop (< = 25 ms late) will still be executed. Events outside the slop time will (>25ms late) will be dropped. You can also control the number of things (poll throttle) Max tries to accomplish each tick and the frequency (event interval) of the ticks.
If
If late events are better than no events, for you, then you should set the slop bigger. This will work better if your events come in bursts. If you are constantly backlogging the scheduler, then you’ll just fill up the slop time and keep dropping events.

mz


February 13, 2008 | 8:52 pm

Thanks a lot mzed, that was exactly what I needed to know.

Mattijs

Quote: mzed wrote on Wed, 13 February 2008 20:17
—————————————————-
>
> > Just to be sure I understood everything correctly: if the Scheduler Slop setting in the Performance Options is set to 25 ms, every event that is 25 ms behind its intended execution time will be deleted. Is that correct?
> >
>
> That’s it exactly. Events inside the slop (< = 25 ms late) will still be executed. Events outside the slop time will (>25ms late) will be dropped. You can also control the number of things (poll throttle) Max tries to accomplish each tick and the frequency (event interval) of the ticks.
> If
> If late events are better than no events, for you, then you should set the slop bigger. This will work better if your events come in bursts. If you are constantly backlogging the scheduler, then you’ll just fill up the slop time and keep dropping events.
>
> mz
>
>
—————————————————-


Viewing 3 posts - 1 through 3 (of 3 total)