Need a Tutor for Reaktor 6 -to build complex sample/granular instruments with GUI's

Thanks for those tips. Also that series you posted is awesome. I'd never messed with Reaktor up until I saw some people asking about it here. I'm having flashbacks of LabView VI's.

Check this thread (search the forum for this sort of thing ;))

I posted an example with two simple scope examples, one using the scope module, the other using XY module in scope mode.

Best of all (but most challenging) is rolling your own using a Multi-display - like the factory block and the factory scope - look here:

I'm gonna have to do some nit-picking here ;)

You have to start with Primary, because it is essential, you can't do anything in Reaktor without accessing the Primary layer. It's not easier, it's just there, so it becomes familiar more quickly.

Core is different. It is simpler, and way more coherent then Primary. Folk often get the impression that it is more difficult or more 'mathematical', but that is a side effect of it being simpler and more coherent. experienced builders do easy stuff in Primary because it's just more convenient, but as soon as what they are trying to achieve gets tricky - like DSP math, or 'proper' programming - folk turn to core, because it's easier in core. All that fancy advanced stuff done in core gives the impression to newbies, and non core folk, that core is super hard and you have to be a math wizard etc., but that is more a side effect of the power and simplicity of core.

The other problem is that Primary is essential, so everyone learns primary first. Unfortunately, core is different (as we have established), and if you just learned a whole lot of new ways of thinking about problems to use Primary, it's easy to fall into the trap of trying to crowbar those methods into core... which doesn't really work, core will just continue to seem obscure and difficult if you keep trying to do Primary style development in core.

Blocks isn't really a Reaktor development layer, it's a specification framework. If you wanted to you could make Blocks using Reaktor 5 (without the patch and play obviously). You couldn't recreate the core layer in Reaktor4 though ;). Blocks are built using Reaktor, rather than being part of Reaktor...

The real new thing was Racks, and that's a higher level paradigm to improve DAW integration rather than a programming layer. You can't develop a Block for racks that won't work in an ensemble.

I'd be more inclined to classify Blocks along with the ZDF framework, the envelope toolkit and the partials framework. Although they don't really fit well there either!

Blocks isn't the only one either, herw (a once prolific member here) developed a very powerful modular framework in Reaktor, it just didn't catch on the way blocks did for a whole bunch of reasons. Anyone can have a go at their own framework, or create extensions to Blocks (I developed an extension for polyphonic Blocks that works seamlessly with the existing framework - its used in some of the toybox packs)

Patch and play confuses this viewpoint, but it also explains why patch and play is somewhat clunky and seems like it could be way better if it was done differently... that's because it was kind of a hack bolted onto something that is really just a framework specification... so we can't self patch Blocks, there is no transparency of cables, cable colours only work in rack mode, there are graphical patch cable glitches, it's a total hassle for builders to set them up within the existing GUI building environment... etc.

So, nit-picking done... carry on :)