TRIGGER 1.65 UPDATE Available MIDI from AUDIO

pshya, more like fanboy list. YEWW denied MEE on FACEBOOK :cry:

Youre probably in my pending friend requests, I have no idea what your real name is so I don't know who you are :p I pretty much keep Facebook just to people I know in real life or talk to a lot outside of forums, try to keep it more for personal stuff! But tell me who the hell you are and maybe I will allow you access to my Facebook shenanigans.
 
Youre probably in my pending friend requests, I have no idea what your real name is so I don't know who you are :p I pretty much keep Facebook just to people I know in real life or talk to a lot outside of forums, try to keep it more for personal stuff! But tell me who the hell you are and maybe I will allow you access to my Facebook shenanigans.

Julian Mazzola
 
Holy humongous increase in Latency Batman!

I actually had to turn delay compensation On. (glad i have it now) Even when triggering trigger via midi where previously it was unnecessary,
Also there seems to be the very odd note will double trigger, again, didn't use to happen.
 
I think i'll never update my old version with the old gui.
everyhting work fine for me with this one and I like the GUI
 
1.65 is a bit buggy compared to the previous version, it now has a MASSIVE latency (1023 samples) and also mistriggers, even when triggered via midi.. Sort of regretting updating, even though they're not HUGE problems.

Also, when you revert to Factory default setting on the plug-in in Pro-Tools,
The samples are still loaded, and are still triggered even though the GUI doesn't display them. Also I got some weird phase issue in some of my stereo sample. Play fine in instrument maker but weird phase in the plug-in...How can I came back to the previous version?
 
koalamo said:
Quote:Originally Posted by koalamo
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.
Waves ya say... :D
funnycomicupdatecompute.jpg
 
I probably found a bug.
I edited my kick via midi, I triggered it with Trigger and I printed it in a new audio track.
In 1 or 2 hits I noticed that the printed track wasn't aligned with the midi track....like the midi hit was in another position. So I had to reprint the hit...
In fact, when I listened the song through PT everything was fine...but bouncing the whole song to mp3, I heard something wrong or delayed during the playback
 
1.65 is a bit buggy compared to the previous version, it now has a MASSIVE latency (1023 samples) and also mistriggers, even when triggered via midi.. Sort of regretting updating, even though they're not HUGE problems.

Also, when you revert to Factory default setting on the plug-in in Pro-Tools,
The samples are still loaded, and are still triggered even though the GUI doesn't display them. Also I got some weird phase issue in some of my stereo sample. Play fine in instrument maker but weird phase in the plug-in...How can I came back to the previous version?

I've had problems similar to the second one on Reaper as well. Not sure how to reproduce but there has definitely been times where only one sample was shown in the GUI but it was still blending it with another sample from the instance I copied it from and things like that. If the TCI format with all my Slate samples already there wasn't so convenient I would probably ditch this fucking plugin, I've never in my life seen a company struggle so much to put out a solid piece of software.

Is there a crossgrade to Drumagog 5 for Trigger owners? Heh...
 
1.65 is a bit buggy compared to the previous version, it now has a MASSIVE latency (1023 samples) and also mistriggers, even when triggered via midi.. Sort of regretting updating, even though they're not HUGE problems.

Also, when you revert to Factory default setting on the plug-in in Pro-Tools,
The samples are still loaded, and are still triggered even though the GUI doesn't display them. Also I got some weird phase issue in some of my stereo sample. Play fine in instrument maker but weird phase in the plug-in...How can I came back to the previous version?

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.
 
C'mon Jeff...don't foxilize yourself on the GUI thing
Today I worked with some kick parts (16th at 200bpm) and I had no problem at all with the new GUI, also without the zoom.
Moreover if they said that's not possible to switch to the 1.62 GUI, probably there is a reason...but you can't write the same thing in every post you do
 
C'mon Jeff...don't foxilize yourself on the GUI thing
Today I worked with some kick parts (16th at 200bpm) and I had no problem at all with the new GUI, also without the zoom.
Moreover if they said that's not possible to switch to the 1.62 GUI, probably there is a reason...but you can't write the same thing in every post you do

agreed, it could be a legality... it's totally not a DEALbreaker, he's acknowledged the other issues atleast and is always super receptive to us. I'm sure he'd work with us if it were possible on something as simple as a GUI revert.
 
agreed, it could be a legality... it's totally not a DEALbreaker, he's acknowledged the other issues atleast and is always super receptive to us. I'm sure he'd work with us if it were possible on something as simple as a GUI revert.

Yes, but it would be nice just to get a simple "sorry, because of legal shit with WaveMachine Labs we had to change the GUI" to close the matter, rather than just a short, cryptic "we can't do it" (and I don't even own Trigger, I'm just curious :lol: )

EDIT: Or "sorry, but we spent too much damn money on the GUI redesign to not use it, so fucking like it" :loco: