TRIGGER 1.65 UPDATE Available MIDI from AUDIO

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.

Can't answer the "why the hell" question, and I'm surely not recommending it to anyone else, but that's how I often work, simple as that :)
 
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.



The weather outside on a given day can crash cubase, that being said I haven't had any problems with it though I've never had any experience with the old gui.

as far as the update goes there were talks that it was going to be a paid update which is why I said it.

Idk on every slate thread I see everyone just bitches about feature updates and problems but no one ever seems to just thank the guy for putting out an amazing piece of software, regardless its not perfect but come on...its a few little lines on a waveform display...
 
The weather outside on a given day can crash cubase, that being said I haven't had any problems with it though I've never had any experience with the old gui.

as far as the update goes there were talks that it was going to be a paid update which is why I said it.

Idk on every slate thread I see everyone just bitches about feature updates and problems but no one ever seems to just thank the guy for putting out an amazing piece of software, regardless its not perfect but come on...its a few little lines on a waveform display...

The weather outside doesn't crash Cubase when simply removing a plugin, like Trigger 1.62 does for me on resource-intensive projects.

Of course we bitch about feature updates and problems - it's a given that it's an awesome piece of software, that's why we bought it in the first place. Having functionality REMOVED from the software with no explanation or apparent reason given AT ALL is a completely different story.

It's not just a few little lines on a waveform display, it's an issue of ease-of-use and workflow that I used to have but was randomly removed in favor of this new POS.
 
You still need to print your samples to make sure they are in phase anyways, Trigger isn't as bad as Drumsgog by any stretch but it's nowhere near perfect enough to trust triggering in real time against a track with any bleed or any less than absolutely perfectly performed hits.
 
The weather outside doesn't crash Cubase when simply removing a plugin, like Trigger 1.62 does for me on resource-intensive projects.

Of course we bitch about feature updates and problems - it's a given that it's an awesome piece of software, that's why we bought it in the first place. Having functionality REMOVED from the software with no explanation or apparent reason given AT ALL is a completely different story.

It's not just a few little lines on a waveform display, it's an issue of ease-of-use and workflow that I used to have but was randomly removed in favor of this new POS.

Fair enough my friend, you have alot more experience than me, I just thought it was alittle harsh just my opinion. :p
 
where can i download the update?
when i go to slatedigital/users and login i only see "VCC" as an option,
even though i own trigger, FG-X and VCC. very confusing...
 
@Adam: Printing doesn't solve the issue. If you want to change the relative balance between your samples for certain parts (let's say you have a very smacky snare blended that you want to tame during softer parts of a song), you need to be able to automate their volumes from within the plugin. Of course, you could tell me "Print the whole track, do your volume change, and then print those softer parts separately" or "Use a different track for your smacky snare", but I really don't like this idea (it's time consuming, you take the risk of losing track of what you've done in your mix, and it's definitely not elegant...). I hope I made clear the reason WHY and you'll be able to find sleep ;)
 
awwwyeah.jpg
 
Slate is one of the very few companys with direct support(here in the forum for example) and Steven seems very interested in things customers would change to make Slate products EVEN better.

Nobody is bitching, the cool fact is that everybody gives input.
 
+1 to Brett and Jarkko. When you're blending 5-6 samples, you want to be able to change and audition the result of changing a whole bunch of parameters such as the dynamics/velocity of each individual sample as well as their levels relative to each other. You need to be able to exchange a sample for another and by not printing you are allowed to do all of these things with a single click, in a matter of seconds.
 
Since everybody neglected to get stoked on awesome new features- lemme get this straight- the new update has drag 'n drop audio to MIDI? You mean...you've effectively made Massey DTM for me in Reaper?? Please tell me that's the case so I can explode with delight and never need to use drumagog (or worse, reaGate) to print sketchy MIDI in real-time ever again.
 
Since everybody neglected to get stoked on awesome new features- lemme get this straight- the new update has drag 'n drop audio to MIDI? You mean...you've effectively made Massey DTM for me in Reaper?? Please tell me that's the case so I can explode with delight and never need to use drumagog (or worse, reaGate) to print sketchy MIDI in real-time ever again.

Dude Trigger has been able to print MIDI in Reaper since version 1. This new feature is actually slower and more finicky than doing it the old way in Reaper.

Turn on MIDI output in Trigger settings screen, right click your audio file and hit "apply track fx as new take (midi)". It bounces the midi file in seconds.
 
Since everybody neglected to get stoked on awesome new features- lemme get this straight- the new update has drag 'n drop audio to MIDI? You mean...you've effectively made Massey DTM for me in Reaper?? Please tell me that's the case so I can explode with delight and never need to use drumagog (or worse, reaGate) to print sketchy MIDI in real-time ever again.

That's what I'm gathering. I'm a bit bummed because I just bought Massey DRT last week, and trigger. Now I find out I may not have needed DRT, and I could have got $50 off trigger. But oh well. I'm lovin Trigger. I'll check out the update after this project is over.
 
So did anyone try the midi drag function??? It f-ing rocks. Its tighter sounding then the previous midi method AND it spits out an actual midi file that you can do whatever with. Also, the triggering engine is definitely easier to work with on really hard to trigger tracks. Full automation on everything coming in next update.
 
Way to change the topic :D

TBH, I got Trigger quite later than most and the GUI is not giving me any problems but the old display does look better I suppose, so I don't see why there shouldn't be an option to toggle between the new and the old GUI.
 
I'm surprised no one's said anything about all the nasty crap and frequencies that happen when you detune drums in older versions of Trigger.

I won't be able to download this atm, but has this bug been fixed in 1.65?