Native Instruments released Reaktor 6 !

[hakey]

Guys, do you remember the times when Pro-53 was chipping away at that CPU?

Today I can run tons of instances of it at huge unisons and CPU still nicely plods along.

Thing is, for a couple of years increases in CPU speed have been achieved by putting more cores on a chip. So, yes, tomorrow's faster CPU will run more instances of Reaktor, but won't perform any better on a single instance of Reaktor. Without multicore support, an instance that chokes the CPU now will do so next year, the year after, and the year after that.

[EvilDragon]

That's a given, but the problem of multicore processing in fully modular environments is real, and not an easy one to solve. If it's at all possible. As mentioned several times already here - complete modularity doesn't gel well with parallel processing simply because of the possibility of feedback in the structures, so the problem of what is concurrent and what's not gets very hard if not impossible to solve. I guess the only thing that could be spread to multiple cores are voices of polyphony, but that's about it. Yet, that also gets tricky in Reaktor, since voices can be used not just to play notes, but to process signals (like vocoders, spectral multiband processing, etc.)

Is there any other fully modular synth that implements multicore processing effortlessly?

[Dostoyevsky]

Is there any other fully modular synth that implements multicore processing effortlessly?

Supernova for Supercollider. Well, "effortlessly" might be a bit of a stretch

[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

[trimph1]

Is there any other fully modular synth that implements multicore processing effortlessly?

Supernova for Supercollider. Well, "effortlessly" might be a bit of a stretch

That is a bit of a stretch. I am rather liking Reactor 6 but I certainly don't think I will kick Supernova off.

[aMUSEd]

Does Max 7 support multicore?

[grymmjack]

Blocks are monophonic. There is no fixing that, or work-arounds, that I know of. FYI.

So a user can't play chords playing with an Ensemble built with Blocks ?

Right. Of course you could create multiple oscillators tuned to a chord, and the OSC5 has a chord mode with 3 options, but it's not the same. Yeah, you can't play chords, at least I haven't figured out how.

I'm not quite sure what the rationale was, but it's a bummer. I upgraded before I checked it out, assuming that polyphonic playback was so fundamental a feature it was implied. I thought it was a demo limitation that it was Mono only. Stupid me

Oh well,

[grymmjack]

You can still use regular polyphonic instruments, man.

GUI updates are alone worth it.

I don't have that much buyers remorse, was just shocked when I couldn't get more than one voice to come out of the latest showcased new feature. I dove into the individual structures and enabled voices, and stuff but it made no difference and you explained simply, why that was.

So the new question is can we use the stuff IN the block in our own polyphonic singular ensembles? Will try that next. The UIs are nice, but not required I mainly bought for the sound and the ease of use. Was thinking "hey these Reaktor blocks can replace KarmaFX Modular" but I was wrong.

[grymmjack]

So being that blocks are monophonic, can you do duophonic somehow with two oscillators? So each oscillator is still mono, but you get two voices?

Yes, I did that successfully.

[Sparky77]

You should be able to, put a note/gate Block for each osc...

Great to know, thanks for the post Evil.

[grymmjack]

You can set one note/gate block to low priority, the other to high priority, there you have it - duophony.

Can you explain this? I created a couple basic "rows" of modules. Bento Osc's with SKF filters and amp env/2 adsrs and a mixer. I patched them so that they ran from the same Note In's out to the signal separately through each row, this effectively works, but it's not adding any voices.

So I duplicated the Note In's and ran both rows of modules uniquely from a note in and that seemed to work in that i could enable glide and legato on one note in and leave it off on the other - basically 2 little micro synths kind of thing, but it still isn't duophonic I guess, because I didn't do what you said. I just would like to understand what you mean by low and high priority - do you mean the note priority in the note In module?

*edit: it was me*

Thanks EvilDragon.

[grymmjack]

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.

[EvilDragon]

See the PRIO parameter? Change it from LOW to HIGH on one of them.

[Echoes in the Attic]

Awesome. And so simple.

Duophonic with the fm will surely be something similar to the amazingness that is duophonic + Ring Mod in Diva/Oddity/impOscar.

[EvilDragon]

It shouldn't be at all problematic to make a ring modulator Block. It's just a multiply operation between two signals. So easy to just take that 4 channel mixer factory Block and multiply the 4 inputs in various combinations then send that to the 4-channel amplifier...