How do I create mutually exclusive buttons in reaktor

manhippo
manhippo Member Posts: 4 Member

Hi folks. First time here. Trying to belatedly learn reaktor to build a specific audio processor I want and can't find anywhere.

As part of that, I want to create a group of buttons that have arm exclusivity, so that when one of them is on, all the others are off, and if i click a different one in the group, the same behaviour tracks. This will be for an array of 8 buttons.

I can see various ways to do this for 2 buttons alternating, but I'm a bit stuck on how to make the principle apply to more buttons.

Does anyone know how to do this, or can anyone point me to an existing ensemble with this behaviour that I can study?

Comments

  • silentio246
    silentio246 Member Posts: 54 Helper

    Maybe this is what you are looking for:

    https://www.native-instruments.com/de/reaktor-community/reaktor-user-library/entry/show/2987/

  • colB
    colB Member Posts: 1,013 Guru
    Answer ✓

    Here's an example I posted a few years ago (2018!), it shows two ways, one based on the Blocks A/B toggle, the other is my own that uses some bitwise arithmetic. There are various other ways to do this as well.

    The main thing is that each time a button is pressed, the display (or state) of all the buttons must be updated, and the output for the array should also be updated.

    There are also options like allowing all buttons to be off (or not allowing that)

    Which is best depends on the situation, and also on your level of understanding - no point in using something you don't fully understand, because then you're screwed if it develops a problem, or you need to modify the functionality.

  • colB
    colB Member Posts: 1,013 Guru
    edited January 31

    Here's an alternative without the bit twiddling

  • manhippo
    manhippo Member Posts: 4 Member

    Amazing. thankyou, these are very helpful. I will study them and see which methodology best suits my needs.

    I'm trying to create two routing scenarios. One for controls, where a bank of 4 common commands can be sent selectively to one of 8 tracks by pressing a button to select that track.

    the second where audio out of the tracks can be sent back to a feedback bus, so in that scenario any of the 8 tracks could be selected, the output would be sent to the bus, but then on receipt of a separate command they would revert to their default routing.

  • colB
    colB Member Posts: 1,013 Guru

    @Sunborn dude, I know it's not your fault, but this whole 'Answer' and 'Best Answer' mechanism is a major turn off for me.

    It was/is an open question, there is no best answer, there are lots of different ways to achieve what the OP was asking, all are valid, which to chose depends on context. It should be an ongoing discussion, but 'Answered' and 'Best Answer' labels act to finalise it and shut down further discussion.

    And it shuffles the order of replies. They appear out of chronological order, so any conversational discussion that did happen is disordered.

    It's the sort of thing that maybe works well in the context of someone asking how to set up midi in their DAW, or how to change sample rate - technical -one correct answer. But here, it just gets in the way.

    /rant

    Anyway, keep up the good work!

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,302 mod

    ok mate, i will do my best to remember it! 🙏

    however, there is an easy way to "fix" this… i will change the thread from "question" to "discussion". 😉

Back To Top