[Timothy Brannigan]

Lots of people are complaining, so why no answer? My Roland TD-50 kit triggering SD3 produces dreadfully low velocity data upon monitoring and recording. The entire reason I bought expensive edrums and SD3 is to get work done. It’s been like a year and I haven’t been able to get any “live” drum work done because the system will not work.

I bought a new MIDI interface, trying to remedy the velocity issues. It didn’t change anything. I’ve even tried 3 different sound modules. I tweaked the hell out of all of these modules with no difference. I’ve played endlessly with velocity curves in the software and hardware. Nothing works.

I’ve had this issue ever since the first time I tried triggering SD3 with edrums. That’s a long time ago, when 3 was released. I see lots of people complaining here about the same thing, but I find zero answers. Toontrak PLEASE HELP!

[Timothy Brannigan]

I bought a new MIDI interface, trying to remedy the velocity issues. It didn’t change anything. I’ve had this issue ever since the first time I tried triggering SD3 with edrums. That’s a long time ago. I’ve even tried 3 different sound modules. I tweaked the hell out of all of these modules with no difference. I see lots of people complaining here about the same thing, but I find zero answers.

[Timothy Brannigan]

I’m having the same problem and it’s been driving me crazy for months. Could it have to do with using a midi to usb adaptor into a usb hub? Right now I’m using a Roland TD-10 kit to trigger Superior 3. I’ve adjusted the trigger velocity in the sound module which only helps a little bit. It also ruins the dynamics which makes using e-drums inferior to programming with a keyboard. Please help!

• This post was modified 4 years, 9 months ago by Timothy Brannigan.

[Author]

Replies