Looper with Max For Live ignoring quantization?
Have come up against an interesting problem – When controlling the Looper with M4L – the looper quantization settings seem to have no effect on looper controls triggered by max (record, overdub, play, etc) they occur instantaneously, regardless of the quantize setting.
If you click the same buttons on the GUI, the looper behaves as expected and obeys the quantization setting – record waits to the next bar or whatever you have set to begin recording.
Any experience with this or ideas on how to get it to work properly?
anyone else experience this?
Yep, that always been a problem.
BTW, did you already check this looper ? It works like Looper in many ways, but it creates loops in clips.
Hehe… Just bought your device, Valium. Didn’t have time to test it extensively and I hope the timing is really tight.
I am moving controls for a rack of 8 loopers onto the Push grid with the PDK, and all I have to do is figure out how to get the quatization of the looper (or global as a fallback), and then delay setting the "State" until the quantized time has come. Ideally this would be sample accurate.
I thought I would post a note here, but I guess I’ll start a new thread about sample-accurate timing in M4L.
Does [pipe 128n @quantize 1n] or [delay 128n @quantize 1n] do what you want?
----------begin_max5_patcher---------- 743.3oc2XssabBCD8Y1uBKddaE1.Kr4o1uippHC3MwQfM0XR1zn7uWeA5RRV .mKK4xKVxiGFOywmY7XtakmeFeOowGbF3W.Ou6V44YDoE30M2yuBuOuD2XTy OmWUQXR+010jj8Rib5N.mQ.bAnhKH.VaUFQz.344shl0fZ02CjWRp.3xRklf B9MrLB9+FpjxH47VlwZnNg0BRiZyvRJmctfjKsd5FD56AqAIa0iAcCfe28Q6 DWjo0SuPmYvx7KorKFXh3nM5uKx70vsF6EFNvJzBSXwyt5anM8N4NNSxvUDy R+TPwk8qnhWJqjHMfD7fPdqrWZv.izP+qwHP0Fqkd+pU5g0NdHvH2nbrmbFT KnL4SP1iD8QaMQucL0.infQB93ObAugZ4OMEAlDZhpnnixQFGShR0iwAShIQ yiI0XgRtjHNmvvYkjgffC3UeFfUj71Zh0K8o5bOfeFlcg+AJ+IiRIAY.5DLI jMCxhZgwShZguILoQQFCjr1hPK.x3.pXYTyfJnmIpfNJp.mhu7lhFOL6azXG hBbHQB9ELQxQ.BE4.9D70CedkMP.TFRZ0700DQn8XHM7k2DAJw8lHfweRZhn fThuUYyTF3G+oEyjpcA.YybeanMcGBic891tzfDCpAiRlJO.ldZKR9dQx066 in35k0hcld6V6tnADUaqQiRTi9nQTyZkRNahJpgnC21hlrfZxyHBlisb5hDa 2TSGIwuuQxKr3wXQrSUAB+jUDXrWoQqIOKHp6kI8XDbxJkmVLxI7wnioX0i9 yBlXSK+gfVCuUj2uCcAA3PzUPZjTl4BmA5neW5.ktjVTPXCK7TPazsCYflie 54p6net2r9Cb4bGUd..NG7fdfRmb+YV3Ic4vm.WnOgKm+fbweVN9yiNJlf+r L9iKzmjEyahcvadobGagQbc80pW1zYRiint23JtPOcyZyTJyN0TH1WPtl1qe hQBVntjPptgnUXqvuOci+J89b+p+Av8mc3C -----------end_max5_patcher-----------
Christopher, this is totally killer. I didn’t realize that @quantize would automatically sync with Live’s transport. That’s a huge help!