Reason's NNXT and Midi Drum Controller...Doesn't work
-
- KVRist
- 256 posts since 23 May, 2006
Has anyone here tried using a midi drum controller with the NNXT in Reason? I've tried this on several occasions over the last couple of years, and I recently picked up the first version of Reason Drum Kits and wanted to give it a go...and I just don't get it. It triggers everything fine in Cubase with other samplers, but for whatever reason (pun intended) it triggers sounds at random within Reason (even Rewired via Cubase). If I were to hit a pad 10 times, maybe 4 of the hits would trigger a sound. Does anyone have any experience with this? I've read a few threads around the internet with no solution, using different controllers. Any help would be appreciated.
I've seen no mention of this problem on the Propellerheads site, naturally.
I've seen no mention of this problem on the Propellerheads site, naturally.
-
- KVRAF
- 1884 posts since 9 Feb, 2004 from Rochester, MN
-
- KVRist
- Topic Starter
- 256 posts since 23 May, 2006
Yeah... my keyboard controller works fine. The drum controller triggers perfectly fine just not with the NNXT for some reason. The green light comes on everytime I hit the pad, but it will only actually trigger the sounds at random. I'm by no means a "newbie" this is just an old problem that I'm determined to sort out.
- KVRAF
- 2818 posts since 30 Aug, 2001 from where dinosaurs are still alive
used rdk with a v-drum all this year and never had this problem.loveless wrote:Yeah... my keyboard controller works fine. The drum controller triggers perfectly fine just not with the NNXT for some reason. The green light comes on everytime I hit the pad, but it will only actually trigger the sounds at random. I'm by no means a "newbie" this is just an old problem that I'm determined to sort out.
try some midi monitoring to see if you're shooting out some unwanted/unneeded cc.
-
Black Box Recorder Black Box Recorder https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=53881
- KVRist
- 101 posts since 5 Jan, 2005
Check the velocity range for the sample. It may be at a limited velocity range (say 75-100) and anything above or below this range may not "trigger" the NN-XT (a velocity setting of 65 or 107 wouldn't trigger the note). In other words, it's receiving the signal but ignoring it because it falls out of the velocity parameters assigned to that sample.
The RDK drum kits sample are very fined tuned in this manner. Certain samples are only triggered in a very small velocity range. This allows for a more natural sounding drums as you never hit a drum with the same velocity twice (or rarely anyways).
That would be my first guess. Otherwise make sure your drum pad is set appropriately for the drum kit you are suing. For example if the drum sample is set to C3 make sure the drum pad isn't set to trigger D1 (I'm assume ing you already tried this but you never know….).
The RDK drum kits sample are very fined tuned in this manner. Certain samples are only triggered in a very small velocity range. This allows for a more natural sounding drums as you never hit a drum with the same velocity twice (or rarely anyways).
That would be my first guess. Otherwise make sure your drum pad is set appropriately for the drum kit you are suing. For example if the drum sample is set to C3 make sure the drum pad isn't set to trigger D1 (I'm assume ing you already tried this but you never know….).
-
- KVRer
- 13 posts since 26 Apr, 2006
I've used a Roland TD-6 with NN-XT and had no problems at all. You can check which sample is triggered if you go into edit mode in NN-XT and choose "select keyzone from incoming midi" (or whatever the button is labeled). Then play the drums and watch what's going on.
-
- KVRer
- 3 posts since 6 Sep, 2006
Did you ever find out what the problem was with triggering NNXT? I am having the same issue. I have an Alesis DM5 running to a MOTU Express XT into a powerbook G4. Everything else in Reason triggers fine. I have spent tons of time trying to figure this out. The sequencer records the triggers fine, and even plays them back fine, but it won't play the samples while i play the triggers. So frustrating!
-
- KVRer
- 3 posts since 6 Sep, 2006
It's definitley not cc messaging errors. I did a test and the only thing my computer is receiving is a note on message with 2 values... a note value and a velocity value. Yet the NNXT is still not responding properly. Crappy software!
-
- KVRist
- Topic Starter
- 256 posts since 23 May, 2006
I was wondering about that, actually. Do you think the NNXT has to receive a Note OFF message in order to trigger? This was my original assumption when I encountered the problem. I mean, I don't really understand -why- if that's the case - but, just... positing that.
- KVRAF
- 2818 posts since 30 Aug, 2001 from where dinosaurs are still alive
one flashback: I once made a setup to jam with a friend on guitar.
my td-10 going into rewired Reason with rdk1 (first months after the release), his guitar going in an audio in. Traction was the rewire master.
I was sure to have all working fine, but when pounding on pads, only few hits came out, just like Reason was ignoring 70% of the hits below a certain velo range, that ruined the day.
I'm sure it was reason2.5 with rdk1, the ekit is the same I have now.
never happened again, though. and I triggered Reason devices with ekit, handsonic, guitarsynths & grooveboxes. all with all kinds of weird cc behaviors.
I'm getting convinced there's something wrong, but hell, dunno what.
my td-10 going into rewired Reason with rdk1 (first months after the release), his guitar going in an audio in. Traction was the rewire master.
I was sure to have all working fine, but when pounding on pads, only few hits came out, just like Reason was ignoring 70% of the hits below a certain velo range, that ruined the day.
I'm sure it was reason2.5 with rdk1, the ekit is the same I have now.
never happened again, though. and I triggered Reason devices with ekit, handsonic, guitarsynths & grooveboxes. all with all kinds of weird cc behaviors.
I'm getting convinced there's something wrong, but hell, dunno what.
-
- KVRist
- Topic Starter
- 256 posts since 23 May, 2006
You'd think that this bug would've been brought to their attention some time ago! If I could only figure out WHAT the bug is. I've searched extensively and only found one or two other mentions on the net about this problem. It's really frustrating for the handful of us out there who are experiencing this problem.

