Trigger 1.65 Update Video Preview

[Slate]

Coming next week:

[ame]http://www.youtube.com/watch?v=8VLqGH3d5nU&feature=relmfu[/ame]

 

[ahjteam]

is it free?

 

[Soundlurker]

Cool stuff, though I can already do the midi part by using Cubase 6's new feature. Still it would be quite handy for someone, I'm sure. Are the midi notes that you get from Trigger with a velocity corresponding to that of the actual hit, like in Cubase 6?

 

[AdamWathan]

Neat, I'm worried this is replacing the existing MIDI Out functionality though, please tell me it's not! That could be run offline in Reaper to print midi for a whole song in seconds, even if I had to nudge the resulting MIDI by a few samples.

 

[RichMinerva]

Is this a free update to Platinum & ex owners?

 

[Ermz]

Excellent, been waiting for this one.

Admittedly I've found that even though Trigger currently outputs MIDI notes with a delay - when those same notes are run back in to trigger it, I still get pretty much perfect phase accuracy from the resulting samples. Odd?

When running those same MIDI triggers into SD2.0 or something of the like, I still get an audible delay.

 

[xmortumx]

Looking forward to this update too, but im wondering if this is going to be free?

 

[::XeS::]

If I remember correctly, it won't be free and it will have an ilok2 included.

 

[Trevoire520]

Is there going to be anything else in the update?

 

[mstone564]

The messed up algorithm causing nasty noises when tuning drums in TRIGGER is really all I care about.

 

[Melodeath]

If I remember correctly, it won't be free and it will have an ilok2 included.

I believe you're thinking of FG-X 2.0, not Trigger

 

[Morgan C]

In the current version of Trigger, there's an issue with Articulations.

1) You can only set the articulations for the first sample in the list, the rest will follow suit. So if I have a sample with 3 articulations in slot 1, and choose articulation 3, it'll automatically default to the 3rd (or 2nd/1st if there's no 3rd) articulation for any samples in any other slots. Nice when you've got a room,oh,close sample from the same set, but not nice with different samples.
2) The articulations keep resetting themselves and going back to 1. Can be solved by simply making different .TCI's for different articulations.. but then whats the point of articulations in the first place?

Will these be fixed in this update?

edit: not to take anything away from what's been posted. Seems pretty cool, but just not for me.

 

[Harley Barley]

Is this going to fix random firing in logic?

 

[JeffTD]

This seems to just be a workaround for issues with printing MIDI? I personally still like the old way quite a bit - will we be able to still do that?

To be honest, you can't really tell the accuracy from the video; not zoomed anywhere near far enough in.


I see you've still got the new crappy GUI going - still no chance we're going to get the pre-1.63 GUI back?

 

[006]

In the current version of Trigger, there's an issue with Articulations.

1) You can only set the articulations for the first sample in the list, the rest will follow suit. So if I have a sample with 3 articulations in slot 1, and choose articulation 3, it'll automatically default to the 3rd (or 2nd/1st if there's no 3rd) articulation for any samples in any other slots. Nice when you've got a room,oh,close sample from the same set, but not nice with different samples.
2) The articulations keep resetting themselves and going back to 1. Can be solved by simply making different .TCI's for different articulations.. but then whats the point of articulations in the first place?

Will these be fixed in this update?

edit: not to take anything away from what's been posted. Seems pretty cool, but just not for me.

THIS. Being able to select one articulation for one loaded set and a different articulation for another would be AWESOME. Right now the workaround involves multiple instances of TRIGGER to do this, would improve the workflow big time for me and I am sure others as well. Linking the dynamics/velocity for each is really awesome though.

I also have to agree with Jeff, I haven't updated to a version with the new GUI for the wafeforms in TRIGGER, I think the original style is much easier to work with.