Midi dropout w/TraktorSD2

[J-Reign]

I'm having a hard time trying to figure out why I'm dropping midi notes, triggering cues on TSD2 with my alesis controlpad. It works, but from time to time, it will miss notes. I've been going back and forth with Torq and Torq has no problems consistently playing the notes I trigger. Though, my dicers work well with TSD2, as I test with manual trigger rolls.

Please help!

[fullenglishpint]

things just randomly don't work? Unless it's a hardware issue I don't know, sorry.

bump in the hope that someone has an idea.

[DvlsAdvct]

Turn Quantize off

[fullenglishpint]

Haha how did I not think of that!

[J-Reign]

Thanks, I will try to see if I even have quantization. I'm using Scratch Duo 2.

[DvlsAdvct]

If that doesn't work we'll go from there. But it's almost always a quick fix.

[J-Reign]

Yeah, I looked around to find any quantization settings and could not find any.

I'm basically using USB drum pads(Alesis controlpads) to play drum sounds on a tracks both on Deck A and B. It was not responsive on Scratch live. Works flawless with Itch using Bomes(midi to keys). Works flawless with Torq 1.5 and 2.0(trial). Bought TSDuo 2 w/Audio6 and it skips a beat or two. I figured Traktor would be awesome at this since I used to use it with a VCI-100 and nanopads. I'm sure there's a fix out there. Plus I'll have 8 cues to use, which can be left over for my Dicers.

Might have to resort to buying an upgrade to Torq 2.0.1 because I need this thing to work in front of judges on the 29th of this month. Also because I'll have one more glorious cue over 1.5!

[Str8upDrew]

It's the little "Q" button under the "Main" knob at the top.

[DvlsAdvct]

Dude, read the manual. Quantization. Turn it off.