Native Instruments released Reaktor 6 !

[grymmjack]

And it looks like, we can access the deeper bits outside of blocks, in our own core cell stuff, though I've never built anything using core cells, it shows the same filter components from audio -> filter when i looked at the structure of Bento Filter inside: SVF (NL) in core.

[Unfocused]

What about using the new table structure to voice trigger on a per MIDI note basis, i.e. an "88x1" element table that routes MIDI On messages to a separate voice for each note value?

At any rate, R6 looks really cool, but I think I need to hold off until K11 since I just upgraded my Reaktor 5 license to K10 during the summer sale.


-u

Regular Reaktor stuff can be polyphonic, in a single instrument like EvilDragon mentioned, just FYI. I don't want to confuse or misdirect anyone here. It was only Blocks I was referring to that acted like this.

So no need for a table kind of thing, when you go lower level (one down from Blocks) you're back in business with everything you'd expect out of Reaktor, including more than one voice and thus chords work, etc.

This I know--been using Reaktor since just before R3 was released (more of a tweaker than a builder though). I just wasn't clear.

My point was that someone might be able to build a custom block with a table structure as I described to allow polyphony. Worth a try...


-u

[Apostate]

Bought this today, WOW.

I'm currently sidetracked by Grip 1.2 though

[olikana]

if someone could make a video tutorial on turning a mono "blocks instrument" into polyphonic that would be very helpful.

I'll try to follow's mokafix instructions in the meanwhile. thanks

Seems like polyphony is confusing for lots of people...

POlyphony in a vst means each note you press virtually duplicates the polyphonic engine part.
So you get virtually N times the engine running, mixed and sent to the monophonic output, which typically either goes directly out or through a built in monophonic FX chain depending on the instruments...

In Reaktor you create a new ensemble. if you plan do make polyphonic synth, you create an instrument and set the max polyphony you wish there.
if you try and directly wire your engine to the instrument output, it seems ok, but then outpside, in the ensemble level, if you try to plug that to your soundcard you will get an error (red wire and connection with a [!] symbol).
= you need an audio voice combiner before sending it out of the instrument, which basically sums all virtual voices and merges them for good before sending them to the outside world.

now, IF you want to say make a polyphonic monark with the 3 monark Blocks, load them and besides create a new empty instrument with macros inside.
You then copy the content of each 3 blocks into the 3 macros inside your new instrument.
Then connect them as you wish, add a voice combiner at the end and here you go.
(hope I am not making any mistake there)
you also need some midi modules etc of course for gate and pitch inside the instrument you made.

[deastman]

if someone could make a video tutorial on turning a mono "blocks instrument" into polyphonic that would be very helpful.

I'll try to follow's mokafix instructions in the meanwhile. thanks

Basically what mokafix is suggesting is to create a new block, aka instrument. Inside of it, create several macros, one for each voice. Inside each macro, you would put everything you want to use polyphonically: oscillators, envelopes, vcas, etc. You would use a voice combiner to merge the audio output from all of these macros into a single audio stream. So if you want to have six notes of polyphony, your instrument/block would contain six macros, each of which would contain another copy of the oscillators, envelopes, etc.

The problem with this is that unless you're going for an extremely basic duophonic design with multiple oscillators but a single vca/filter/envelope, you end up building an entire synth into a single block. That kind of defeats the whole point of using blocks to begin with. I'm sure we'll see some of those being created in the user library eventually, but it really seems to me to be missing the point. I suspect we'll also see some blocks to facilitate voice switching, but again I think its mostly more trouble than its worth.

