TRIGGER 1.65 UPDATE Available MIDI from AUDIO

thanks for the update slate.

to all those using 1.62:
i've never used trigger before 1.64 so would somebody mind posting a screenshot to illustrate what was better GUI-wise?

thanks
 
thanks for the update slate.

to all those using 1.62:
i've never used trigger before 1.64 so would somebody mind posting a screenshot to illustrate what was better GUI-wise?

thanks

slate_digital_trigger.jpg
 
Looks like a lot of people like the old waveform display better. Maybe you could just have both displays and allow us to choose which we want by clicking a button or checking a box in the settings.
 
Ahhh bollocks. I just bought Trigger EX 4 days ago. Coupon would have been awesome...

I've been using the Massey DRT to convert to midi and send it to trigger, so I actually haven't even tried the normal trigger method.
One thing I've noticed a bit about the Massey plug is it has placed a few notes a bit too early on the transient. I will definitely give this function in Trigger some work...
 
I've got a problem with 1.65 on my iMac. Running Pro Tools 9.0.1

I've tried opening new sessions and old sessions and when I open Trigger, it does this weird thing where it opens in a certain part of the screen and then as I open and close it, it moves each time it opens. I can still adjust the parameters in Trigger (when I can see them) but I can't move the Trigger window to my other monitor (where I control all of my plug ins) which is quite annoying.

Anyone else getting this?

Pics attached. All I did was open Trigger, close it, and then repeated a few times.

pic1.png


pic2.png


pic3.png


pic4.png
 
Am I the only one whose a fan of the FREE update?

I mean the old waveform display looks cool but is it really that big a deal?

Thanks slate haven't tried the new midi stuff yet but it will definitely come in handy on my first project his weekend.
Cheers! <3
 
I'd want to be able to automate stuff in Trigger badly... And by that I mean everything, not just Master Bypass, Input volume, Output volume, Sensitivity, Retrigger, Detail and Articulation...

yeah, i couldnt believe my eyes its impossible to automate the master blend function.... would be gold for more dynamic sections to have 20 % and loud sections 80-100.
 
Don't you guys print your drum samples? I don't need to automate anything in Trigger because it's gone from my session before I mix. Print samples, if it screws up, change settings and punch in the section that triggered wrong, repeat until you have perfect sample track and then automate volumes against the natural drum track if you want to change the blend. Trying to automate all that stuff sounds like waaaay too much extra time consuming work...
 
I definitely agree with Adam, not only is it just a better workflow practice in my opinion, it also saves on CPU which can come in handy! Of course you end up committing your sample choices but hey that's nothing to be afraid of!

I for one am not bothered by the new GUI, I've never really encountered any problems with it.
 
Don't you guys print your drum samples? I don't need to automate anything in Trigger because it's gone from my session before I mix. Print samples, if it screws up, change settings and punch in the section that triggered wrong, repeat until you have perfect sample track and then automate volumes against the natural drum track if you want to change the blend. Trying to automate all that stuff sounds like waaaay too much extra time consuming work...

Considering the ridiculous amounts of CPU power we have in our hands these days, I like to keep as many options open as possible while working during all stages. Trigger isn't CPU heavy, and I like to have the possibility to change things a bit when the mix is starting to get there.
 
Don't you guys print your drum samples? I don't need to automate anything in Trigger because it's gone from my session before I mix. Print samples, if it screws up, change settings and punch in the section that triggered wrong, repeat until you have perfect sample track and then automate volumes against the natural drum track if you want to change the blend. Trying to automate all that stuff sounds like waaaay too much extra time consuming work...

i too like to have full control, changing samples when mixing (different low end etc) is what i do all the time. would be too time consuming printing that stuff over and over again.
 
Considering the ridiculous amounts of CPU power we have in our hands these days, I like to keep as many options open as possible while working during all stages. Trigger isn't CPU heavy, and I like to have the possibility to change things a bit when the mix is starting to get there.

Which is still easy to do when you have printed a perfectly clean sample track with accurate hits and the correct velocities, you can easily trigger from that track with static settings. Why the hell would anyone waste all the effort needed to automate the sensitivity and threshold throughout the whole track? It's so much easier to print even a "blip" track by punching in any parts that need different settings and then trigger from that so you don't have to automate fuck all.
 
Am I the only one whose a fan of the FREE update?

I mean the old waveform display looks cool but is it really that big a deal?

Why would an update to an existing plugin cost anything (unless it's from Waves)? This isn't special, it's par for the course.

And yes, it's a huge deal - I'm stuck using an older version because of how terrible the GUI is, and that version still has bugs/crashes Cubase a fair amount.


Agreed on the topic of printing samples - I can't trust a sampler playing live as much as I can a printed waveform, and things need to be hand-aligned to be in perfect phase, even with Trigger.
 
McDSP is charging for updates too ;)

back OT ... I haven't even updated my version of Trigger forlike 6 months so I think I might be a couple releases behind? Thankfully after reading this thread I'll probably just leave it as is for now :p