Hi, I'm working on a new system for a project and i'm going to have to manually type in an awful lot of sends/receives. 14, 336 i've calculated it at.

Before I start manually typing "s t1s1t1" all these times and lose my mind are there a faster way to do this? It must be sends as its a sequencer system and these are the steps and each one must trigger this information for that function whenever I need it if I need it. I'm using Max for live if features are restricted regarding this issue.

If I hadn't of asked here I would set it up so I would only have to change the last digit on the end of the send (everything would be copied and pasted patch wise) so it would be a case of clicking on each object and changing that last digit.

If this is the case i'm not too fussed as had to do it this way before with another aspect of the patch and was well worth it but it wasn't an awful lot of fun so wondering if there's a work around.

Before I start manually typing "s t1s1t1" all these times and lose my mind are there a faster way to do this?  It must be sends as its a sequencer system and these are the steps and each one must trigger this information for that function whenever I need it if I need it.  I'm using Max for live if features are restricted regarding this issue.

If this is the case i'm not too fussed as had to do it this way before with another aspect of the patch and was well worth it but it wasn't an awful lot of fun so wondering if there's a work around.  

naming-mass-sends

I’m just curious. I’ve never used such an amount of send/receives. What is it all about? Can’t you integrate the values into lists?

Have you considered using poly~ and the "target" message to manage the steps?

or you can check [thispatcher]'s helpfile and the scripting section:

or, even better, use javascript to create all the objects.

Hi LSKA I had a play around with your patch and made it work for what I want, will have a bit more of a look but will cut down the time considerably anyway! Was thinking could duplicate your patch and edit the text for each copy and then with a single bang hit them all and then generate every send, then duplicate for receives. Its wicked though so thanks! :)

Hi BERND its basically a drum/music sequencer music making thing I'm rebuilding. The part I wanted to build is a mute step feature.

There's 8 tracks and steps all the way up to 128 if you break it down into bars. Each step of each track can send a bang using a switch so if there's a snare or sound in a certain step it will just mute every single step on tracks you decide from that step. It also has a reset button on the sequencers to go back to normal. Just think it will be sweet to hear what it does as love silences in tracks and then maybe automate it so the track dissolves to nothing or have sequencers runner across it randomly adding silences in time for ends of bars. In terms of lists I guess I'm just used to doing it this way.

Hi BERND  its basically a drum/music sequencer music making thing I'm rebuilding. The part I wanted to build is a mute step feature.
There's 8 tracks and steps all the way up to 128 if you break it down into bars.  Each step of each track can send a bang using a switch so if there's a snare or sound in a certain step it will just mute every single step on tracks you decide from that step. It also has a reset button on the sequencers to go back to normal.  Just think it will be sweet to hear what it does as love silences in tracks and then maybe automate it so the track dissolves to nothing or have sequencers runner across it randomly adding silences in time for ends of bars.    In terms of lists I guess I'm just used to doing it this way.


if all 16,000 are all in the same patcher window you should change that design anyway IMO - but mass creation of objects can be done via scripting.

however, it should be okay to put 16,000 the same obejct(s) into subpatches with 64 or 100 instances each.

then you only have to create and connect 100 and then make 160 copies of that.

16,000 different names could be loadbanged using arguments to the subpatchers which do some + to the uzi inside.

Its cool, I'm just not too knowledgeable on scripting to be honest but i'll look it up. I just use a lot of gates, basic code and things I know well. Not the best programmer really but everything works and is plugged in correctly and makes quite mad music.

I did the manually typing the last digit's with a similar problem in scale for a different feature of patch which took about three days but all it does is just fires a simple floating point number into the steps and the whole thing worked fine in sub patchers. Its not constantly these values yet but when I use it in real time and hit the button its not a problem. I just got max toolbox too which i'm going to use for connecting the cables so its not bad now compared to before at all, well happy about it :) if your interested I can post an audio clip when its done.. I will bookmark thread incase.

Its cool, I'm just not too knowledgeable on scripting to be honest but i'll look it up. I just use a lot of gates, basic code and things I know well. Not the best programmer really but everything works and is plugged in correctly and makes quite mad music.  

I did the manually typing the last digit's with a similar problem in scale  for a different feature of patch which took about three days but all it does is just fires a simple floating point number into the steps and the whole thing worked fine in sub patchers. Its not constantly these values yet but when I use it in real time and hit the button its not a problem.  I just got max toolbox too which i'm going to use for connecting the cables so its not bad now compared to before at all, well happy about it :)   if your interested I can post an audio clip when its done.. I will bookmark thread incase.


Naming MASS sends