Im trying to implement this block diagram where we receive a co-ord, check the condition. If true the co-ord is sent forward and stored as current co-ord. If false the co-ord is checked against current co-ord...

The thing is Im not sure how to store the co-ordinate values so as you would in a general-purpose program perhaps? Has anyone designed a keyboard application and had to do this?

Please find attached a flow chart and the pure data patch to implement to flow chart design.

many thanks

Hi, this sends out the x y coordinates only when their state is 1. I suppose you could also do it with [poly].

store.variable.pd

So, when the button is pressed (state == 1) you need the coordinates to be sent out and stored, but what do you need to happen when the state is 0 (= button release?) Do you just need that the coordinates are not sent through?

Ok I see, then I think it depends on whether each button (aka each set of coordinates) is assigned to a fixed note or not, because in that case rather than using this sort of logic you could use each unique pair of coordinates to trigger a specific note, and use the state value to trigger the velocity (0 = 0, 1 = 127, for example).

for example in this screen shots we take values that meet a certain condition. if i press say 3 15 1 hold it ..press 5 15 1 thats fine 5 15 1 plays. But when i release 5 15 1 where i was holding 3 15 1 is lost.

what also happens is if i press any co-ord value that meet the conditions here but then press say 6 12 1 whatever job 5 15 1 was doing stopped?

With Midi it would be very simple, let each button send a note-on when pressed and a note-off when released and you are finished.

If you want the sound processing in pd i guess you would need to build a polyphonic synth and send the on and offs to one of the synths. I haven't used the audio stuff in pd yet so i could be wrong on that.

I just realised I didnt link the other flow chart more specifically applied to the patch

If I understand your presses....... and (the result).....
What you posted looks like.....
press and hold 3 15 1 (note) ....... press 5 (new note)........ release 5 (nothing)

Is that true?
David.

if all button presses are going through the same logic gate, there is no way of keeping track of which coordinate is associated with which state, and as soon as a "state = 0" is received, 0 is sent to [s note1] regardless.

I think the best way is to somehow pair the state (on/off) with whatever value you want to pass through (which in the last picture you attached is only the x value?). Then you can send the list to the sound generating stuff and scale them, or convert them to midi and send them outside pd.

any co ordinate such as 12 14 1 makes the condition output false. If a current true value is being used and a false value occurs it should't be stopping a currently active true value ...

get co ords

r x is sent to store in three float objects
and the condition equal to - 1?

co word are test with equal to 3

what do we test for next? I guess if equal to three is true or false.

but before we can send the result of == 3 forward….we do something with values from r x, what happens are the -1 condition?
r x (condition) is multiplied with r y (condition) ?

then we either get 0 or 1.

we can then send the result of all the co-ord added together forward?
we then bang the r x values stored in two of the floats and a zero to spigot 1?

but if spigot 1 is zero we bang a -1? to an earlier condition….

I wanted to send this in the mean time while i look at this again but I think I’m describing it in a convoluted manner?

logic.zip
Extended and Vanilla.

You can save the patch with the grid drawn...... but then must be careful not to create the grid again..........
The drawing can be automated with a [loadbang] of course.

It is probably possible to attach an age to the xytog abstractions as well, so that "updates" are sent in the correct reverse order when there are many....... as all current xyz values are stored!
David.

The first button who meets the condition sets the toggle to 1 and closes the spigot. The current number is stored in the [==]. Only this button can open the spigot again: If and only if the incoming number equals the stored one and the second condition is true (1 x 1 = 1), the spigot is opened. The [change] protects against redundancy.

I dont think i fully understand where the values are stored exactly ? is it that a toggle pushed down maintains the co ord position and somehow we can recall this back?

@ingox I combined what you sent to manage and allocate a row of buttons still.

What happens with the two combined is if i hold press and hold 3 15 1 then push 6 15 1, 6 15 1 wont make it though the conditions until i let go of 3 15 1.

@whale-av if I use the logic patch alone 3 15 1 can be pressed and held, then 6 15 1 can be push and the note will jump to 6 15 1, If i then release 3 15 1, 6 15 1 is then triggered again.

@ingox when your patch is isolated and if i press and hold ie 3 15 1 every other button is ignored which means i can trigger parameters on the grid without it interfering with the values within the conditional range..... I wondered if its possible with this to push and hold 3 15 1, and update a list when another note is pushed within the conditional range and revert back to what is previously held like an analogue monophonic synth synth.....

i guess xytog is one solution to this ...?

also I'd just like to add that this process is much more enjoyable and less daunting with the your help so I'd like to say i really a appreciate the support in the responses
I'm getting here

(Still don't know exactly why you would want them to be interdependent... )

____@whale-av if I use the logic patch alone 3 15 1 can be pressed and held, then 6 15 1 can be push and the note will jump to 6 15 1, If i then release 3 15 1, 6 15 1 is then triggered again.

That does not happen in my model...... but then it has no real data.
It is likely that holding an xy button sends a continuous stream of messages....... but?

Maybe time to post your input messages for those key presses. Maybe the problems originate in the "sent" OSC message order?
Could you put a print from your OSC receive object, and do those key presses and then Screenshot the terminal so that we can see the exact input?

I will think about implementing aging for the [xytog] abstractions. Yes, they hold the last z value (0/1) for every xy coordinate and then send again when they receive a bang from [s update]..... but only if their value is 1 (and the bang is only sent when a button is released...... z=0). However, at the moment they send their output in the order that they execute the command, which is the order of their creation. Hence an aging value is necessary for stepping backwards.
David.

these are the print messages from the serialosc object:

I really wanted to try the monophonic keys.pd but the array objects arn’t recognised ? I tried including a table so see if it would be recognised to store the values in there?

I want to link this design he’s using velocity to compare to a previous value I wasn’t sure if it would be helpful yet? I think its applied differently because of the live signal and the way it receive data…