funkychorlton

I have a very complex patch that is occasionally crapping out and crashing for reasons I can't understand and the max window is not telling me - no significant errors reported. I have a feeling that it might be choking on the amount of external midi I am sending. It is receiving about 28 midi CCs and 8 of these are 14 bit pitchbend controllers on different midi channels. I will use the speedlimit object on all these inputs - but can anyone suggest appropriate settings for filtering these 14 bit numbers? - I am keen to avoid audible stepping. Exact settings will be suck and see of course but what kind of ranges should I be looking at to begin experimenting?

suggest-speedlimit-settings

The baud rate of midi is relatively low. Typically you will be receiving a value about every 1 ms (or two thirds, if sender uses running status). With double precision controllers, this value goes up.

Max would crash if the amount processor time needed to do all calculations on every controller value received exceeds 1 ms. Depending on processor speed, this represents quite a bit of calculations.

First of all, what you might try to do is to use a single midiin object with midiparse, rather then multiple ctlins. Performance-wise, I believe the first method is better.

Second, the calculations performed on each of the controllers could be optimized, or better yet, stored in look-up tables (eg. table or multislider). Looking up values is almost always faster then calculating.

If this doesn't help you might give speedlim a try. With 1 ms per controller value and 28 controllers, the speedlim value should be higher then 28 ms.

The baud rate of midi is relatively low. Typically you will be receiving a value about every 1 ms (or two thirds, if sender uses running status). With double precision controllers, this value goes up.
Max would crash if the amount processor time needed to do all calculations on every controller value received exceeds 1 ms. Depending on processor speed, this represents quite a bit of calculations.
First of all, what you might try to do is to use a single midiin object with midiparse, rather then multiple ctlins. Performance-wise, I believe the first method is better.
Second, the calculations performed on each of the controllers could be optimized, or better yet, stored in look-up tables (eg. table or multislider). Looking up values is almost always faster then calculating.
If this doesn't help you might give speedlim a try. With 1 ms per controller value and 28 controllers, the speedlim value should be higher then 28 ms.


suggest speedlimit settings?