Drum Trigger in SD2.0

[urobolus]

Good evening, so I am finally getting to spend more time with the MegaDrum 32 I bought around June/July. I could never get things to work quite right, and since I got the the 20130901 firmware to update yesterday, some things work better and some worse. On to the specifics...

I am running MD from MDM and triggering Superior Drummer 2.3. Thus, I have been following this link mostly, but have deviated slightly on some things:

http://www.megadrum.info/wiki/index.php ... orDrummer2

I have been consulting the forums, which are very helpful, but haven't been able to resolve this current issue. Here are the pads I am currently working with (the problem ones are in red):

Kick (Channel 1) - CKV Pintech: was alternating between 36 and 0 yesterday, but seems good today.
Snare (channel 4/5) - 14" Dual Zone Pintech: works fine
Tom1 (Aux2 channel 20/21) - 8" Dual-Zone Pintech ConcertCast: works fine
Tom2 (Channel 10/11) - 10" Dual-Zone Pintech ConcertCast: is setup to trigger 79 & 80 in SD; but all zones trigger 7 in SD. MIDI log shows it is sending 79 & 80. (Fig. 1)
Tom3 (Channel 12/13) - 10" Dual-Zone Pintech ConcertCast: is setup to trigger 77 & 78 in SD; but 78 (rim) is triggering 7 in SD too. MIDI log shows it is sending 77 & 78. Every time the pad was struck in center it would alternate between 77 and 0. Can't reproduce this right now. (Fig. 2)
Tom4 (Channel 14/15) - 12" Dual-Zone Pintech ConcertCast: hot, but works fine
Tom4 (Channel 16/17) - 12" Dual-Zone Pintech ConcertCast: hot, but works fine
HiHat (Channel 2/3) - 13" Pintech Visulite Dual Zone and Bell: is setup to trigger 19, 18, & 20 in SD; but 19 triggers 47 and 20 triggers 43.(Fig. 3)

No pads are currently setup to send notes 7, 43, or 47, so doesn't seem like vibration is causing another pad to trigger.

I have verified the cords are going where they should. Before the update, the hihat was working (somewhat) under the same settings. I haven't changed anything since then.

Thanks in advance for the help!

[dmitri]

I moved it to "Related Software" since it looks to me to be an SD configuration issue.

[urobolus]

Ok, thanks! Any ideas on what could be causing this? Not too strong with MIDI, but I can poke around in SD when I get home and see why it would changing the message cent.

[airflamesred]

Clearly, you'll need to the high level settings in MD.

[urobolus]

Actually, disregard. Started a new SD project and the problem went away. Now to get this hihat working. Only playing open notes.

[urobolus]

Hi, so I started making a new kit using the Metal Foundry library and I'm running into some of the same problems. Starting a kit from scratch doesn't seem to be helping as it did with NY Avatar.

I have the hihat on notes 18, 19, and 20, but when I play the hihat, it is playing Tom2; Tom2 is playing the hihat. Verified MD is receiving the correct, but in SD2, it is receiving the notes for the tom. I haven't changed anything as far as inputs since I made the Avatar kit, which was working OK... until every pad started triggering Tom4 faintly, and Tom2 started alternating between Tom2 and Crash1, for some reason.

You can see the pictures I posted above as they are relevant to the problem.

I also have the latest firmware installed.

[urobolus]

Any suggestions? Maybe I just need to remap in SD. Still would like to know why the notes are off in SD.

[airflamesred]

Once again, you need to set the high level.

[urobolus]

Adjusting the HighLevel isn't doing anything for why my hihat is playing Tom2, Tom2 is playing the hihat. Again, both a properly configured and verified, but it is playing this way in SD.

[G-Man]

What about if you map your Megadrum in Megadrum Manager to match the notes in Superior Drummer and nkt the other way round? I have almost finished my megadrum and intended on using Superior Drummer myself so if I find anything out I will post it here. Should be done this weekend.