I’m frustrated

DM10 to Midi then amp instead of directly to Amp?

I'm getting a lot of audio loss from various triggers, particularly with cymbals and kick but I also get a lot of kick distortion from time to time, especially when there are a lot of quick Tom/Kick combos I'm doing.
I'm wondering if it makes more sense to use some kind of Midi audio interface from the Midi out to drive the sound rather than trying to drive sound through the DM10 module directly to the Amp.

Does this make sense?

If so, what midi audio interface would you recommend?
1 person has
this question
  • Hello,

    Thanks for posting. 

    Let's try out the steps below to help you out with crosstalk. 

    Optimizing Crosstalk Settings 
    First, disable write protection so that you can save your changes: 
    To turn write protection off: 
    1. Press UTILITY. 
    2. Press SYS (F4). 
    3. Press O/S (F3). 
    4. Press MEM (F4). 
    5. Press VALUE DOWN or move the VALUE DIAL counterclockwise until the "WriteProt" field says "OFF." 
    6. Press DRUM KIT to return to the main page. 

    Every time you strike a pad, the whole kit vibrates. Vibrations travel through the kit rack and can sometimes trigger other pads. This tendency is known as ‘crosstalk’, and due to the physical nature of drums, it is unavoidable (even on an acoustic kit). The DM10 Module comes prepared with a “Crosstalk” (or ‘Xtalk’) setting. A more accurate description of this setting would be “Crosstalk compensation”, as there really isn’t a way to prevent the physical tendency for vibrations to travel. This setting, however, uses an algorithm to separate intentional hits, from unintentional crosstalk triggers; the result, when tweaked correctly, is that you only hear sounds you want to hear. 

    1. Press “Ext. Trig” 
    2. On top of the screen, rotate the value wheel to select the trigger you’d like to adjust 
    3. Press ‘F2’ for ‘Trig’ 
    4. You’ll notice three ‘Xtalk’ settings: ‘Xtalk Send’, ‘Xtalk Receive’, and ‘ZoneXtalk’. ‘Xtalk Send’ describes the trigger’s tendency to cause adjacent pads to trigger when struck. ‘Xtalk Receive’ describes the trigger’s tendency to be triggered when an adjacent pad is struck. Lastly, ‘ZoneXTalk’ affects how likely a dual zone trigger is to cause crosstalk upon itself. For example, a Ride Bell and Ride Bow. 
    5. Here’s where things get tricky. Each of these settings can be adjusted from 1-7. Since the setting is really ‘Crosstalk Compensation’, the higher the value, the less likely the pad is to send or receive Crosstalk. Here’s the catch: It may be tempting to simply turn it all the way up. But remember that the DM10 is using a smart algorithm to try to ‘weed out’ crosstalk from intentional hits. If you turn it all the way up, you may find that it mistakenly mutes some of your strikes, writing them off as crosstalk. Try to find a balance (ideally somewhere in the middle) with any problem pads, as well as their surrounding pads that are sending crosstalk. 
    6. Don’t forget to press the ‘store’ key to save your settings each time you make a change!
    • I've been conservatively adjusting these "Crosstalk" settings since I got the kit back in June (2017), but also adjusting "Sensitivity", "Threshold" and "Retrigger", using trial and error to get the best outcome possible. The settings I have now seem optimal when playing somewhat simple sets but when things get complex, thats when I experience the issues.

      For example, when bringing my Crash-1 to a swell with a slow roll stroke, the audio cuts out multiple times making it sound like a reverse crash, particularly with heavier strokes. Its as though the electronics aren't able to keep up with the trigger request/demand.

      Using the example of the Crash, here are the settings I currently have:
      XTalk Recv: 00
      XTalk Send: 02
      ReTrigger: 00
      Threshold: 09

      Whenever I feel I am experiencing a Crosstalk issues between multiple triggers, I'll go into these settings under the "TRIG" tab and select the trigger that is being offended and watch the indicator in the top right corner of the window to determine if I'm experiencing Crosstalk from another trigger. If I do, then I adjust one or many of the above settings (from both the receiving and offending triggers) until the Crosstalk goes away. I may also go into the "INP" tab and adjust "Sensitivity" (currently at 99 for this Crash trigger) as needed too but I don't usually adjust this very often.

      I've also adjusted the "VelCurve" under the "CURV" tab in order to adjust how the trigger responds to increased pressure or stick control/sensitivity. This is particularly important to me on the ride, high hat and crash cymbals. I also have a sensitive snare setting because I use the snare in various ways.

      I've done this with all of my triggers, taking each one and adjusting as conservatively as possible to ensure I get the most optimal responses, little to no Crosstalk and appropriate sensitivity for how I use them.

      The main reason I'm asking about using a Midi out is because I mostly hear this when I output to my Simmons DA50 drum amp going from the Main Out to the Drum Inputs (both L & R) on the amp, not as much in the headphones. It almost seems as though I'm trying to overdrive the output to the Amp but not sure if thats what is really happening. In my limited experience with these (but 35 years experience in computer tech), I was thinking if I moved the output from analog to Midi and digital Midi to another processor more qualified to reproduce the quality output required prior to amplification, then I might be able to get the best audio result.

      As an example, I was considering the Alesis Multimix 4 USB FX | 4-Channel Mixer to go between the DM10X and the Simmons DA50.

      [DM10 X Module] ==(midi)==> [Multimix 4] ==(analog)==> [DA50 Amp]

      Is this making any sense??

    • One more question - would it make sense to replace the cables with a higher grade, balanced, heavier shielded cable?
  • (some HTML allowed)
    How does this make you feel?
    Add Image

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited