Liam

added in some fun stuff to the tracking gen control patch for my alesis ion but i'm having some problems. I'm using a preset object to save settings on the multislider that sets the tracking points on the synth. however, a problem arises when i change presets. when all the multislider points change at once it ends up overloading the midi bandwidth and only one or two point changes make it to the synth. is there any way to slow down the [iter] object below the multislider so that there is a set delay between each output? this would give the xNRPNout2 and the logic before it some time to get the preceding midi message out to the synth before being interrupted by the next incoming message. here's the patch:

hey again guys
added in some fun stuff to the tracking gen control patch for my alesis ion but i'm having some problems. I'm using a preset object to save settings on the multislider that sets the tracking points on the synth. however, a problem arises when i change presets. when all the multislider points change at once it ends up overloading the midi bandwidth and only one or two point changes make it to the synth. is there any way to slow down the [iter] object below the multislider so that there is a set delay between each output? this would give the xNRPNout2 and the logic before it some time to get the preceding midi message out to the synth before being interrupted by the next incoming message. here's the patch:


iter-speed-and-midi-bandwidth

With zl queue there might be a solution possible.

ah, there you go. i knew there had to be a [zl] mode that would do this for me. [zl] continues to amaze me as i learn more uses for it. thanks!

And if you want a "you kids stay off of my lawn!" brute force method, replace iter with this:

iter speed and MIDI bandwidth