TRIGGER Intro Video and NEWS
- Thread starter Slate
- Start date
GeertSamuel
Member
I'll try the new demo. The first demo wasn't at all accurate or even phase accurate. Hopefully version 1.1 will live up to the expectations.
Soundlurker
Member
- Nov 19, 2005
- 3,730
- 0
- 36
AdamWathan
Member
Guys, I'm sure the problem just in triggering settings. TRIGGER is very sensitive plugin and for some tracks even changing Input by 1 dB may totally change results.
Feel free to PM me your tracks and I will send you renders and screen shots with optimal settings for your tracks. I always happy to help you
Hey Adam, I found your track in this thread. I can post here (or PM you) render and screen shot with optimal TRIGGER settings for your track.
Feel free to share any findings right in this thread for everyone to see, I don't mind being proven wrong in public
I want this plugin to be as accurate as you're claiming badly, trust me!For some reason I did find that using only rimshots put the samples in a more accurate place than using the full snare track, not sure why that is. I know you said the soft samples have a smoother attack, but you could see pretty clearly that the sample wasn't starting at all until 5-10ms after the transient of the incoming signal.
imo, it would be amazing if you will cut a part of track with 10-20 hits so that it will contain "good" and "bad" hits, and post the unprocessed wave, triggered wave and screen shot of trigger settings.Feel free to share any findings right in this thread for everyone to see, I don't mind being proven wrong in public
For some reason I did find that using only rimshots put the samples in a more accurate place than using the full snare track, not sure why that is. I know you said the soft samples have a smoother attack, but you could see pretty clearly that the sample wasn't starting at all until 5-10ms after the transient of the incoming signal.
An after taht I hope slate support will do the same with his variant of setting
So it would be great way for me (and I hope not only for me) to learn how to setup this plugin from such a clear examples.
Don't get me wrong, I downloaded your wave file and have played with it, but I've spent a lot of time to find the misstriggers in such a long track.
AdamWathan
Member
imo, it would be amazing if you will cut a part of track with 10-20 hits so that it will contain "good" and "bad" hits, and post the unprocessed wave, triggered wave and screen shot of trigger settings.
An after taht I hope slate support will do the same with his variant of setting
So it would be great way for me (and I hope not only for me) to learn how to setup this plugin from such a clear examples.
Don't get me wrong, I downloaded your wave file and have played with it, but I've spent a lot of time to find the misstriggers in such a long track.
Good idea, I'll get something up in the next hour.
AdamWathan
Member
I've actually gotten it to work pretty much perfectly now, thanks support dudes. The key seems to be setting the detail knob as absolutely LOW as possible without it mistriggering. There are a lot of settings where it is low enough to catch everything and trigger the hits, but like the support team said, in some of those cases, its the body of the hit that is triggering the transient of the sample because of the weird dynamics in the playing, so you need to make sure the detail knob is getting the sharp transients of even the softest hits. So turn that knob WAY WAY down, and only bring it up if you hear it misbehaving.
Another trick, NORMALIZE the copy of the snare track that you are replacing. Obviously don't use the normalized raw track in the mix because normalizing is pretty useless in general, but for replacement it makes perfect sense. Normalizing puts the hardest hits closest to 0db so there is a LOT less room for guesswork with your input gain and velocity settings. This way you are making sure the incoming signal is as loud as possible on the loudest hits, so Trigger can easily identify which hits are hardest and which are soft. My detail knob was set at 0.20 which is default, but because I normalized the snare track before replacing, it was the equivalent of bringing that detail knob down to like 0.1 or less, since all the hits were now proportionately louder. On top of that, I STILL had input gain cranked to +6. All of this is JUST so you have finer control with the detail knob, that knob is key.
Here's what I'm getting on rolls now...
Much better!
Here's the settings and the wav file for anyone else to try...
http://www.adamwathan.com/trigger/trigraw.wav
Another trick, NORMALIZE the copy of the snare track that you are replacing. Obviously don't use the normalized raw track in the mix because normalizing is pretty useless in general, but for replacement it makes perfect sense. Normalizing puts the hardest hits closest to 0db so there is a LOT less room for guesswork with your input gain and velocity settings. This way you are making sure the incoming signal is as loud as possible on the loudest hits, so Trigger can easily identify which hits are hardest and which are soft. My detail knob was set at 0.20 which is default, but because I normalized the snare track before replacing, it was the equivalent of bringing that detail knob down to like 0.1 or less, since all the hits were now proportionately louder. On top of that, I STILL had input gain cranked to +6. All of this is JUST so you have finer control with the detail knob, that knob is key.
Here's what I'm getting on rolls now...
Much better!
Here's the settings and the wav file for anyone else to try...
http://www.adamwathan.com/trigger/trigraw.wav
I've managed to put detail way lower by using "bleed suppression"
if you have not only the snare track you can try it, cool shit 8)
if you have not only the snare track you can try it, cool shit 8)
AdamWathan
Member
avrinder
Member
Ermz
¯\(°_o)/¯
Umm......am I the only one that notices an eerie similarity between a certain user named "methull" and "trigger_support". Just an observation....... not making accusations......
JeffTD
Senhor Testiculo
Yes. It's just another dude with bad English - probably the dude who coded it, as Ermz suggested.
Hey Guys, TRIGGER SUPPORT happens to be none other then one of the Slate Digital top programmers Alex (not the customer support Alex).. Alex is one of the designers of TRIGGER and can help anyone with a problem track. The good news is, with 1.1 demo, we haven't found ANY track that couldn't be triggered with phase accuracy after some simple tweaking. Once you get to "know" trigger, the tweaks become obvious for each track. Also, the bleed suppression is a must when using low detail settings!
Thanks, and feel free to take Alex up on his offer to send him tracks so he can show proper settings. Thanks,
Slate
Thanks, and feel free to take Alex up on his offer to send him tracks so he can show proper settings. Thanks,
Slate
::XeS::
Member
Is there a way to set the blend between the miced track and the sample? I tried to play with the settings but I found nothing
AdamWathan
Member
Just click there and drag up and down and you can set the wet/dry, took me a while to find it at first as well haha...
::XeS::
Member
Hey, AdamWathan. What if I tell you that your track can be triggered with 100% phase accurate result on default settings? And you need to do only 2 things to get this result
I checked this in Cubase. So I downloading Reaper right now, to check this in Reaper to be absolutely sure that it working identical in Reaper.
I'll post results soon!
I checked this in Cubase. So I downloading Reaper right now, to check this in Reaper to be absolutely sure that it working identical in Reaper.
I'll post results soon!
