NI Reaktor, I forgot how awesome it is

[mellotronaut]

Yeah, snapshots/presets are a total mess. I always save anything Reaktor related as an Ableton rack. Much easier.

great idea! thank you very much!

[bmanic]

Anybody know some good video tutorials on advanced core level programming for Reaktor? Stuff that goes through how the various events and signals are ordered etc? It can be paid tutorials, as long as it's not beginner/mid/basic stuff.

I'd also like a really comprehensive tutorial on the modern way of creating User Interface panels.. you know the way Razor, Monark and all of those do the separate audio engine + UI core level stuff.

I only found some super old ADSR tutorials and while they do look really quite comprehensive I thought that maybe there are other sources out there? Anybody know?

I'm planning on possibly spending my Christmas holidays exploring Reaktor again at a deeper level. Yes I know I should just sit down with the manual and start dissecting a lot of other people's work but that takes way too much brain power and I don't really feel like burning out during Christmas.

[EvilDragon]

The ADSR tutorial is quite well done IMO.

[gentleclockdivider]

Anybody know some good video tutorials on advanced core level programming for Reaktor? Stuff that goes through how the various events and signals are ordered etc? It can be paid tutorials, as long as it's not beginner/mid/basic stuff.

The old forum was a goldmine , but hey wait... N.I. decided to put it down .
The new forum and it's admins are a f.disaster .

[CrystalWizard]

Anybody know some good video tutorials on advanced core level programming for Reaktor? Stuff that goes through how the various events and signals are ordered etc? It can be paid tutorials, as long as it's not beginner/mid/basic stuff.

The old forum was a goldmine , but hey wait... N.I. decided to put it down .
The new forum and it's admins are a f.disaster .

Agreed. Par for the course NI.

Evil Dragon-"The ADSR tutorial is quite well done IMO"
I"ll check that out.

great idea bmanic. i am now somewhere with harsh winter weather, seems like a great project.

[elassi]

Anybody know some good video tutorials on advanced core level programming for Reaktor?

For the Core part I think you're better served with DSP courses/tutorials as Reaktor's core department is basically low-level DSP programming with modules instead of instructions.

And there's the dedicated 200+ pages Core manual (rather a module description) you're probably already aware of: https://www.native-instruments.com/file ... ual_EN.pdf

re. User Interface Panels
Monark and the like are actually no quantum physics stuff but slick designs crafted by skilled people. The tech itself is quite simple and has been there since the early days. When you know how to stitch images with your graphic program of choice your're almost done. If there's demand I may make a tutorial for this covering the most important aspects. It has always been fun to skin ensembles.

[Scrubbing Monkeys]

^^^
I for one would be very interested in re skinning some older stuff with bigger guis

[elassi]

Is there a particular ensemble you'd like to re-skin?

[Shabdahbriah]

re. User Interface Panels
Monark and the like are actually no quantum physics stuff but slick designs crafted by skilled people. The tech itself is quite simple and has been there since the early days. When you know how to stitch images with your graphic program of choice you're almost done. If there's demand I may make a tutorial for this covering the most important aspects. It has always been fun to skin ensembles.

I seriously intended to get into this ages ago, with instruments I wanted to make for Reaktor and/or Kontakt, and got distracted with more pressing 'life' matters. Would love to study a Reaktor skinning tutorial. I do recall I 'stitched' quite a few images together a decade or so ago, so I think I could figure that out again. I use Affinity Designer and Photo, or the old Jasc-7.

[bmanic]

Anybody know some good video tutorials on advanced core level programming for Reaktor?

For the Core part I think you're better served with DSP courses/tutorials as Reaktor's core department is basically low-level DSP programming with modules instead of instructions.

I do know my way around some DSP basics but I'm no programmer.. it's partly why I feel more comfortable using tools like Reaktor/MaxMSP etc. I'm no stranger to scripting languages either so I can parse and learn basic things quite well.

The thing with Reaktor that has been slightly troublesome over the decades is the way things are instanciated, meaning the way things like events are ordered depending on when you insert things into the structure. I'm keen on learning when/why/if this is also the case with Core level components or if there is more freedom there.

And there's the dedicated 200+ pages Core manual (rather a module description) you're probably already aware of: https://www.native-instruments.com/file ... ual_EN.pdf

Yes I'm aware and have actually read through this many years ago but it's just like you said, a reference/description manual (with some helpful hints along the way that are definitely appreciated!). It's well written though and I will keep it handy but it's no substitute for an actual "teacher" who can give practical examples.

re. User Interface Panels
Monark and the like are actually no quantum physics stuff but slick designs crafted by skilled people. The tech itself is quite simple and has been there since the early days. When you know how to stitch images with your graphic program of choice your're almost done. If there's demand I may make a tutorial for this covering the most important aspects. It has always been fun to skin ensembles.

I'm not talking about the images themselves or the UI design itself. I'm talking about this:



I want to learn how to separate the UI into it's own module and how those merged cables and info nodes work. I've never actually used those before in any of my own creations. I've only copy/pasted things and modified ensembles but never started anything myself from scratch as I don't fully understand how it all works. I need to learn that system.

The actual images and UI design itself is a whole other thing and that part I know how it works. It's the innards that I don't understand yet.

[EvilDragon]

In Core there is no event order, things happen kinda simultaneously on every clock tick. Core fixes a lot of confusing and unintuitive stuff from Primary.

[gentleclockdivider]

The thing with Reaktor that has been slightly troublesome over the decades is the way things are instanciated, meaning the way things like events are ordered depending on when you insert things into the structure.

No such thing in core , it's all happening at the same time ( or sort off ) , after all these years I still have wtf moments in core .
The latch module ( which is basically a write to mem , read from mem ) is probably the most important one to control your signal flow
And Evil Dragon beat me to it

[elassi]

I want to learn how to separate the UI into it's own module and how those merged cables and info nodes work.

There's no wizardry behind it. Panel objects are "primary-level" while core cells are ... erm ... core-level. You can't place primary-level objects inside core cells. That's why they are divided into two 'blocks' when looking at Monark's main structure.

If you'd replace Monark's core-level objects with primary-level ones, you could put them all into one macro or even work without a macro at all. But even then you'd want to separate them for the sake of organisation and structure to keep overview and don't get lost in a jungle of modules.

[gentleclockdivider]

Most monark controls are not your standard gui knobs and sliders , they are mouse areas etc..and multipic’s
There is some custom parameter smoothing going on , that’s why there are core cells .
To keep things nice and tidy the core and gui section is separated , as elassi explained .
And primary can’t live inside a core cell anyway

[elassi]

Most monark controls are not your standard gui knobs and sliders , they are mouse areas etc..and multipic’s

I wonder though why they used multipics for many controls (e.g. volume, cutoff, etc.). This isn't necessary as the controls (here: knobs) can contain their own image strips. However, there must be a reason for this, probably a resolution thing?

The mouse areas on the other hand help to design styled switches which obviously makes sense.