Ableton Forum

I've been using MIDI Yoke to trigger clips and the triggered clips have always started one bar after the MIDI note used to trigger them. If I want a clip to start playing at bar 8 I've put the MIDI note on bar 7 and this had been consistent, but I added a new clip and it was launching about a beat early, which was odd, and now after messing around with it a bit other clips have started triggering earlier than expected as well, which throws everything off..

Any ideas on this?

is there any change in the global/clip/default launch quantisation?

Global quantization is set to 1 Bar, All clips have their Quantization set to Global and Default Launch Quantization is set to Global, so I'm not seeing any changes there... I'm seeing some clips behave as if set to Global, some as if set to none, and others just not when I would expect them to...

Maybe I'm missing something, but from what I've seen in the past when I have Global Quantization set to 1 Bar and the Clip Quantization to Global, a clip triggered by MIDI has played 1 bar after the MIDI note triggering it..

Still messing around with this... Setting the Clip Quantization to none for the clips I'm triggering works fine for those, they just play when the MIDI note is played like they should... But...

Triggering scenes is another issue... this worked great when they were triggering on the next bar following the MIDI note used to trigger them, but the way it's working now makes it difficult to trigger a scene without throwing the timing off - this should be (and had been) easy, but I'm lost now...

With Global Quantization set to one bar where should I be placing a MIDI note to trigger a scene after a clip has played through?

It does seem to be this set - checked out another with the same Global and Clip Launch Quantization settings and it is still behaving as it had been - the MIDI notes triggering clips are all set at the first beat of the bar before I want the clips to start playing and the clips start playing on the next bar...

For now I should be able to get around the issues with triggering scene launches using follow actions and some empty clips, and get the clips to trigger at the proper time by setting their Clip Launch Quantization to none...

It would be nice to not have these inconsistencies though, I've spent far too much time trying to figure out what is going wrong here, but for now it appears to be a bug in this one particular set. I'd really rather get this set working correctly than try to replicate what I think is a bug...

I work for a software company so I know that it can be difficult to fix a bug unless you can consistently reproduce it, plus I'm dealing with a third-party app (MIDI Yoke) here which I'm sure complicates things further...