Slate Trigger still not fixed after a year.

Joshua Wickman

Yes Sir!
Feb 11, 2009
1,504
0
36
Michigan
Trigger with midi is not sample accurate and will place drum samples both before and after your original snare. Most of us have to revert back to 1.62 to even use the plugin. Let's hope we don't have to wait another year for this to get fixed.

Here are some past threads with the problem.

http://www.ultimatemetal.com/forum/backline/734637-slate-trigger-midi-mistriggering-problem.html

http://www.ultimatemetal.com/forum/...idi-triggering-not-phase-accurate-reaper.html

http://www.ultimatemetal.com/forum/f-o-h/682671-covert-before-after.html


Slate does have some new plugins in the works though. That should make up for any inconvenience this has caused paying customers. :err:
 
I also have an issue if im loading in multiple samples in the single .TCI file....it'll just lock to a single "articulation" as default and I can't roll through the sample's in that TCI. Very annoying =(
 
I also have an issue if im loading in multiple samples in the single .TCI file....it'll just lock to a single "articulation" as default and I can't roll through the sample's in that TCI. Very annoying =(

That is on purpose so that you have a global articulation control with all the loaded TCI's. The problem is a lot (most all?) of custom TCI's don't follow the same format as the "factory" Slate ones, etc.
 
This happened with both 1.65 and 1.66. Here is a few screen shots, you can see how the sample (in the middle track) ends up early and late. This is not just a single hit that is off, it's every single hit and they ends up out sync with the midi/original snare.

Screen%20shot%202012-10-22%20at%205.36.09%20PM.png


Screen%20shot%202012-10-22%20at%205.38.19%20PM.png
 
That is on purpose so that you have a global articulation control with all the loaded TCI's. The problem is a lot (most all?) of custom TCI's don't follow the same format as the "factory" Slate ones, etc.

I mean, say I put in a few slate snares then I put in say the Death Snare TCI CJ did, it should come up with the death snare names as articulations but sometimes it doesn't, it just sticks to the first sample and wont move. There is no way that's intentional.
 
I mean, say I put in a few slate snares then I put in say the Death Snare TCI CJ did, it should come up with the death snare names as articulations but sometimes it doesn't, it just sticks to the first sample and wont move. There is no way that's intentional.

I've noticed this as well. As a beta tester for a few plug companies and LOVING to trouble shoot shit, the ONLY way around this is to load the DEATH SNARES TCI in your first slot. THIS is the only slot that seems to work properly with ANY TCI containing different articulations...

Other than that, none of the other slots will change the Articulation.

This should NOT be global, this should be on a PER SLOT basis just like EVERY. OTHER. CONTROL IS. =D

SOOOOOOOOOOO yeah!

About the MIDI issue, I thought the LATEST release immensely fixed this but I'm not using PT and haven't even looked at where the Trigger samples are landing.... I'm on whatever the latest build is, 1.66?

Maybe I should take a look and verify the accuracy of the MIDI.
 
I mean, say I put in a few slate snares then I put in say the Death Snare TCI CJ did, it should come up with the death snare names as articulations but sometimes it doesn't, it just sticks to the first sample and wont move. There is no way that's intentional.

Yeah it is.... the whole thing follows the articulations of the first sample I believe. So if you put cj's in there all alone, you'll have all of them. If you put another slate snare in there, and choose hard or something, then everything else will follow that. Since the death stuff has no hard setting, it just sits on the first one. That's how they've designed it. I wish it was the other way around and you could select individual articulations for each tci.


And to the OP.... FUUUUUU! the midi thing is STILL not accurate? I haven't dl'ed the new update yet. I'll have to check it next time I'm at the studio....
 
I'm pretty sure it's fixed for me (I use Reaper). The only problem I can think of would be that your buffer is set too high or the samples you are using aren't cut like the slate samples are.
Although, I highly doubt that's what the cause is on your end!
Only other thing I could see it being is a pro tools bug.
 
Yeah, it's totally intentional. Not that I, or really anyone besides Slate & co. for that matter, agree with it. I feel like you do, all slots should have their own independent articulation control.
 
Do you have delay comp on? and what playback buffer are you set to?

Trigger with midi input will only work in in 256 or under in Protools, and i have tried them all with the same results. Anything higher than 256, it just goes crazy and will not even trigger correct. I made a support ticket about that problem as well, they just said it was a Protools and Trigger problem and can't be fixed. So, Trigger is useless on Protools when i'm mixing at 1024.

I always have delay compensation on as well. Long.
 
Trigger with midi input will only work in in 256 or under in Protools, and i have tried them all with the same results. Anything higher than 256, it just goes crazy and will not even trigger correct. I made a support ticket about that problem as well, they just said it was a Protools and Trigger problem and can't be fixed. So, Trigger is useless on Protools when i'm mixing at 1024.

I always have delay compensation on as well. Long.

Yeah, I've found it has to be below 256, and also delay comp OFF.
Bounce that shit.
 
I'm somewhat glad I never invested in digidesign proprietary stuff/protools etc... To me it seems like the Photoshop of audio, powerful sure, but not user friendly. When watching Pensado's place, he's doing stuff that take 5 minutes that I can do in reaper with like 2 mouse clicks and it blows my mind.

To be fair.... I'm a seasoned pro tools user, and whilst I have nothing but the utmost respect for Dave; he does things THE SLOWEST FUCKING WAY POSSIBLE.
It's him; not tools.