Expert Sleepers ES-8 + Reaktor Blocks + Ableton Live

Hi -

I am trying to set up the ES-8 within Ableton Live with Reaktor Blocks. My goal is to use Reaktor Blocks along with my hardware modular system.

I have been able to do this successfully outside of Ableton Live just with Reaktor.

However, once I try to do it within Ableton, I can’t figure out how to set it up. I am also having issues with using an Aggregate Device in Ableton (I also have a Presonus Studio 18/10 for my traditional audio interface). I know this is a routing question, so any assistance would be appreciated.

I was wondering if there are any tutorials or use cases to help me here.

Thank you!

Best,

Justin.

 

More specifically, my issues really have to do with the ins & outs within Reaktor.

In standalone mode, I am able to assign the Reaktor ins and outs appropriately to the ES-8 ins and outs via the "Audio & Midi Settings".

However, within Ableton, the "Audio & Midi Settings" option does not exist.

With regards to the aggregate device, I finally figured out which of the outs were the ES-8 ones, so I think I am good there.

Thank you!

 

Hi jlevine711

Did you ever find a fix for this?

I'm having the exact same issue routing CV from Reaktor plugin to the ES3. Works fine in standalone mode, but not when it's a plugin in Live.

Tested the Max 4 Live CV Tools and that sends CV to the ES3 no trouble. Just can't figure out how to do it with Reaktor plugin.

Hoping you worked it out and can help.

Cheers

 

Here's how I do it--
1. Load in Reaktor as an audio unit (it will be a midi track obviously)
2. Create a new audio track
3. On the Reaktor track, assign AUDIO TO to the audio track you created in step 2
4. On the Audio track from step 2, assign AUDIO FROM on the top selection to the Reaktor track.
5. On the bottom of the AUDIO FROM (same track) select the channels you will use to send whatever CV signal you will send to your module, ex, "3/4"
6. On the AUDIO TO portion of the same track, the top selection- choose EXT OUT, and on the bottom, the same channels you assigned for CV signals - "3/4"
7.Set the Audio unit reaktor track to AUTO in the monitoring setting. (not IN or OFF)
8. On the Reaktor Track, set the input to IN

In Reaktor - on the output section in patching mode, click the ADD button to add more outputs- don't use outputs 1 and 2 for anything, start by using 3 and 4, and keep adding outputs according to what signals you will send. Label those outputs so they match the ones on the audio tracks you created to not get confused

Continue to add audio tracks in Ableton following step 4 and on, and add them also in Reaktor by clicking ADD on the output section to create more outputs, and follow the same direction- from step 2 on.

To record your audio, use ANOTHER audio track, use EXT In on the AUDIO FROM section and choose the output from your module or wherever in your rack you are sending your module output to in the ES8/6, ex. ES8 inputs 1-4.

Important- before doing all this-- in Ableton's Audio Preferences, enable the number of inputs and outputs you will use and lablel them - this will keep you organized.

I added a few photos below to show this.

One more thing- on the Track Delay settings on the REAKTOR track, you may have to type a negative value in ms to compensate for latency. This depends on what latency settings you are using, and how many plug-ins you are using that may cause any additional latency. I usually send a clocked gate signal out of reaktor to a kick drum or some other short sound in the modular and record the audio onto a track, and see where on the timeline it is hitting. If it hits too far past the the grid, I'll dial the latency back a few milliseconds until it hits on the grid. It's trial and error.

Also, keep the volume of the Audio Track at 0 if you are using the pitch/cv out block. (or any block that you use for CV to your modular as moving that will change the overall values coming out of Reaktor and being sent to your modular).

Hope this helps! I had a time trying to figure this out, and this is the way it worked for me.

 

Labeling outputs

 

Thank you willieraylewis. I’ll try your workaround to see if this works.