M+ standalone optimized Reaktor content from the community

Here's a mono version - let me know if this is what you were looking for, I can optimize the stereo version as well.

EDIT: Whoah, this is a fun one! I'll do the stereo version for sure. Combined with Maschine Saturator and VHS.A.D.S, this is a brilliant loop mangling processing chain. Surprisingly enough, Running OTT & VHS ADS together only results in a CPU load of ~20% (Does Reaktor recognize mono signals and reduces CPU load of Stereo ensembles? weird..)

EDIT2: And here's the Stereo version

Glad you are enjoying these! But the most credits should really go to the original Reaktor builders.

OTT was a great find, thanks for suggesting it! I just auditioned some factory kits through it and found plenty of cool riff/loop ideas. I've always been a fan of 1176-style parallel limiting, this reminds me of that but in an even more exreme way.

All in all, this has been a very good learning excercise for me. I've had Reaktor for years, and am only now starting to learn building with it. Still at the stage where I'm more comfortable analyzing and modifying existing designs, but I feel like I've already learned plenty.

I'm thinking of checking out that vocoder next, starting tomorrow. I'm hoping to be able to make it so that you just slap it to the group level, pan the synth sound(s) in the group all the way to the right, and then pan the voice/vocal/drums/whatnot sound(s) all the way to the left. The group level vocoder fx will then produce a vocoded dual mono output, which you can then stereoize and apply further fx to as you see fit. This offers most flexibility, as you can use any synth sound, or anything really, for vocoding with.

If you already haven't read this thread, I recommend doing so. Plenty of info there about getting Reaktor ensembles to play well in Maschine+:

https://community.native-instruments.com/discussion/1836/user-reaktor-ensembles-on-maschine-standalone

I agree, simple ensembles are better suited to the M+ UI, although you can cram in a reasonable amount of complexity as long as you plan out your parameter pages, group them out and label them properly. We have to currently deal with a 100 parameter limit anyways, I'd say anything beyond 40-50 parameters or so could start getting tedious to navigate.. Unless you plan out the UI very elegantly so that the user only needs to jump between a few parameter pages in order to access most of the frequently used controls.

And hey, no worries about having time for beatmaking! Using M+ is so fast the beats practically write themselves.. seriously, it feels like cheating at times 🤗

If you already didn't check the youtube Reaktor tutorial video series I linked to in the beginning of this thread, I recommend checking it out. That guy has great pedagogy skills and watching them helped me to make sense of a lot (relearning) of the basics.

Halftime? So that's like a pitch shifter or something? Maybe kind of what you can do with an Elektron Octatrack, by microtiming a recorder trig one tick before tha playback trig and pitching down? Or does it just do the same as what you can do to audioloops already in Maschine (in repitch mode), but just to realtime input?

• AFAIK, all content from the Reaktor User Library should be free to use, as long as you can run the ensembles. I would think NI would already have stopped me from sharing these if it wasn't legal, or violated some use guidelines. I am crediting the original Ens builders in every effect I have ported, and if you open up the ensemble in Reaktor editor, you can find a URL to the original ensemble page in the User Library.

• Installation instructions for all the ensembles in this thread can be found from the first post in this thread. Basically you just copy the ens file(s) to a specific folder in your M+'s SD card. Then they should show up in the browser under EFFECTS - REAKTOR - USER

• This is not in fact a limitation of Reaktor as such, but more a limitation in Maschine. A Reaktor instrument in Maschine can only ever receive MIDI data from machine, and a Reaktor effect can only ever receive 2 channels of audio from Maschine; both types of Reaktor Ensembles can only output 2 channels of audio. 2 Channels = one stereo channel (or two mono channels) in this case.

While panning the sounds might not sound like an ideal way to use a vocoder, it's actually quite straightforward in practice, and also mimics how Hardware Vocoders (ones without a built-in synth anyway) work IRL - you send them the mic as a mono signal and the synth as another mono signal. Such things are not hacks, but actual practices in many studio situations, it's simple and it works as intended (Academically speaking, grouping audio into bundles of 2 channels like in stereo, is a much younger practice, it was all mono before that). Besides, what would be a more elegant method? Some sort of dropdown menu for both signal sources (like on Maschine's sidechain)?