How do I get Reaktor 6 to respond to my MIDI keyboard in Reaper?

skroobler · 2025-04-12T02:01:56+00:00

There was an error rendering this rich post.

I just bought the full version today, and I load it as a VSTi in Reaper (Windows 11 Pro). With the track armed, it shows MIDI is being received on the track, and the MIDI light even comes on in the Reaktor GUI, but I can't get it to actually respond to the MIDI signal and put out sound. Sound is coming out of every other plugin I use, including Analog Lab V, Serum 2, Pigments, etc. so I know the keyboard is working properly and such.

Find more posts tagged with

Accepted answers

Sunborn

https://community.native-instruments.com/discussion/comment/221314#Comment_221314

Your entire ensemble is at "Omni" but the actual instrument is still on Channel 1, by default.

Maybe this is causing the problem? Try change that to Omni too.

I have tested in Cubase 14 and works without problem.

I also noticed some differences (for example i don't have that "Borgie" snapshot that i see in your screenshot). Maybe you are using an older version (i have version 2.0)?

Important!: I also noticed that some snapshots (usually Sequencer-related) do not produce any sound, unless you push "Play" button first (in Reaktor). Maybe you use one of those?

skroobler

Well yep, that's exactly what it was! Thanks for the help, folks!

All comments

Sunborn

https://community.native-instruments.com/discussion/44354/how-do-i-get-reaktor-6-to-respond-to-my-midi-keyboard-in-reaper

Hello,

Almost all Reaktor ensembles are mapped to Midi Channel 1.
So when load them in your DAW you also have to use the same Midi channel on the selected track.

You can change this on each ensemble separately, by going on ensemble's "Connect" tab and change it to any other Midi channel you wish and then save the ensemble. In most cases, you can use the "Omni" option (all channels).

skroobler

Thank you for the response! This is the one I'm currently trying to play, and it appears it's already set to Omni.

PoorFellow

https://community.native-instruments.com/discussion/comment/221258#Comment_221258

Have you tried setting up Audio and Midi in the Reaktor 6 stand alone app ? ; File : Audio and Midi settings ? You most likely want to use same audio as for your DAW ? Always setup first in N.I. stand alone version first and always check if stand alone version works if you have any problems.

skroobler

This is what I have in the MIDI settings. I know the audio is working, because I can create a self-generating patch and it will put out sound, it just won't respond to any MIDI input.

PoorFellow

https://community.native-instruments.com/discussion/comment/221268#Comment_221268

I know the audio is working, because I can create a self-generating patch and it will put out sound

I don't know what "create a self-generating patch" is , and I am very far from being an expert in anything Reaktor , but my suggestion that you should also check the audio settings remains.

Also you haven't told if it works in standalone Reaktor

The Aralsk 7 worked immediately for me using my Reaktor 6 plugin , I have tried three different DAWs and a plugin host , and it works for me immediately.

skroobler

Sorry, I just mean that if I do something like this, it puts out sound, but still doesn't respond to MIDI in any way.

And that's the same in both standalone and the DAW.

skroobler

Update: When I change the channel on that simple patch to omni, I'm able to change the pitch via MIDI, but I can't get any ensembles to respond to MIDI on omni or otherwise, standalone or DAW.

PoorFellow

https://community.native-instruments.com/discussion/comment/221286#Comment_221286

I think that this is a Reaper problem. I just tried to install Reaper and could not even get Reaktor 6 to respond to the Reaper Virtual Midi keyboard , I tried several times and with Kontakt also , then after having played around with audio and Midi settings and adding a loop back midi in Reaper and closing and opening the damn Reaper a couple of times then it suddenly decided to respond to the Virtual Midi Keyboard.

I have no idea why Reaper acts this way , maybe it has to do with that Reaktor is both an instrument and a FX I think , but I added it exactly the same way as an instrument every time..

skroobler

Thanks for the help! I'll give it a shot in Bitwig in a bit when I have a smoothie in me.

PoorFellow

https://community.native-instruments.com/discussion/comment/221295#Comment_221295

Good luck , if you want to try another cheap and rather simple DAW then try the Mixcraft trial , Reaktor 6 worked immediately for me on that one.

skroobler

I really like Reaper, and Reaktor is the only plugin behaving this way, so if I can get it to work in Bitwig, I'll just kinda consider it a "Bitwig plugin" for my purposes and keep fiddlin'

PoorFellow

https://community.native-instruments.com/discussion/comment/221302#Comment_221302

Try adding the loop-back as I did.. That's all I did besides checking Midi and audio and opening and closing Reaper and Reaktor standalone. I never selected the loop back or anything in Midi after adding , though I think that it turned on itself in Reaper

skroobler

Okay, I'll give that a shot!

Sunborn

https://community.native-instruments.com/discussion/comment/221314#Comment_221314

Your entire ensemble is at "Omni" but the actual instrument is still on Channel 1, by default.

Maybe this is causing the problem? Try change that to Omni too.

I have tested in Cubase 14 and works without problem.

I also noticed some differences (for example i don't have that "Borgie" snapshot that i see in your screenshot). Maybe you are using an older version (i have version 2.0)?

Important!: I also noticed that some snapshots (usually Sequencer-related) do not produce any sound, unless you push "Play" button first (in Reaktor). Maybe you use one of those?

skroobler

Well yep, that's exactly what it was! Thanks for the help, folks!

Quick links

Unanswered questions