finally after long time request we got InTrigger! In studio this wasn’t a problem, as there were many triggering tools out there and with ProTools one could easily insert drum samples manually.
I tested InTrigger - it worked well so far (with way less latency as even the most expensive drum modules do!).
But I’m urgently missing a parameter to define, which sample in the 4 available velocity layer would be played.
We used trigger-pickups as input to InTrigger. If you gain them as hot, that the velocity layers at triggering correct, we got peaks in the server which leads to crackle a dropouts.
Lowering gain “fixes” this, but then the samples are are played “to low”, as the drums weren’t hitting hard.
So having user definable thresholds for each layer (or a user velocity span for each layer) is missing here.
… yes, but there no such thing in InTrigger live. So still no option to define which incoming velocity from the actual drum will trigger which sample of the 4 velocity layers in InTrigger live.
Oh sorry man. I did not read “Live” anywhere. But then, I do also literally have mild dyslexia.
I understand there would be differences between the two as live versions of Wave’s software seemed to be focused on reducing as much latency as possible. This usually results in removing any latency inducing features.
But perhaps you can customise your setting in the full InTrigger, save it as a preset to be used in InTrigger Live. In theory, that should work.
