Triggering Snap Changes in Reaktor
Reader Gherat writes:
I have extented the macro of the roux step/event sequencer with a snapshot macro.
The snapshot macro will switch between sequences on beats or triggers (like how ableton live switches between parts…), so it’s even better than using multiple Y tablerows (I used to use multiple Y rows as well but this is much better I think.. thanx..
Yup, I do something similar. Interested builders should check look in the factory ensembles under new additions / sequencers and load the “Snapper Macros” ensemble. That example will show you how to use the Snapper instrument to change snaps in a slave instrument in a synchronized manner.
Of course there’s more than one way to do this – my usual way is to put slave instruments inside a master instrument that has a custom “scene master” macro that looks like this:
This allows me to manually trigger master snapshots, or scenes, using the computer keyboard. MIDI keyboard notes will also work.
Before I go into more detail on the subject, and on my own setup, I’d like to ask readers how they deal with snap changes in Reaktor for live sets or live improv – are you using the Snapper macro? Do you have your own solution? Are you interested in automated changes, or do you prefer to do it manually with your own sense of timing? And finally – are Reaktorists who have Kore 2 using Kore performance presets to change Reaktor settings, bypassing the snapshot system entirely?
information
forums
subscribe
links
11 Comments
Leave a Commentandy t
how do you map a knob from a user page to a knob on another user page? i am following the manual and it just ain’t working. the assign button stops blinking after i click …”assign”… (assign stops blinking)…. no worky! help! i am using kore 2 in standalone mode.
the idea is to make a custom macro page of regularly used knobs instead of spelunking all over kore creation in a live situation.
November 8, 2008 @ 11:06 am
Peter Dines
Andy T, spelunk no more.
November 8, 2008 @ 4:45 pm
andy t
you are the man, Peter D, muchas gracias amigo
November 8, 2008 @ 5:40 pm
gherat
I like to built switches that switch between random/automated pattern switching or switching by hand but synced to beat/bar/2 bars/4 bars ect..
However that thing that I’d built where I said it didn’t had any hickups.. I’m beginning to think there are hickups!
It looks like the CPU dives to 0 for a moment and sometimes you can hear it to in the triggered sounds.. Like a small stutter or something.. What’s up with that?! A bug or something?
November 9, 2008 @ 1:10 pm
Peter Dines
Gherat, thanks for sharing the macro!
Two small problems – number one, you’re using switches. They always cause a global reset event in Reaktor, so most builders avoid them nowadays, except as a means to shut off CPU hungry parts of the ensemble. Try a list module to hold values, or a selector / scanner.
Number two, there used to be a problem with automated snap changes causing a mild CPU spike. I see you’re using sync pulse modules for the synchronization, which I hadn’t tried, so let me tinker a bit with your macro before I say any more… cheers!
Andy T – glad I could help!
November 9, 2008 @ 1:35 pm
gherat
Allright I see/hear the problem..
When I uploaded the first version where I said it worked liked a charm I did not use a switch at first but a simple knob..
I later replaced that knob by a switch because of the cool +- buttons and updated the file on the server! I now replaced the switch again for a normal knob and the hickups are gone now!
Thanks a lot for the “do not use switches” tip! They should say that in the manual!
PS I replaced/updated the file in the download location with the working macro now over here (that’s the same location as the other links I posted so they are good now as well..)
Thanks again..
November 9, 2008 @ 3:19 pm
gherat
I’m way to fast with my solutions haha, I see list items have those cool +- (change style to spin) as well! That way you can press + to go to the next snapshot and – to go back..
For people like me there should be an update button on the comments boxes haha!
November 9, 2008 @ 3:35 pm
Native Instruments Kore, Komplete, Reaktor @ Create Digital Music » Serendipity: Sound Variations and Happily Unintended Consequences
[...] I began writing this post to discuss Kore 2’s performance preset system. If you’re not familiar with this, the quick lowdown is: you can store banks of settings and change between them, or automate changing between them, in a master performance. I touched on this in my last post about Reaktor. [...]
November 19, 2008 @ 12:17 am
andyt
i was trying to automate sound variation jumps by pressing the buttons on the kore controller in ableton live. But, live doesn’t record the automation of the button presses. So I can map midi notes to trigger empty live clips that send program changes to kore presets, one preset saved for each of the 8 sound variations.
So now i want the kore controller to send the midi notes to live to trigger the clips that send program change messages to kore so that the presets are activated that enable each sound variation.
How would one, (after trying to understand why anyone would want to do this), utilize the reaktor toolpack to get kore’s buttons to send midi notes? I shall try tommorrow and report results after recording a very, sadly, non-digital recital at my school.
November 19, 2008 @ 10:01 pm
andy t
two weeks later…actually you can do this, after the following steps are completed: in live, create a midi track, add kore, add the reaktor toolpack midix8 koresound, add the reaktor enseble midix8 from the toolpack, configure the buttons to send midi notes, enable plugin midi output, create a second midi track in live, get the midi notes from track one via the kore2 plugin output from track one and send it to a virtual midi cable like maple, midi yoke, hubi’s midi loopback, etc, then create another midi channel in live, assign the virtual midi cable to send note through it’s out and to catch remote in it’s input, create 8 live clips in ableton on this midi channel, assign the clips to send program changes 1-8 respectively, map the incoming midi to the live clips in ableton with midi mapping, create another midi channel in live, get the midi program change data from the clips into an instance of kore on that channel, setup 8 different sound variations, click each variation and create a performance preset for each, check the box for program change to catch the program changes from the live clips in the previous channel, hit play on one of the clips. Now, your kore page on the first kore instance’s buttons trigger the sound variations via performance presets on the second kore instance). The key here is that ableton catches the button presses now for recording the automation. Easy, right? :0)
December 5, 2008 @ 10:57 pm
Peter Dines
Andy: yikes! I’m going to have to fire up Live myself and try that out. That’s a heck of a workaround – thanks for piecing it together for us!
December 6, 2008 @ 3:08 pm
Leave a comment
RSS feed for comments on this post. TrackBack URI