It really makes more sense to look at the blocks framework as something akin to analog modulars. Yes, you can patch up something polyphonic with enough time and effort, but it really isn't worth it. If you want polyphonic, just use an existing Reaktor synth or something else entirely. The fundamental nature of an analog modular is that of an audio playground in which to explore patching together modules in interesting ways and coming up with unusual sounds which a typical prepatched synth can't duplicate. Patching it into a lead or bass monosynth is easy enough, but that is really one of the most boring uses possible. Forget about polyphony... just start experimenting and make some weird noises! (This, my humble opinion, is based on nineteen years' experience as a eurorack modular owner... take it or leave it.)

[cyberheater]

I've had Reaktor since it was called Generator and i'll not be buying this upgrade.

I can't afford it right now

I can't wait to get it. It looks amazing.

[overhishead]

is it possible to look inside the modules and see how they are made?

for example, if you wanted to learn how to make a monark filter, could you go inside and look at the coefficients?

[Mokafix]

Oh hi there, Efflam! Nice to see you around here

Hi !
had not logged in for a long while...

Basically what mokafix is suggesting is to create a new block, aka instrument

yes, actually it was more theoretical. Reality is a bit more complex because the blocks architecture with the modulation etc makes also parts of the GUI connected to the main core process, so when you use polyphony not only you need to combine voices before output but also put some event combiners here and there and end up with something not super optimal for your cpu I think...

This is not patching blocks anymore it is becoming a builder... some work but definitely within reach if you know what you want to do and have a bit of patience.

It is pretty amazing that Blocks is already giving some users a itch to become builders

[hivkorn]

someone have try to use it under osx 10.8.5 ?

[whyterabbyt]

if someone could make a video tutorial on turning a mono "blocks instrument" into polyphonic that would be very helpful.

I'll try to follow's mokafix instructions in the meanwhile. thanks

Basically what mokafix is suggesting is to create a new block, aka instrument. Inside of it, create several macros, one for each voice. Inside each macro, you would put everything you want to use polyphonically: oscillators, envelopes, vcas, etc. You would use a voice combiner to merge the audio output from all of these macros into a single audio stream. So if you want to have six notes of polyphony, your instrument/block would contain six macros, each of which would contain another copy of the oscillators, envelopes, etc.

Pretty much. I'd expand that that as

" Normally in an instrument you would use a voice combiner to merge the audio output from all of these macros into a single audio stream. But if you want to have six notes of polyphony output individually, your instrument/block would have to contain six macros, each of which would contain another copy of the oscillators, envelopes, etc"

just to make things absolutely clear.

i suspect you'd also have to do a bit of work to remake the UI, btw.

The problem with this is that unless you're going for an extremely basic duophonic design with multiple oscillators but a single vca/filter/envelope, you end up building an entire synth into a single block. That kind of defeats the whole point of using blocks to begin with. I'm sure we'll see some of those being created in the user library eventually, but it really seems to me to be missing the point. I suspect we'll also see some blocks to facilitate voice switching, but again I think its mostly more trouble than its worth.

It really makes more sense to look at the blocks framework as something akin to analog modulars. Yes, you can patch up something polyphonic with enough time and effort, but it really isn't worth it. If you want polyphonic, just use an existing Reaktor synth or something else entirely. The fundamental nature of an analog modular is that of an audio playground in which to explore patching together modules in interesting ways and coming up with unusual sounds which a typical prepatched synth can't duplicate. Patching it into a lead or bass monosynth is easy enough, but that is really one of the most boring uses possible. Forget about polyphony... just start experimenting and make some weird noises! (This, my humble opinion, is based on nineteen years' experience as a eurorack modular owner... take it or leave it.)

I agree with all of this. Im sure there are probably a couple of folk out there using multiple Doepfer A-111-5 modules polyphonically, but its sorta missing the strengths of a modular; the nature and application of a complex monophonic instrument is intrinsically different from that of a simpler-but-polyphonic one.

[whyterabbyt]

is it possible to look inside the modules and see how they are made?

for example, if you wanted to learn how to make a monark filter, could you go inside and look at the coefficients?

Some subcomponents of Monark were 'locked' so you couldnt look inside them. I suspect that might not have changed for the Blocks version. Someone who alkready has R6 would be able to confirm that.

[Mokafix]

is it possible to look inside the modules and see how they are made?

Definitely. I would recommend the multiwave OSC for exemple. Fairly easy to see what is doing what in the process corecell.

for example, if you wanted to learn how to make a monark filter, could you go inside and look at the coefficients?

Monark filter macro is locked as in the original synth so in this very case answer is no. Only Monark and Driver have locked macros if I am not mistaken. Everything else is completely accessible.

[Ingonator]

I just logged in into my NI use account and at the shop i found that as a Komplete 6 (+ Monark) owner i am allowed to purchase the "Update" version of Reaktor 6 for 99 €.
while this offr is tempting i am not sure if i really need the upgrade to Reaktor 6 at the moment. Recently i was mostly using Reaktor to load Monark (and to some modifcations to it) anyway.

Will maybe wait for Komplete 11 and try save some money for the upgrade to it (also as i still only have Kontakt 4 and would be interested in v5).

[Apostate]

I just logged in into my NI use account and found that as a Komplet 6 owner i am allowed to purchase the "Upgrade" version of Reaktor 6 for 99 €.
while this offr is tempting i am not sure if i really need the upgrade to Reaktor 6 at the moment. Recently i was mostly using Reaktor to load Monark (and to some modifcations to it) anyway.

Will maybe wait for Komplete 11 and try save some money for the upgrade to it (also as i still only have Kontakt 4 and would be interested in v5).

Customer support was predictably sketchy when asked, but I got a strong intuition from my dealings with them that KU 11 won't be out until well into 2016. Reaktor 6 is interesting enough to warrant an upgrade in advance, especially at that price.

It depends on how deep into programming you want to go, you could easily make Reaktor 6 into a fairly consuming hobby, it has all the requisite depth. I know it's captured my interest, and has actually been diverting me a bit from my recent purchase and studies of Zebra/Dark Zebra. I'm pretty sure that last is saying something.

[EvilDragon]

Will maybe wait for Komplete 11 and try save some money for the upgrade to it (also as i still only have Kontakt 4 and would be interested in v5).

K11 will probably not have Kontakt 5, but 6 instead, though.