Im working with a patch which needs to be displayed on 16 by 16 grid hardware, called monome. Inside the file is an abstaction called gridsamplerPtest $0. There is an unpack f f f object which receives grid coordinates from the monome. These values then need to be sent around the patch....inside the sub patch load.sample there are the sub patch monome.abs inside there receives values from the grid. however where i;ve left the comment "assign to grid" I need to specify the the coordinate values i want i want to use as the condition. how do i do this after trying to make unque instances of the first sub patch $0 ? will the gird values have to be put in manual..this would be counter intuitive to the design? and I do require multiple instances of gridsamplerPtest? grid250717 2.zip

@weightless There are other errors that make the patch non-operational such as.....

It would need to send info from a whole row of buttons to achieve the objective.
Selecting for x and sending y, (on/off....z.... sorry, s in this case) onwards.

The whole probably needs going through with a fine tooth comb.... But is impossible to design without a "button map".....
With a button map a ground up redesign for the osc (incoming data routing) would be advisable I think.
David.

@whale-av i already wrote a button map concept for @fauveboy with which he could flexibly assign buttons to individual moduls: https://forum.pdpatchrepo.info/topic/10749/binary-counter/13

Even wrote a trainer for the monome, with which he could easily create the button map: https://forum.pdpatchrepo.info/topic/10749/binary-counter/16

But this was not wanted for some reason...

@Fauveboy Some of it fixed.. I think... row 8, 9, 10 should work...... grid3.zip

@whale-av i m just away from the monome at the moment to test it properly... the 2nd argument we give monomer.abs can this be a variable that can be sent the argument or is this design suited to type in these constant values ?

@Fauveboy Throw grid3 away..... there was a mistake anyway.
Yes, anything can be done in Pd.......... grid4.zip
Row changed by message (monomer retains function, only row changed).
You could use the buttons of a row to change functions throughout.... by sending such messages...
David.

the problem is if i do two instances of gridSamplerPTest $0 when I change monome $0 7 whatever...its changes it in both instances of gridSamplerPTest I thought $0 would help separate the two?

@Fauveboy

grid5.zip
$0 gone.... except for local sampler messages. No more mind mangling.

Gridsamplers numbered (0-15).
Row one buttons control which gridsampler is being actively controlled (and is sending back to the leds).
All gridsamplers continue to play.... correct? or should stop?

Probably no sound, as I have not touched your [pd fader] volume control.
There will be small mistakes maybe?, probably?.
David.

thanks sorry it took a bit long to take a study of the patch....the limitation is that monomer.abs is set up to display only one grid sampler...i changed it to this so now the display is comes down from the top of the 16 x 16 grid but....is there away to set up monomer.abs so i can do this without changing it globally...i would then set the leds to toggle then it will be possible to view muliple samples on the grid

This is working in the correct way but it stops me from controlling multiple samples. compared to previous designs..if I need to launch two samples simultaneously it cant happen?