My patch has a single design which I need to use multiple copies of. I was hoping there may be some suggestions following this if I upload the patch. grid1.pd

Inside the patch are copies of a sub patch called gridSampler. Inside is all the same code except on the objects which I've appended a, b ,c or 1 ,2 3. so the patch doesn't confuse object data. including the array table....is there a way to have this set up so i only have to send one value ? rather than change every object every time i want another gridSampler?

Many Thanks,

@Fauveboy Using abstractions...... you were nearly there (and did not upload the abstraction [GridSampler])
like this.zip
See here for more help.......https://forum.pdpatchrepo.info/topic/9774/pure-data-noob/4
David.

@Fauveboy Not sure if I got it right but if you name your abstractions [gridSampler 1], [gridSampler 2] etc.. then inside the abstraction you can get that argument with $1 even in object's names.

gridSampler$1.pd

ah sorry so heres inside gridsampler....theres alot going on inside. im not sure I cant apply a technique where I just have to design the gridsampler once and just sending it a $1 value to it and everything inside to get a different instance can apply?

@Fauveboy I have started but I don't have time to finish (flight to Prague waiting).......
Yes, you can have just one gridSampler. It is about the most important thing to learn as you advance with Pd.

like this.zip

I have changed the table name and some of the send/receive objects so you can see the principle.
Change every send, receive, send~, receive~, throw~, catch~ .......
Add a $1 to their names and they become unique in every copy of the abstraction [gridSampler X]

so change (for example) [r phasea] to [r $1-phasea]

If you are sending or receiving information from outside the abstraction use the value of $1...... the argument of the [gridSampler] you want to communicate with.
So to send to [gridSampler 1] use [s 1-phasea]........ to send to [gridSampler 2] use [s 2-phasea]

Inside the abstraction $........ outside it's value....... its value in its name too (it is outside)..... see example above...
Every $ (in an object... not in a message) will be given the value (become that value) when the abstraction is created.

David.

Thats great, Looking alot tidier now.....To get multiple instance off thw abstraction in this case gridSampler X, can i use poly so I dont have to copy and paste gridSampler 1, gridSampler 2 ect...? Have a good time in Prague, Many Thanks!

grid2.pd gridSampler.pd

I think ive just about finished all the variables. However the array isnt being read yet? if I tap in the read message to send the wav to the array it says the following:
Although thats confusing because it has managed to load the file?

@Fauveboy If you click on the read message then the $1 inside it won't work. Try connecting a [bang( message to the [+ $1] object (which I personally would've called [f $1], and click on that instead whenever you want to send the sample to the table.

Thank you for the suggestion I how see how that works now. Did my mention of the poly idea make any sense ?
I mention the poly also because I have this repetition of code here and its only values that change to assigne buttons to a grid but it would alot tidier if I could right it once and an bit of math to the values are correct

@Fauveboy You can also use symbols as arguments, so I'd do it like this to make it tidier, you might want to check everything since I had to retype it all, but I'm sure you can adapt it to your needs if you find the concept useful.

monome-parent.abs.zip

One note is that instead of sending [+ $1] to pack, you can include it directly as [pack]'s argument.

Hope it helps.