How do I get CV to select an array of triggers (or gates)

I want to use a CV to select a trig/gate output (out of say 8 or 16). This is a simple attempt to get midi signals meant for a GM drum set to spark arbitrary events (that I want to use for rhythmical purposes).

I didn’t forsee that this would be difficult, seeing as it only requires the CV to select the output, but I can’t find the right module.

Very grateful for any tips

this is a simple solution but any switch / scanner / router / panner / fader module can be used

1 Like

The v/oct (cv) selects the output (random in this case) and the gate opens the gate.

2 Likes

My first solution would be to run my 8 or 16 gate outputs into a CV-addressable switch, such as the Doepfer A-152 in hardware. I think Befaco Muxlicer does it in VCV, but I have never tried. Looks like the Count Modula 16-1 switch might work too.

Grazie! Talvolta, ci vuole una paglia per assimilare queste goccie di saggezza. Sto arrivando, poco a poco, a comprendere il concetto (CV-switches), comunque.

1 Like

Thanks! I hadn’t considered using the MIDI ⏵ GATE module, but this is a good trick. In fact, I don’t think I have ever used this module (even though it seems quite straight forward).

1 Like

I would sooner have guessed (though, I obviously didn’t) running the gate through a 1-16 switch in stead. Are there some disadvantages I haven’t considered (hard to know what I have considered, but you get it) with this approach?

you need only one module:
the cage

1 Like

Gli darò un’occhiata. Ma l’hai fatto stesso? In tal caso, Mitico! Bravo! Stile Buchla allucinante!

Penso che io intendessi Serge piuttosto che Buchla…

With a regular switch, you always have to proceed through the steps in order. With a CV-addressable switch, you can use a sequencer–or keyboard, or any other CV source–to select the steps in any order you choose.

1 Like

Assuming that the 1-16 switch was equally CV-addressable, of course. In CVC-land we often are spoilt for choice. I mean is there a good reason to avoid one-to-many as I thought, as opposed to a many-to-one. In hardware one alternative might be the best choice and in VCV perhaps the other.

Having said that I am an ignoramus. In a hardware rig I suppose everything is available all of the time, whereas perhaps modules not being used might lead to less CPU-power (I’m not being facetious, I know from experience that it is not easy to make your code take advantage of such things). Please enlighten me!