In case it isn’t clear, the four Switch buttons select a different step in the CV Sequencer.
There doesn’t seem to be an easy way to make “radio” buttons as the Buttons module allows you to press all or as many of the buttons as you like without being exclusive.
I'd also like to be able to have the Layer number output when you select a Layer (but you can do an easy workaround for that) and also a way of selecting the Layer by sending the layer number as in input.
Great idea to overcome the “I need zillions of number modules” problem. Will keep that in mind and might update some of my own creations. Thanks @rs2000π
I think there's a bug with p-locking Switch-1-N: seems you can't p-lock the first switch as when you try it opens up the properties for the button (Name or Remove). Works OK on all other switch buttons though. Weird.
I'm not sure that's a bug as just an inconvenient UI design decision. Any switch button will bring up the properties when tapped if it's the currently selected button.
A simple workaround is to select a different button first when you go to p-lock the step, then tap the one you want for the p-lock.
Comments
In case it isn’t clear, the four Switch buttons select a different step in the CV Sequencer.
There doesn’t seem to be an easy way to make “radio” buttons as the Buttons module allows you to press all or as many of the buttons as you like without being exclusive.
Been requesting radio buttons, an index output in the N switches and more button value freedom since ages but I guess we're the only ones π
I've done it the same way as you did. Numbers and a N-to-1 switch.
You can build a radiobutton with logic modules, there’s been talk about it before.There isn’t one module yet
To delete embedded elements in posts, it needs some text ahead, before you can delete them. That’s vanilla forums for ya
For animated gifs you need to host them elsewhere then post the link and wait a couple of seconds for it to display before you post
100% this. In fact it's almost the entire reason I built the above as all the CV Sequencer is doing is serving up the button numbers.
Any examples of this?
Ha, I just put more thought into it and here's a somewhat more elegant solution:
NIce π
I'd also like to be able to have the Layer number output when you select a Layer (but you can do an easy workaround for that) and also a way of selecting the Layer by sending the layer number as in input.
Great idea to overcome the “I need zillions of number modules” problem. Will keep that in mind and might update some of my own creations. Thanks @rs2000 π
I think there's a bug with p-locking Switch-1-N: seems you can't p-lock the first switch as when you try it opens up the properties for the button (Name or Remove). Works OK on all other switch buttons though. Weird.
Can someone else try p-locking the first button of a Switch-1-N?
Where do we submit bugs to?
I'm not sure that's a bug as just an inconvenient UI design decision. Any switch button will bring up the properties when tapped if it's the currently selected button.
A simple workaround is to select a different button first when you go to p-lock the step, then tap the one you want for the p-lock.
Ah OK that makes sense ππ»
Possibly the latter but +1