Searching for Module/Macro or Core That Holds & Outputs Last Non-0 Value Sent from Multiple Inputs

juanholdero

Been searching for this with no luck. I need a module, macro or core set up that will hold (for a potentially unlimited time period) and output the last given non-0 value from multiple inputs.

Background: I have many modules that each contain a Midi Select Note Gate programmed to a specific note and a multiply value that take the input from the Gate and multiplies it with a specific unique constant. I'm searching for something that can essentially 'remember' that last note pressed, which I will use to switch a Stacked Macro display accordingly via a panel index.

I'm fairly new to this so I welcome any criticism and advice for this. I'm open to any solution, but I'm genuinely lost even though it seems like a fairly simple context. Thanks (:

KoaN

https://community.native-instruments.com/discussion/18653/searching-for-module-macro-or-core-that-holds-outputs-last-non-0-value-sent-from-multiple-inputs

If i understood correctly this should do the work,the separator is used to get rid of the 0s,i don't think it is included in Reaktor 6 though so i showed the structure to the right and then all the signals go into a merge module which lets through the last active event

colB

https://community.native-instruments.com/discussion/comment/107727#Comment_107727

You only need one separator, stick it after the 4-way merge. So in Primary it would look like:

colB

@juanholdero Assuming you are trying to select some set of different processes/panels using specific midi notes, there might be better ways to achieve this! It really depends on what you are trying do achieve (not how you think it should be implemented!).

What are you trying to do - functionality overview not implementation?

KoaN

https://community.native-instruments.com/discussion/comment/107765#Comment_107765

I thought of a condition where a 0 would arrive at the same time as another value and cancel it because it has priority "on lowest input",could be possible no? Maybe a very rare condition but still,like a key being released at the same time another starts,the new one wouldn't pass through.

colB

https://community.native-instruments.com/discussion/comment/107799#Comment_107799

What condition?

It shouldn't be possible if all connected devices are correctly following the MIDI spec., and there is no bug in Reaktor. MIDI is sequential, and there should be some time between every midi message, should be more than an audio clock tick, and that's the only time slice small enough that Reaktor could think two sequential events are simultaneous - but even then, only if they have been re-encoded as an audio signal for Blocks or similar.

juanholdero

https://community.native-instruments.com/discussion/comment/107765#Comment_107765

Thanks man, this worked perfectly.

juanholdero

Want to thank everyone that replied - makes me feel happy