This works a little better still. Nobody suggested a name, so i’ll just be calling it TrackStates. The poly~ patch has changed to state_setter.maxpat
Thankfully for the most part, the aberrant behavior happens only if the device order is swapped and presets overwritten for the new device configuration, or if the device is opened for editing. my advice is to finalize your selection of effects for the track before adding the TrackStates to your chain.
It will most likely boomerang if you change devices once it’s all first set. The jittery recall still happens a small percentage of the time even if you leave everything in place, and I can’t figure out what the issue is with the faulty interpolation. I have a feeling that it’s an error on my end, but the pattrstorage is not outputting recall messages that are out of order or going backwards, and the initial (go from) preset is not being stored once the recall gets going. . . so . . . ?
Nov 2, 2010 at 4:49pm #187015