In Trigger: Great Idea, Poor Execution

I’ve used a lot of sample replacement tools, including plugins like Slate Trigger 2 It sounds great, but lacks proper humanization, which becomes a problem when you’re trying to avoid that “machine gun” snare effect.

That’s what drew me to In Trigger. The humanized velocity feature looked like exactly what I needed, and to be fair, that part actually delivers. It’s the strongest aspect of the plugin.

Unfortunately, everything else falls apart.

First, stability and reliability are a mess. In demo mode I thought the dropouts were just limitations, but after buying it, I realized the plugin simply misses hits. It forgets triggers. Opening a new instance can mess up an existing one, forcing you to reanalyze everything. Even relearning sections manually doesn’t fully fix it.

Triggering accuracy itself is inconsistent. I tried adjusting sensitivity, retrigger, separation, no setting really locks it in properly.

Then there’s the sound quality, which is honestly the biggest disappointment. The internal samples are extremely poor. The snares and toms sound flat and artificial, like random, uncurated samples rather than something properly recorded for a professional tool. Compared to Slate Trigger2, which offers high-quality, mix-ready drums, InTrigger is nowhere close.

Another major issue is how the sampler engine behaves. You can clearly hear when a sample is triggered, it cuts off the tail of the previous hit. The room, decay, and natural sustain just disappear unnaturally. What it seems is that what sets other similar products apart is also the sampler section. That’s where a lot of the “magic” happens. In this case, the sampler feels very basic, and that’s exactly what sets it apart in a negative way. It sounds like a standard sampler rather than something purpose-built for drum replacement. The sampler engine here really needs to be worked out.

MIDI functionality is also poorly implemented. On paper, there’s MIDI out, which should allow triggering external samplers. In practice, it’s almost unusable. There’s little to no documentation, tutorials don’t explain it, and getting it to work is unnecessarily complicated. I run a very complex MIDI rig in my studio and rarely run into issues, but here I couldn’t even get it working properly in Logic Pro, I just couldn’t figure it out.

Pros:

  • Excellent humanization engine

Cons:

  • Unreliable triggering / missed hits

  • Buggy behavior between plugin instances

  • Weak sampler engine (unnatural cutoffs)

  • Confusing / unusable MIDI implementation

For $29, it’s not a huge loss, but it still feels like wasted money. The idea behind InTrigger is solid, and the humanization is genuinely good, but the execution just isn’t there.

I really wanted this to work. I genuinely did. I wanted something that just works out of the box, with minimal effort. You load the plugin, learn the triggers, and then it mostly just does its job, with only a bit of tinkering here and there.
Instead, it ended up being the opposite. I spent more time than I normally would, not less. For example, I was trying to fix a snare for about two hours. Then I moved on to the kick, and suddenly the snare hits were gone. I fixed the snare again, and then the kick disappeared. I kept going back and forth like that, and nothing stayed stable.

Right now, it feels like it will just get buried in the pile of plugins, with missing basic features already giving that impression.

I know this isn’t the place to promote other products, but at this point I’ll be going back to Slate Trigger. It’s not perfect, especially when it comes to humanization, but it’s reliable, sounds great, and actually holds up in a mix.

Right now, In Trigger just isn’t cutting it for me.

1 Like

Yeah, can’t disagree with any of that. I too was excited about InTrigger (especially the live version), but ultimately gave up and went back to using Slate Trigger for recordings and giving apologies for the thinness of live snares.

Mostly I was excited about the trigger separation, since I often get stuck with electric kits and only a stereo mix. But even with a dedicated channel I also didn’t find the samples any better than the original signals.

So yeah, great idea, doesn’t work well enough to be useful. If the trigger separation was better then it would be awesome, but also I’d be happy enough with just the “smart gate” functionality.

1 Like

The way I see it, In Trigger will likely fall behind unless Waves seriously reworks it. The core idea is strong, and there are genuinely impressive ideas here, but it isn’t reliable right now.

The triggering engine is inconsistent and buggy, for example, I’m working on a kick drum with some bleed, using a gate before InTrigger’s detection or Triggers gate. It will correctly trigger some kick hits, then in a tom section it slightly triggers toms, which is understandable and can be fixed, but then a clearly stronger kick hit in between the toms doesn’t trigger at all…whaaat? One hit is detected, a louder one isn’t, and there’s no clear consistency in how it responds to threshold or signal strength. At that point you wonder whether you should re-learn the section, ok a learn fixes it but then the next section doesn’t work. Close session re-open and it doesn’t work at all, everything has to be done again and again.

