[Mike Sheard]

Thanks. I wasn’t really looking for a workaround though, I was after a solution. Translation in a DAW seems like a potential extra layer of latency.
I already run Reaper in the studio, but wanted to get standalone EZD2 running so I can practise without the crappy built in module samples.
Anyway, as suggested by TT, I did a factory reset of the module and I’ve tried both None and the Alesis preset. No dice I’m afraid.
Hope Lerxst has more luck.

[Mike Sheard]

I’d already tried that and a bunch of other things before I posted here. There is no manual mapping in the Surge module or EZD2, which is the problem. Toontrack sent me this, which I haven’t got around to trying.

”Unfortunately, we have had similar reports from other Alesis e-drum users. This usually has to do with the proper CC data not being sent from the module for EZD2 to use.

We always recommend using the factory/default preset for the module along with the Alesis preset in EZD2.

EZD2 can only use and respond to the MIDI as it is received from the module. MIDI not getting through into EZdrummer 2 can hardly have anything to do with installation of the software. Is it possible the checkbox for the device is not ticked/checked-off (in front of the device name) in EZdrummer 2’s Settings > Audio/MIDI setup > MIDI device area? Once the device is checked-off, the Apply button needs to be used to save those changes.

Some ASIO drivers can cause crashes or memory corruptions, so it could be worth testing with a different driver (and restarting EZdrummer after changing it).

Best Regards,
Toontrack Music”

[Author]

Replies