[Ferrauda]

Hi  (Please excuse my bad english)

At first, the problem will NOT be solved modifying Dtxplorer settings or banks, because the problem nature is different.

So, don´t touch anything into your Dtxplorer brain, this is not necessary.

Dtxplorer has the note values for Snare and Kick changed respect to the GM (General Midi ) notes. I mean, our Dtxplorer midi out is NOT GM (general Midi) but a particular Yamaha midi conception.

Just as an example, (not the exact numbers), if your Dtxplorer sends the Snare in the note #36 , and GM (general Midi) trigger the Snare in the note #38, and the metronome click in the note #36, then you will hear a metronome click when you hit the snare….

Since I use to work with Cakewalk Sonar, I don´t know how Logic works with drums.

But I had the same problem with my Dtxplorer into Sonar, and it was corrected just by modifying a Drum Map.

A Drum Map is a sheet having each one of your input midi device (Dtxplorer in this case) notes applied to trigger a different sound.  I think Logic should also use something very similar to the Sonar Drum Maps.

Each note has an INPUT note value (the one coming from your Dtxplorer and getting into the DAW) and an OUTPUT note value (the one going to your Ezdrummer kit to get the snare if you want a snare, or the Kick if you want the kick, etc).  That numbers are into the Drum Map sheet.

Well, in Sonar the solution was just to take a Standard Drum Map and changing the OUT value notes for Snare and Kick.  (I remember it was by working around the notes #33, #36 and #38).

Later, you save the modified Drum Map naming it and load it to your drum track as TRACK OUTPUT if you want to record your Dtxplorer in MIDI.

Ezdrummer works perfect doing this and you can exchange the drum kits with no problem.

Just study a little and work around Logic drum maps.

Your problem can be solved just by setting the exact notes into a single sheet (Drum Map).

Hope it can help.

Cheers
fab

[Author]

Replies