Hello,
we’re rephrasing for our upcoming arena tour in germany end of November this year.
Our setup: 2x DiGiCo Quantum 7 with 2 Titan-R, Axis One on each engine, all running at 96kHz, PlugIn V16, SuperRack V15, fw 16.5 (all updated 3 days ago).
We switched to InTrigger from a Pearl MiMicPro unit, because InTrigger has significantly less latency and is way more handy.
We still use out trigger-pickups on kick, snare and toms for dual purpose:
first we use it as side chain for the gates on the microphone channels and second to layer some samples with InTrigger.
So we have set them up like microphones, just connecting them to separate mic-inputs on our consoles.
Therefore we use InTrigger in 100% sample as the “real” drums are parallel on separate channels (all together in a latency group to keep things together).
So far so good - works. But we experienced some strange behavior (we could reproduce it by using virtual soundcheck and looping partial bars):
As the trigger modules have lot of spikes, the from time to time cause peaks in inputs. As we are not hearing the triggers, but only the layered Samples vom InTrigger plugin, we normally wouldn’t bother, but this clipping causes the cpu to peak on the very moment (the Titan server sits around 42%, peak is somewhat around 50%, so not really critical) and this peak causes up to 30,000 lost samples from server back to console which leads to very noticeable crackles.
We tried to just lower the Input to SuperRack, but when we are low enough not causing any cracks anymore, we don’t have enough input, to trigger the higher value samples, when the drummer hits hard.
going up a bit to reach the higher value samples, again causes these drops.
switching off the two low level layers and cooling down input just a bit also avoids drops/crackles.
But this isn’t again true for the kick/snare, where we have combined layers (but all playing at the same time, not level dependent).
So there seems to be two layers (or combined) issues:
- clipping a racks input causes cpu occasional clipping/Cracks (even you don’t hear distortion beforehand)
- InTrigger seems to clear ram and then has trouble loading sample layers for instruments not used often (like toms); at least at 96kHz
Did someone experience similar with InTrigger yet?
Thanks Peter