TRIGGER 1.65 UPDATE Available MIDI from AUDIO

[JeffTD]

I agree with Marcus, and that's why I keep posting about it. I really do hate the new GUI, though, and thinning the Drumtracker-esque bar they use now is all it'd take to solve most issues with it.

It's kind of a moot point now, though, as I'm really looking heavily into using Battery 3 for my replacements instead. At least then I could print my room tracks separately from my direct tracks and have them be in phase.

 

[Slate]

We'll be coming out with a very quick 1.66 update.. this will make TRIGGER exactly like the 1.64 but will add the new midi capture.. in a future update we'll have a new ULTRA mode which will be even more accurate on harder to trigger tracks.. This way, old projects with 1.64 won't need any settings changes which they do with the current 1.65.

For GUI, I'm still a bit amazed at the reaction since its just the full waveform rather than half of it.. and you can zoom. All I will say about the display GUI is that it will not go back to the original version.. you guys are smart folks and can assume why.

I personally don't think you can fault the display for not being able to properly trigger tracks with the plugin.. I just did two metal tracks with blast beats full of leakage with ease and had no problems with the display. Sorry if you hate it.

 

[darthjujuu]

We'll be coming out with a very quick 1.66 update.. this will make TRIGGER exactly like the 1.64 but will add the new midi capture.. in a future update we'll have a new ULTRA mode which will be even more accurate on harder to trigger tracks.. This way, old projects with 1.64 won't need any settings changes which they do with the current 1.65.

For GUI, I'm still a bit amazed at the reaction since its just the full waveform rather than half of it.. and you can zoom. All I will say about the display GUI is that it will not go back to the original version.. you guys are smart folks and can assume why.

I personally don't think you can fault the display for not being able to properly trigger tracks with the plugin.. I just did two metal tracks with blast beats full of leakage with ease and had no problems with the display. Sorry if you hate it.

old mode and new mode... definitely the best we could've hoped for. Adam - I just used your suggested Reaper MIDI print function last night for a 10 song full length. The amount of time that one small tip saved me is mind boggling.

 

[RichMinerva]

old mode and new mode... definitely the best we could've hoped for. Adam - I just used your suggested Reaper MIDI print function last night for a 10 song full length. The amount of time that one small tip saved me is mind boggling.

what tip was this dude

 

[TheDriller]

For GUI, I'm still a bit amazed at the reaction since its just the full waveform rather than half of it.. and you can zoom. All I will say about the display GUI is that it will not go back to the original version.. you guys are smart folks and can assume why.

It has exactly half the vertical resolution of the old GUI. And the new full-waveform view has no practical advantage, it just takes up the same amount of space to display less information. Sometimes less is more, but certainly not in this case.

 

[darthjujuu]

what tip was this dude

Instant convert audio to MIDI in Reaper using Trigger

(I imagine this will also work for Drumagog and maybe even ReaGate?)

1. insert Trigger on drum track
2. adjust settings to achieve best possible triggering response
3. Click settings in Trigger
4. enable MIDI out, Select proper notes/channels (VST Internal)
5. right click the audio event and select "Render item as new take (MIDI Output)"
6. ???
7. Profit

Now, if you enable "MIDI In" in Trigger on that same track, it will act as a VSTi for your newly bounced MIDI and you can automate velocities. (Beware of blending, this bounce seems to not be phase accurate.) Or, if this track happens to be entirely bleed free (such as in my case, half-programmed drums) you can quantize the MIDI and edit it any way you see fit.

 

[AdamWathan]

The not phase accurate thing is Triggers fault. When using MIDI In, it triggers the midi instantly instead of waiting 485 samples like it does for audio. So it still reports 485 samples of latency to the host but triggers right away, so when the host compensates the delay the triggered signal ends up being 485 samples early. This has been confirmed in Cubase and Reaper and reported so maybe fixed in 1.65 but it sounds like 1.65 introduces even worse problems so I'll just keep using a time adjuster after Trigger when triggering via MIDI.

Also, I think the MIDI rendered from Trigger is either early or late as well, so I usually just slide the MIDI track in time, not a big deal really and to be expected when all hosts handle MIDI a bit differently.

 

[Soundlurker]

Sometimes I wonder...am I the only person here other than Slate that thinks Trigger is amazingly good, powerful, accurate and easy to use as it is (1.64)?

I'm saying this quite honestly, just after I got a death/grind project with super-fast kicks and snares. I didn't need to automate or edit anything. After I routed things so I use every possible suppresion minus cymbals and after I set the trigger hi-pass to ~200hz it was literally done. All I even needed the GUI for was to set input and detail which is so easy I don't see how you'd have any trouble with it. Sensitivity at 40, retrigger also around 40 and it was solid from start to finish 0_o

 

[darthjujuu]

