brendan mccloskey

I am testing an interactive system which triggers midi notes from slider values. It uses logic conditions as follows:

if any slider is raised from 0 to >0 while any/all previous sliders are at 0, then the notes are discrete, ie the leap to the 2nd note is instantaneous

if any slider is raised from 0 to >0 while any/all previous sliders are NOT at 0 (ie, >0) then a glissando to the second note occurs (via a line ramp).

Furthermore, the time of the line ramp is dictated by the 'peak' value of the second slider, such that large values cause a slow glissando, small values a quick one.

This all works fine, relying mainly on [togedge] and [==].

I think I have my message ordering correct, but the curious behaviour of [noteout] to a line ramp has me stumped. Below is a simplification of my system, if you hook up a [print] to the output of [line] you will see rapid note repetitions during a glissando; while the logic/message ordering is slightly imperfect, it appears that this note repetition will occur even with perfect logic etc. Anyone with expertise in [line], [trigger] and/or [noteout] able to assist?

ps it's for an international conference on Friday. Eeeeek

Hi
I am testing an interactive system which triggers midi notes from slider values. It uses logic conditions as follows:

Brendan EDIT re-attached correct patcher


sending-line-ramp-to-noteout-causes-ghostrepeated-notes

The above is example is fairly self-explanatory, but below I have simplified the logic challenge even further:

Quick hack (as usual..) in response to your second example. Some thought may yield a more elegant solution. And while I'm at it, Everytime I do a logic 'thing', I always wonder why there doesn't seem to be a boolean inverter (ie NOT) in Max's object complement...

Quick hack (as usual..) in response to your second example. Some thought may yield a more elegant solution. And while I'm at it, Everytime I do a logic 'thing', I  always wonder why there doesn't seem to be a boolean inverter (ie NOT) in Max's object complement...


Thanks for the hacks guys; going back to square 1, I've got a semi-solution using good ol' [if]:

if ($i1>0 && $i2>0) && ($i1==$i2) then bang, using [todgedge]-[toggle] on each input; just struggling now with how to get only one bang if the condition is false, ie each slider goes from 0 to >0 back to 0 in turn

[togedge] - how do I love thee? - let me count the ways!

But in the end, is it any more elegant-er-ful than the above solutions??

ps any ideas on the r-r-r-r-repeating midinotes?

You'd think that, given that I wrote the togedge object in the dim dark past, I would be more loyal to it.

there are almost no interactive patches of mine that do not rely, at their core, on [togedge] - she's a beauty, so thanks. Some algorithms using [maximum], [peak] or [change] require a little hacking for specific needs, but [togedge] does exactly what it says on the tin.

ps repeating midi notes solved in this too

Hi Chris, gotta say
there are almost no interactive patches of mine that do not rely, at their core, on [togedge] - she's a beauty, so thanks. Some algorithms using [maximum], [peak] or [change] require a little hacking for specific needs, but [togedge] does exactly what it says on the tin.

ps repeating midi notes solved in this too


sending line ramp to noteout causes ghost/repeated notes