Chaser,
Thank you for the comprehensive reply. I tested the MIDI coming from the Nitro module using MIDI Monitor, and it appears the module is simply not passing trigger data. I can see clock info coming through, and other buttons on the module create a response in MIDI Monitor, but hitting the pads or striking the drum buttons on the module don't send anything. It would appear the module may be faulty. This is unfortunate, since I am living in Peru (I'm from Northern Califorina) and shipping it back to Alesis is unrealistic. Luckily, I have a different module coming in a couple of weeks, and I anticipate it won't have the same problem.
George
Sorry to hear that..this module/design has been around for over 10 years (
Medeli DD512) , just licensed/rebranded.
Medeli modules usually have a internal test mode , unfortunately I don't have one of these modules or the key/pad combinations for it as I do for the others
DD650..(Command/Crimson/IIDM10 MKII Studio/Forge) and the DD680 (DM10 MKII Pro)
Drum modules are basically TMI (Trigger to MIDI Interfaces) and Local Control is for selecting where to send the MIDI..ON=Internal Sound Generator..OFF = External.
However I have found that Medeli modules (all the ones I have..DD650..DD680..STRIKE..) will still send MIDI out even if Local Control is set to OFF.
Do the Internal sounds still play?..have you checked MIDI output with Local Control ON?...just curious if it's a firmware or hardware issue.
Another way to test the MIDI signal is setup a MIDI loop...connect a 5 PIN MIDI cable to the MIDI IN and MIDI OUT ports on the module and to set LOCAL CONTROL=OFF.. GM MODE ON..The module should now be sending MIDI out and receiving MIDI and triggering the GM Bank/Section (AKA Percussion Section) of the module.
The GM Kits/Backing Instruments etc are listed in the DD512 manual starting on page 32.
If you set LOCAL CONTROL= ON..GM MODE ON..both Internal sections (Digital Drums and GM) will trigger simultaneously.
EDIT:Added Medeli manual links