PLOGUE BIDULE PROGRAM CHANGE EVENT MOD
PLOGUE BIDULE PROGRAM CHANGE EVENT SERIAL

Is there a way around this? How can I split the gates? If I want to output to 4 different channels, I need four different instruments in reaktor for the outputs, right? Since each instrument has it's own channel. etc? If I'm splitting to different output channels by note, how do I split the gates the same way? The confusion I have with using the individual MIDI objects in reaktor is this: If my incoming data stream gets divided into pitches and gates, and I want to split the data and rechannelize it or transpose it, how does the pitch get re-connected with its correct gate? Does reaktor somehow know they belong together, even if the pitch gets modulated or rechannelized. Plogue would still function as host, but I'd like to do as much midi processing as possible within reaktor, for the display options. I'd like to be able to use reaktor to switch incoming midi between different channels of output, and re-allocate various controllers, depending on the state of other controllers. to filter, rechannelize, remap or rescale midi messages in reaktor. I'd like to come up with a library of MIDI processing modules in reaktor to do what I did in plogue. I have been using plogue bidule for this, but I miss having a user-configurable display of the state of the system.

I also have a tap tempo implementation that takes midi CC messages from a button.

PLOGUE BIDULE PROGRAM CHANGE EVENT MOD

All controllers are rechannelized differently for each instrument, and there is various custom processing for each one, such as latching mod wheel events to control the leslie, and converting notes to CC messages. I use a controller to page through instruments, and another to page through a limited number of patches on the currently selected instrument. My setup is an edirol controller that currently runs 4 instruments live- B4II, Kontakt, Pro53 and Reaktor. I'm really not sure whether I should use the individual midi in and out objects or the generic mono message object. Okay, I have a stupid beginner question from someone who is trying to use R5 as a MIDI router. i'm sure r5 will make me wish i had not bought max, but we'll see. you know, something that says, no matter what happens you MUST pay attention to this at some point.

then reaktor just flat out drops a good deal of event activity, presumably in favor of making sure the audio drops out for as little time as possible, even if the ens is not making any audio at all! i just want some means of applying a 'priority' to event streams.

PLOGUE BIDULE PROGRAM CHANGE EVENT SERIAL

you can edit note lengths, suspend all note offs (sustain), turn them back on (which also sends note offs to any note on any channel that has missed the note off it would have otherwise gotten while at the same time not sending ALL NOTES OFF TO ALL CHANNELS, because that will really clog up your serial pipeline) and never miss a beat, no stuck notes, no nothing.

for example, i made a sequencer called no!tron. i totally agree with everything you said in principal, just not in practice. I'm not saying that Max is better than Reaktor, just pointing out some areas where R could use a little encouragement.Ĭlick to expand.that multi-slider was just an example of how easily you can make a boring max gui object look rather fancy with nothing more than a floating inspector. So it makes it very easy to record and play back live midi loops with different durations that phase-shift against each other delightfully. Design a Reaktor macro that does that for an arbitrary number of voices and I'll be REALLY impressed.Īnd then there's the seq object, which records any length of raw midi data and plays it back - it's ridiculously easy to loop it because it tells you when it comes to the end of the data so you can retrigger it. Midiflush does NOT just send an all notes off - it keeps track of what notes have gone through it and when triggered sends note offs only for the ones that haven't already received a note off. As far as I can tell its written in C or something like that, not made of other standard Max objects. Click to expand.Borax is part of the standard package, though for all I know it may have originally been written by a user - there seems to be some overlap between users and developers, as there is in Reaktor.

Plogue bidule program change event