playmodes

Hi all! I'm trying to find a behavior where recalling a preset is not creating a burst of every operation result in a patch, but just the final (and good) result when every variable has been updated.

I'm working on a midi pitch class set generation patch, which sends MIDI data realtime to some synthesizer. Sending this bursts to the synthesizer is kind of unefficient, but i'm not finding an easy solution...

I'm attaching a simple demonstration of the problem. Just check the max console after recalling the presets and you will easily see what i'm talking about...

Obviously, i could have the final result entering the right inlet of an [i] object, and triggering the result with a bang; but i need to keep every single number-box updating the final result when used with the mouse, but restraining the output to a single value -and not a burst of values- when recalling the preset. 

print

preset

number

Hi all! I'm trying to find a behavior where recalling a preset is not creating a burst of every operation result in a patch, but just the final (and good) result when every variable has been updated.  

I'm working on a midi pitch class set generation patch, which sends MIDI data realtime to some synthesizer. Sending this bursts to the synthesizer is kind of unefficient, but i'm not finding an easy solution...  

I'm attaching a simple demonstration of the problem. Just check the max console after recalling the presets and you will easily see what i'm talking about... 

Obviously, i could have the final result entering the right inlet of an [i] object, and triggering the result with a bang; but i need to keep every single number-box updating the final result when used with the mouse, but restraining the output to a single value -and not a burst of values- when recalling the preset. 
Maybe i'm asking for too much?  

Hi all! I'm trying to find a behavior where recalling a preset is not creating a burst of every operation result in a patch, but just the fi

presets-and-multiple-operations-triggering

your first mistake is not to EXCLUDE from preset the last number

without the complete picture it is difficult to suggest

what is best way, but if one takes exactly that what you posted,

you need expr that allways calculates all 3 inputs in one go and outputs only 1 final result.

the idea with banging the final result is correct, needs a delay to skip

your first mistake is not to EXCLUDE from preset the last number
which is only the result of the others.
without the complete picture it is difficult to suggest
what is best way, but if one takes exactly that what you posted,
you need expr that allways calculates all 3 inputs in one go and outputs only 1 final result.
the idea with banging the final result is correct, needs a delay to skip
the pre-final calculations.


Presets and multiple operations triggering