I updated. The drag and drop could be useful in other DAW's, but I can't imagine anything that's better than Reaper's print to MIDI function. In addition to the latency issue, the MIDI triggering (using TRIGGER like a vst instrument) is now also broken...the samples play randomly way too early or late (no logic to it), and it worked better (although not perfectly) before. Steve, you gotta crack the whip on your beta testers! dudes be slackin!

 

[mva801]

the MIDI triggering (using TRIGGER like a vst instrument) is now also broken...the samples play randomly way too early or late (no logic to it), and it worked better (although not perfectly) before. Steve, you gotta crack the whip on your beta testers! dudes be slackin!

Bumping this thread rather than make a new one. Any word on a 1.66 update? I'm having this issue that Jujuu is talking about, and it's driving me INSANE. I made a midi track from my snare with Massey DRT. Using that midi track to trigger the Trigger plugin. I adjust a few velocities and such, then print to an audio track. Well when I print, Trigger is randomly playing the midi everywhere but where it's supposed to. The actual hits are coming anywhere from about 10 to 900 samples away from the actual midi note. Frustrating to say the least.

 

[s34nsm411]

how do you get the track colors like that in cubase?

 

[TheBlackSheep]

Steven, your samples are all over the net.

Steven.Slate​.Drums.Plati​num.Library.​v3.5.KONTAKT​-AudioP2P

Do something man.

 

[Trevoire520]

Best to give Slate an email through the website letting them know where you've found it so they can take steps to remove it.

 

[colonel_claypoo]

that sucks.
hope something can be done about it.

however, it's funny to see people struggle with cracked software, trying to get it to run properly:

"So I've tried at least 20 times now.. Load Kontakt in Reaper, add library (activate still there) remove library, close Kontakt, close Reaper, Repeat.
Open Kontakt standalone, add library (activate still there) remove library, close Kontakt, Repeat. Tried running in Administrator still nothing.
Added actual folder that I downloaded instead of copying to lib location, nothing."

HAHA!

 

[updog]

however, it's funny to see people struggle with cracked software, trying to get it to run properly

agreed.

too bad the amount of effort mostly doesn't make them buy the plugins, though... just remove them from their computers. but that's good enough.

the samples had a sort of watermark system, right? while there's some damage done, you can take the files down and send the bill to the guy's house who uploaded them.

 

[ahjteam]

from slate via gearslutz...
Ok.. so soon we'll have a new update..

It will make the version of TRIGGER exactly like 1.64.. but with the new midi capture.. The latency setting will be exactly the same 11ms.. and so on.

We'll reintroduce the newer trigger engine as an optional mode in a future update.. this way all old project will play exactly the same, and you can still take advantage of the really great midi capture and drag.

We'll be coming out with a very quick 1.66 update.. this will make TRIGGER exactly like the 1.64 but will add the new midi capture.. in a future update we'll have a new ULTRA mode which will be even more accurate on harder to trigger tracks.. This way, old projects with 1.64 won't need any settings changes which they do with the current 1.65.

For GUI, I'm still a bit amazed at the reaction since its just the full waveform rather than half of it.. and you can zoom. All I will say about the display GUI is that it will not go back to the original version.. you guys are smart folks and can assume why.

I personally don't think you can fault the display for not being able to properly trigger tracks with the plugin.. I just did two metal tracks with blast beats full of leakage with ease and had no problems with the display. Sorry if you hate it.

I wonder what is their "soon" is, since that was in March and it's been 5 months since that was posted and when I just logged in to the user area in Slate website the 1.65 is still the latest version available... The drag and drop midi at least in OSX + Cubase 5.5.3 is totally broken too, it only drops like 3 bars worth of midi data.

 

[::XeS::]

The drag and drop works wonderfully in Protools / OSX. Did you try to delete previous "midi recordings" before the right one?

 

[Empathy]

Drumagog shits me to tears. Is Trigger worth the dollariedoos / less agonising?

 

[ahjteam]

The drag and drop works wonderfully in Protools / OSX. Did you try to delete previous "midi recordings" before the right one?

I did some trouble shooting and figured out a few things...

1) If you start the midi capturing from the beginning of the track and it will work like it should be, but if you start from anywhere else and have it on loop playback, it won't do more than the area in the new loop, in my case it was 1 bar of the 8 bars I wanted to capture. AND you ALWAYS have to drag and drop the midi to the beginning of the track (bar 1, beat 1). Since this was not in the manual, I didn't know that. (Yes, I'm one of those idiots who read the manuals when totally confused)

2) If I set my hardware buffer to 2048, the midi triggering goes totally haywire. With 1024 and below it works just fine.

edit: audio demo, first 1024, then 2048: http://dl.dropbox.com/u/1338211/slatetrigger_1024_2048.mp3

 

[vespiz]

Would be nice if there was an off-line renderer (option?) for the MIDI. I have no idea if this is even remotely possible.. Kinda like what Sound Replacer does but with MIDI.

Other than that, Trigger was one of the better purchases I've done recently. Highly recommended!