Clicking on the screen does not really give you a really precise “velocity sensitive” performance of the kit drum piece. It’s true that depending on the area clicked you might get different velocity samples. – I agree with this previous comment

BlueMistral wrote:

Reduce the velocity range from 127 to 90, i. e. Drag the right 3 points to the left in the curve editor

– You can edit the velocity curve so that your Virtual Drum Kit reacts with a non-linear curve. – But you can always edit your recorded drums and then scale the velocities of each drum piece. I suppose it’s more convenient to adapt your kitdrum pieces’ velocity curves so that you hear the result you’re going to record. Just save your kitdrum patch with the velocity curves you’re planning to use in your song(s).

The stock SD3 library is very soft/low volume even at full velocity 127, you need to modify the curve/velocity range

Not the sound but the volume and easiness to reach it, I hit my snare as hard as I can and I can’t never get 127, increasing sensitivity on the module to get more volume is wrong, reducing the dynamic range by modifying the curve is the only solution that works for me, if you’re a heavy hitter and reach 127 easily well that’s another topic…

Also that’s why I mentioned the core SD3 library is very quiet even at full 127, compare it to the Fields of Rock, hit your drum to get 127 and it will hurt your ears, so saying 127 is the loudest doesn’t always apply…

• This post was modified 3 years, 4 months ago by BlueMistral.

Not sure I agree with that but I wont argue the point

But you would then set triggers for a 12 year old. The td30 has different bands of trigger settings you can use. It’s not the way I do it in SD3. It doesn’t feel natural to me