I am loving inTrigger so far! It is really great, but I have encountered one glaring issue. I have been using inTrigger not just for sampling drums, but as a drum gate as well. It works really well on a kick or a snare, but when I put instances on my tom tracks, that’s when things get wonky. It appreas inTrigger continues to “learn” the track even after the learn process. This is great in a way, because the learn process does not last the length of an entire song. So I get why the continued learning is an asset, but let us turn it off! When I am trying to use inTrigger as a gate on toms that haven’t been strip silenced, and I end up working on a section of the song that has no tom hits, the plugin starts “thinking” that it should be looking for other sounds. The result is that the gate keeps opening when it’s not supposed to, and gets rid of the actual hits it detected earlier. I will walk you through what happened exactly.
I instantiated two instances of inTrigger on my two tom tracks. I went to a section with tom hits, and the plugin learned the hits. I then went to a few other sections of the song to check them, and after a couple of passes on that section, it learned those as well. I repeated this with every section where toms were being played. i then went through the entire song to get rid of any mis-triggers. Ok, job done, or so I thought. About fifteen minutes later I noticed that my toms were missing in sections. I opened the plugin to find that it was now triggering off of the snare bleed in the tom track, and not the tom hits. I repeated my original process again, only to find that the plugin continued to start triggering off of a different sound. The kick and snare continued to work just fine, but those elements are present throughout the song, so there really isn’t a way for it to get confused.
In conclusion, I love the plugin, I appreciate the extended learning, but at some point let us turn it off when we know it has learned all the info it needs to perform. Working around it is not difficult, but that’s not the point. Just please give us back some control.
2 Likes
This is an interesting observation.
I wonder if it is indeed intentional, or just minor glitch with InTrigger’s coding. You could always get in touch with the devs and let them know what your experiences are. At least then there might be a chance they’d do something with thew information.
Having the same issue! very frustrating.
I thought the plugin update a few months back allowed you to freeze it or something. Basically stop it from constantly learning and updating.