I picked this while mixing an album for a more humanized feel, something Slate Trigger struggles with, but it takes too much effort to get consistent results.

At this point, I don’t have much confidence in its future without a major overhaul.

I just lit $30 on fire with this app. The other poster is spot on. The samples are barely usable. The midi generation/extraction is a joke and I can’t get it to work in a usable way. I should have known better based on the price. I guess I just need to feel lucky I didn’t pay the original $89 price. Either way I’m bummed.

I don’t know a bout the first 2 issues but the last 2 might just be be more flexible than you realise.

  • Weak sampler engine (unnatural cutoffs)

If you click on the CR8 icon on the bottom right it expands the sampler section and there is alot or sample playback customisation that can be done there, in eluding filters and release tails.

  • Confusing / unusable MIDI implementation

Meanwhile, clicking on the arrow in the bottom left corner will allow you to customise the modi note generation along with any velocity levels and curves.

Unless you already know all about this, then this is not really helpful.

I 've reported some issues in the past and alot of it ended up getting addressed. So I reckon leave your feedback on their website. Apparently everything gets read and the more voices the more squeaky the wheel, the sooner it’ll get a good oiling.

This is the link I’ve used in the past. Just create a form with Tech Support.

I find the samples are fine for blending with a live input which is what I’m looking to do anyway. I agree the triggering is not great. I’ve tried with the raw mic input, processed mic input, trigger input, and the amount of missing hits is surprising, especially when you can look at the graph and see a hit way over the threshold not trigger a sample then have bleed from another drum trigger a sample when it’s clearly below the threshold. I was excited about this plugin when it came out but I gave up on it fairly quickly which is a shame because having this capability on the LV1 should be a game changer. Hopefully it gets an overhaul soon.

Note there are updates for InTrigger as of the last few days. (not sure if they address any off your concerns however).

Making the Target value lower, below the Detection UI can help with picking up more hits. Or maybe some of those hits you want to assign to a slightly different sounding sample, such as harder hits.

The other thing can help is setting the Retrigger value lower, especially in the case of faster playing. While the Trigger shift can help with adjusting the timing/synch.

I have tweaked a lot of those settings over long sessions with virtual playback. The lower threshold just picked up more bleed and caused too many false hits… even when using the trigger as the input. The retrigger speed helped the most. But there are still odd discrepancies between what the graph is showing me and when things are being triggered. I will sometimes have obvious hits that audibly and visually are definitely over the threshold that won’t trigger a hit but an adjacent high hat or cymbal hit will trigger the sample even though those are definitely under the threshold. I don’t seem to have these problems with the exact same triggers on an spd-sx. I’m well seasoned dialing in triggers as is the drum tech for the band I’m working with. Using the mics as an input renders similar results just a little looser.

I think the latest updates were just adding samples but I’m up for trying again. I’d love for this to work natively in the console so I can eliminate the spd-sx.

I just went back to using Slate trigger which also has it’s issues but the samples are great the triggering is way way better although sometimes it sounds a bit machine gune’ish which was the reason i got Waves trigger, judging by what I saw online this was what I was looking for but not in practice, didn’t do what it claims to do. One thing that it does better than Slate trigger is that sample drop works better with velocities, in Slate trigger you need to go via the editor which I never found to work well, in Waves trigger this works a bit better though.

Imho the sampler section of Waves trigger is very weak, which I have explained in my post, yes it can be played around and tinkered with but it should sound good even on default.

Shame it doesn’t run standalone, same thing with Slate trigger.

@houghton.cb, @menkisertek… Sounds like it might be worthwhile telling support directly, Even send them video clips demonstrating the issues more specifically. At least it would give them something more verifiable to work with.

These are not issues that I am experienciing, this is my thought on it and by the looks of it other users here seem to feel the same about Trigger. I would suggest Waves redesign this otherwise great idea. Samplewise, there are plenty of companies in the drum sample market, why not have one of them on board to create a sample library for this particular product?

Share some videos with Tech Support so they can see your issues first hand. That will give them something more to work with.

This is not an “issue” that I am experiencing, these are my general thoughts on the software itself, it is a weak and poor software which I have uninstalled anyway, if there wasn’t a forum talking about it I would have forgoten that it even exists!

I would just find it a pity if you didn’t share any videos of your experiences with Waves as it could have lead to fixes that would help everyone out. But you’re under no obligation and you gotta do what’s best for you,