Well, it turns out that the DM10 has very similar internal workings as the Trigger I/O. Let's first look at the "X-Talk".
Even though there is a "Zone talk" setting in the DM10, you still can not fire off adjacent zones (i.e. dual zone on a signal input). At first I did not think this was an issue on the DM10 (meaning I didn't notice it at first) and even though you have to be more accurate with the DM10 than the Trigger I/O it is still there. Is it really a problem? I don't think so. That's because it is only an issue for those who want to use a VST with
eTrigger to get position sensing. Even with that said, I still don't think it is much of an issue because of the extra inputs the DM10 has. Just spilt one of the extra inputs.
The other similarity to the Trigger I/O is the fixed piezo/switch input. The crash input on the DM10 is a fixed piezo/switch input just like the Trigger I/O's input #4 (ride). The difference is, the switch zone on the DM10 can only be used as a choke switch. Since we are on the topic of switch zones, the DM10 (like the Trigger I/O) does not have any velocity when using that switch zone.
Are these problems that need to be addressed by Alesis? Are they even problems? I don't think so. Every edrum company handles triggering a little different than the next. I think what we are seeing is the way Alesis approaches triggering. The truth is, it is easy to work around these Alesis quirks. The DM10 is able to do so much (see
DM10, 35 additional sounds via MIDI!!!) so none of these "issue/problems" (as some would say they are) should never be a problem.