Yamaha DTXpress/DTXplorer/DTXtreme

Thanks very much, Keith!

Alright, I've been playing around with this for a bit and have come
across a rather unusual problem..

Sitting down and playing the kit doesn't work. I first need to do a
bulk dump (I've been dumping "one drumkit"), which suddenly enables me
to play the kit as normal. HOWEVER, I can only seem to play any given
pad for as long as I can keep that pad "busy". As in I need to hit it
fairly hard and very very often (pretty much a slow roll) in order to
keep things working 'normally'. If I stop hitting the pad frequently
or start hitting too quietly, the signal just drops off and no more
midi messages are sent. I have to do another bulk dump to get it
started again.

Any idea at all what might be causing this? It seems so strange.

The other thing is that I downloaded MIDI Watch to keep an eye on the
signals sent. When I just play the kit there's nothing. If I do a bulk
dump a bunch of code pops up, and then after that it shows the normal
Note On/Note Off messages for as long as I keep the drum kit "busy"
and hit it plenty and often. However I noticed that the Note value
displayed by MIDI Watch is a full two octaves higher than what Battery
3 is telling me! For example, in MIDI watch if I hit a pad it'll say
Note: B3. But in Battery 3 the cell assigned to B1 will get triggered!
While I can work around this easily, I'd still like to know what's up.

Other than that I'm amazed that this got set up pretty quickly. I
opened up Battery as a vsti within cubase and set up a midi track and
everything works well. The sounds are triggered in real time, the
velocity is taken into account, and when I record the midi track
everything gets popped in beautifully. It's just this really weird
matter of having to play a ton before the signal just cuts out. 

If anyone has any idea what's going on here please let me know!

Thanks,
DS