trig delay block?

Hi, I´m very close to making a purchase of Reaktor and machine. I wonder if there is a building block that can be used as a trig delay? like on a hardware modular system. And do building blocks have midi learn function?
Thank you
Peppe

 

It depends what you mean by 'building block'.

If you are talking about Blocks, the answer is yes to both.

 

Panel elements has midi learn functions. Building blocks are part of the structure.

 

That's good to hear! I´m going from 20 years with modular systems, and feel this is pretty close to what I´m doing all this time. I´m asking because I´m planning my first ensemble, building 16 separate voices and sequence them from a step sequencer module, and setting up a midi controller where I can delay trigs to archive grooves. Right now I´m reading how to archive as fast clicky sounds as possible. I would like to use trig itself if it´s possible but not only. Fast envelopes are of course also welcome. A pop a click sound ensemble will be my first goal.

 

Hi Peppe, Do you mean an audio delay effect that can have its delay time synchronised to an input clock trigger, or a module that delays triggers?
both are possible, but it would probably be overkill to use an audio delay in the second case, and I'm not sure that there is a dedicated trigger delay module amongst the Factory block - simple to build one though, and there is likely something amongst the many third part blocks that are available.

16 full voices in Reaktor Blocks might be a stretch unless you have a very fast modern system. It really depends on which Blocks you are using and how complex the voices are.
Clicky stuff is definitely possible, Envelopes can be stupid fast, and when you do get the urge, building your own stuff is MUCH easier if you are actively exploring the glitchy noises and 'problems' that many developers spend years learning how to avoid or remove

 

No not a audio delay a trig delay of course..yes my first mission, sketch in my head, is to build a rhythmic click endamble.16 voices is overkill mabey. Im spoiled with big modulars. But can start with four and make modulations. But then rythmics wont be as complexed as if I can set startpoints for individual voices. Or is there ways to put trig delays and combainers after the stepseq. Module? Im not after creating infernos, just like to be in full charge over trigs. Think African rythms. Thanks for your thought thru answer.

 

With Reaktor, there is always 'a way', but some things will require a lot more work than other things. Really just whether someone has already built a module or a block for that purpose, or whether you need to do some building yourself, of patch up something from multiple Blocks.
Remember also that 'building' is programming, but all by connecting modules together with wires, so very much like creating a modular patch.

It would be no problem for an experienced builder to build an ensemble from scratch with 16 or 32 or more voices to produce complex rhythms from delayed triggers, but building that from Blocks might be more difficult... its all possible though

e.g. the factory ADSR as individual gate outputs for each stage, so if attack is set to 30ms, then the decay gate is delayed by 30ms with respect to the input gate, but that would not work with a trigger as input, only a gate, but the 8step sequencer has a controllable gate ratio, and takes trigger inputs... and there's a gates & trigs module that has some processing options... so there are lots of possibilities...

Just checked and there is a specialised 'gate delay' Block in one of the 3rd party Blocks collections in the User Library... so

 

"It would be no problem for an experienced builder to build an ensemble from scratch with 16 or 32 or more voices to produce complex rhythms from delayed triggers, but building that from Blocks might be more difficult... its all possible though"

How do you mean? what would an "experienced builder" build it with if not blocks?

e.g. the factory ADSR as individual gate outputs for each stage
this is really cool! so I can set up trig delays after each stage and control the timing with a midi controller for example?
Do gates work the same way as trigs in Reaktor or is there any converter module, sorry blocks?
In the modular world, there are many types of converters, for example, you can convert modulation data to trigs (function generators.), so you can for example take pitch data and trig new voices accordingly to pitches in a melody.

Can I run two ensembles simultaneously? so I can use hardware faders to fade between two or more ensembles? Or must I copy-paste blocks from one ensemble to the other and set up a mixer to achieve this? I think of ensembles as patches in the modular world.
I´m looking for the right midi controller for me to use with Reaktor. I will also get a Machine for an easy way to sequence sounds I made in max. I REALLY tried to get friends with max/MSP but it never happened. Buiding cool sounds are fine but sequencing them is tough work. A very unmusical interface made for mathematicians if you ask me.
How do Machine and Reaktor play along?

Just checked and there is a specialised 'gate delay' Block in one of the 3rd party Blocks collections in the User Library... so

I´m going there right now to DL it!!
are there any online resources for reading about blocks? I thought I start with reading about the ones that are included in the application and take notes in word in Word about the ones that I can use in the click & snap ensemble I will start with

Sorry for all these questions, I´m after a kickstart and want to start making music right away. Just take your time and answer all this when you have time!

 

I have been up reading all night. And now understand that I will work on the structure level with modules and macros first, that where the action is. Then save it as an instrument. Make more of them and save it all as an ensemble.
For the last couple of hours, I been looking for a clever way to record midi from a controller within a set timeframe but have not found any concrete.
There must be a module for this right?


I'm getting this one. I can mute and set the volume on 8 voices and fade between two instruments and have 8 Gridless push encoders for my
disposal Faderfox UC4 – Thomann UK

 

But I just read I can easily do it in Ableton. But it would be nice to be able to record midi within Reaktor so that s a part of a macro. Then when setting together macros to an instrument and ensemble, there will be the ability to make polyrhythmic stuff with modulations if I record different lengths of midi data/knob and fader/mute actions of each macro Endless of possibilities

 

If you want to make music straight away, I'd consider looking into Blocks first. Building your own stuff from scratch is a great & laudable thing to do, but it might be a little while before you're making anything more complex than a basic subtractive synth.

(Although I suppose the sooner you start learning about building, the sooner you get exactly what you want...)

I should also point you towards this dedicated trigger delay: here

 

thanks for your advice but I don´t mind sitting and scratching my head for a couple of months. I now exactly the patches/instruments I want to do and it will take some time for sure. And I will be a daily visitor on this forum. I hope you guys won't get tired of me
But the one thing does not have to exclude the other, I can do simpler things too.

wow thanks for the link!
I will start with making a library of voices, sounds I like. Then start sequencing them. I will search thru the user lib for interesting modules for this. And find out how to make simple stuff in sequencing like strums, and then modulate them.
But have to wait for two weeks to buy Reaktor. I get money then.

 

Sounds like you are going into it with your eyes open, which is the main thing. And who knows, you might well be a natural

 

You can record MIDI in Reaktor in it's raw form as a serialised stream of monophonic MIDI events using a Channel Message module. In this case when you read it back you will have to 'manually' process those midi messages. Or you can take advantage or Reaktors built in separate pitch and gate midi input modules, giving you more meaningful note and timing data that you can manipulate, store and recall however you like.
You can store even data like pitches and gates into Event Tables, or into arrays if you're working in core.
(There's an extra step with core if you want to be able to recall recorded data at a later time - you need to set up a snap value array and manage loading dn saving to and from the core array, which is a PITA, and we were promised extensions to the Table Framework years ago which should have made this a whole lot easier...)

It's up to the builder how to manage this kind of process - you could just store events per 16th note and use up a lot of memory very quickly... or store event/timestamp pairs, or whatever. That's part of the skill of programming - working out which compromises to make.

There are probably lots of different things in the User library that will store and recall note and /or controller data in various ways.