so, i just started toying with this idea, I've got 16 loopers and they are all input into specific "channel strip" abstractions. each of these channel strips has sends going to delay, reverb1, reverb2, reverb3, reverb4, pitchshift1, pitchshift2.
i've written separate abstractions that allow me to turn say, all loopers to be sent to reverb3 on/off with one simple tickbox.

but now i just started thinking, what if i could toggle them on and off with a metronome. kind of like "open a door for 1 second, then close it for 1 second, then open another door for 1 second, then close that for 1 second".

i got, obviously, one metronome and one tickbox and one sender going on, but i'm not sure how to cycle it so that it wouldn't just be 1 sec on 1 sec off on one effect, but rather that it'd be cyclical.

any ideas how this could be done?

@esaruoho

so i decided to have a crack at this, but now this unfortunately also turns all of the reverbs open for multiple seconds. so i guess every step should do a [0( to the rest of them for it to make any sense.

and this just looks chaotic, what if i need to add more? ideal situation would be to have it open for x amount of seconds and closed for y amount of seconds. but given that this is the amount of complexity i'm at, just throwing stuff at the wall and trying to make it stick, i'm not sure if this is really and truly and honestly the best way of doing it.

ok wow it turned out to be simpler than i expected. so now every 10 seconds there's a 1 second of one of these on and the rest off. obviously now i'm starting to think, what could be improved in this so that there'd be better control over this. i.e. now i'd have to change this quite a bit (change the [% x] to be a specific amount.. and mapping the [0( to all the new ones and the old ones

@esaruoho Shift registers are your friend here and they are very simple to make with [pack] and [unpack]. This is a tricky thing to effectively turn into an abstraction that can scale to any size unless you resort to using externals (need iemguts/initbang to get variable number of outputs) and at that point you may as well use a shift register external which I am sure there are many of. You can limit the max number of outlets and have an abstraction which always has 10 outlets and let an argument/inlet determine how many are used and even which ones exactly are used.

@esaruoho You could also replace the select object in your patch by the logical operator [==] to got 1/0 instead of bang as output. That's how I would do it.

@manuels said:

@esaruoho You could also replace the select object in your patch by the logical operator [==] to got 1/0 instead of bang as output. That's how I would do it.

i'm afraid i'm missing what you're saying here by quite a bit. i mean, i thought i was using [select 0 1 2 3] to use the counter (f & +1 and % 4) so that it sends a toggle-on/off to one of these 4 sends? how would using == for this change the whole thing?

@esaruoho Run the output of [% 4] into 4 separate [==] objects, one for each number [% 4] will output, [== 0], [== 1], [== 2], and [== 3].

@oid ok! i get it now! thanks!!

so, i guess a bit like this?

@esaruoho Yup.

@esaruoho
and if you arrange all
[==][==][==][==]
||||
[x][x][x][x]
||||
[s][s][s][s]

horizontal in line
makes patching easier with "fan out":
select [0( and all toggles and press shift while connecting the first toggle, you can see in these vids:
https://forum.pdpatchrepo.info/topic/13471/shortcut-replacing-wires/6

https://forum.pdpatchrepo.info/topic/13134/things-i-wish-i-had-known-when-i-started-pd/22

Or instead of connecting [0 ( to all toggles, connect [-1( message from [delay] to the float-atom-box.

@lacuna
you are right, i simplified it with your instructions to:

@lacuna said:

@esaruoho
select [0( and all toggles and press shift while connecting the first toggle

thanks, that was great! i'll use shift from now on when connecting a single toggle to 16 sends, this is sure to save me a lot of grief