Stephane Morisse

That's probably trivial but I have a hard time trying to get trigger quantization work. There's something I don't get in delay and pipe use.

If I get it right, the syntax in upper left (mentioned by someone on the ableton forum doesn't work because, to quote delay help about the quantize attribute : 'if the applicable time is a fixed unit (ms, hz, samples etc) this attribute will have no effect'.

Can someone please clarify about delay ? and why pipe doesn't work ?

Edit : think I understood why [toggle] to [pipe] doesn't work : 0 and 1 coming out from [toggle] are ints and are read as the delay time. Is that it ? But then, what is the right way to do this ?

That's probably trivial but I have a hard time trying to get trigger quantization work. There's something I don't get in delay and pipe use.
Please test this :

If I get it right, the syntax in upper left (mentioned by someone on the ableton forum doesn't work because, to quote delay help about the quantize attribute : 'if the applicable time is a fixed unit (ms, hz, samples etc) this attribute will have no effect'.
Can someone please clarify about delay ? and why pipe doesn't work ?

Edit : think I understood why [toggle] to [pipe] doesn't work : 0 and 1 coming out from [toggle] are ints and are read as the delay time. Is that it ? But then, what is the right way to do this ?


trigger-quantize

First you need to set the delay time which then can be _adjusted_ with the quantize attribute.

So you mean that when you use the quantize attribute, the delay value is replaced by the quantize value ? and that the delay value has to be (as I quoted from the help) as a relative value ?

No, the delay value is not replaced but modified (quantized). So in my example, the delay 1n will be made a little shorter or longer such that the output is always sent exactly on a beat (4n), regardless of input timing. This works only with tempo relative values and running transport.

thanks Broc, but it seems I'm can't yet do what I want : I try to trig for example the [record~] object to start recording into the linked [buffer~] from the next 4n note. If I trig it with the [toggle], with the quantize setting for [pipe] set as 4n, just before the 1st time of next bar, it seems that it doesn't start recording on the 1. Am I wrong ?

Be aware that MFL devices introduce audio latency (relative to the buffer size of Live). Consequently, audio received in a device will not be in sync with Live's transport and thus the quantized recording trigger doesn't work as intended. Unfortunately there is no reliable solution I guess.

trigger quantize