SD2 Intermittent Triggering

[grizsk]

Hey there,

I’ll start off with the setup:

MacBook Pro 8gb Ram dual SSD’s
Presonus iTwo interface
Old Yamaha DTX 2.0 e kit
Superior Drummer 2 in SOLO w/ EZX

Kit is all mapped out nicely, but SD2 is only registering every second or third hit. Its almost as if its making me wait until the first sound is finished playing before letting me hit another, except sometimes it decides to register 2 hits in quick succession (but never 3).

So. Here’s the thing. The drum module is very clearly registering every hit on every pad, I can see the velocity register on the module screen. Only about 30% of those hits are making it into Superior Drummer.

The kit plays like a dream on its own. I fiddled with all of the pad, velocity, crosstalk and every other module based setting, to no avail.

Are there any hidden settings in SD2 that would cause this issue? Has anyone experienced this before with SD2?

Thanks in advance for any help. Let me know if you need any further info!

Topic

[Scott Eshleman]

How are you connecting the e-kit to your MacBook?
I ask because both USB and MIDI have their limits in terms of cord length.

[grizsk]

Midi in from DTX module to midi out on interface.
Midi out from DTX module to midi in on interface.
USB from interface to MacBook.

All cables are under 6ft.

I’ve considered new midi cables, but these aren’t old to begin with and the last thing i want to do is shell out more cash on non-fixes.

[John]

Hi,

most often, the problem with drop outs is a too low set Buffer size. OR bad cables.

John Rammelt - Toontrack
Technical Advisor

[grizsk]

Thanks for your input guys, I just scraped together the solution. For anyone else who may have this issue in the future, I needed to do the following:

– Set the menu style for my DTX module from ‘Easy’ to ‘Advanced’
– Locate the MIDI clock settings in the Utility Menu (in my case the target was called ‘SyncMode’) and set it to ‘Exterior’ to allow what I assume is Logic’s timing clock to take over.

That fixed the bulk of the issue immediately and I was able to play most pads with zero latency issues.. However, two pads would still respond only to every second hit. Then it struck me like a ton of bricks. The last kit I was using before my foray into SD2 on my module was not a conventional kit. I had built my entire map on an effects kit that has ‘hold’ functions on those 2 triggers. Hit the trigger once, a sample would start, hit the trigger again and it turns the sample off. On/off/on/off.

Every second hit.

This has been quite the journey.. I hope this helps someone in the future.

[Author]

Replies