Doubling metro speed output?

For these things I use metro-->counter, then the counter output goes into three modulo objects (in your case, % 1, % 2, % 4). Each of these goes to its own sel 0. The mods give you the remainder of the incoming number, so % 1 will always be 0, hence always bang---your bpatcher which needs the most bangs. In this case, set the metro to the *fastest* pulse, or the 1/16 note. So, the % 2 will give you a bang every other pulse, and the % 4 will bang every 4.

You could have a dropdown with a selection of numbers to set the mods, like 1, 2, 3, 4, 6, 8, 12, 16 perhaps. This gives you a wide selection of common subdivisions to choose from; I use something like this a lot. The counter doesn't need any min or max arguments at all; it doesn't matter how low or high it goes, the remainders will always behave in these cyclical patterns.

Gregory mentioned the phasor~ etc. objects because they have much better long-term accuracy than metro (which is not designed for this and tends to drift). If you use the above example, everything will be synched together (only one metro), but compared to an external clock it will drift. Using phasor~ and edge~ to generate your bangs is much more reliable (audio objects are processed at a higher priority than scheduler objects like metro). So you can use that piece to generate the bangs instead of metro, then go into the counter etc.

Modulo is often overlooked but can be very useful.... another common use is to filter octave displacement out of a MIDI note, in other words, take the note into a % 12, and the output is 0-11, corresponding to that semitone in the scale---no matter which octave it's played at. So 63, 75, and 27 will both give you 3, or E-flat, though they are in different octaves.

--CJ