03-08-2019, 09:40 AM
Thanks Darryl!
I have upgraded to 1.1.020
3 is definitely still happening. I am doing the following to test:
- connected via USB only to mac running ableton for routing.
- sync in from USB1 (ableton clock)
- control channel from ableton sending notes C5, etc in a 16 bar loop
- arm the pad and the motif 1 parts
- start ableton:
if pad quantise is on, the pad start is delayed by the value of pad quantise; i.e. it does not catch a note right on the 'down' beat.
with pad quantise off, it starts on the 'down'
Is this enough for you? is there anything else I can provide for you to replicate and isolate this?
Regarding 1 and 2; cool. I'd LOVE it if you got to implementing number 1...as it is its great for 'noodling' in a writing mode, as input to another sequencer.... but not so good for predictable use in a live context.
I have upgraded to 1.1.020
3 is definitely still happening. I am doing the following to test:
- connected via USB only to mac running ableton for routing.
- sync in from USB1 (ableton clock)
- control channel from ableton sending notes C5, etc in a 16 bar loop
- arm the pad and the motif 1 parts
- start ableton:
if pad quantise is on, the pad start is delayed by the value of pad quantise; i.e. it does not catch a note right on the 'down' beat.
with pad quantise off, it starts on the 'down'
Is this enough for you? is there anything else I can provide for you to replicate and isolate this?
Regarding 1 and 2; cool. I'd LOVE it if you got to implementing number 1...as it is its great for 'noodling' in a writing mode, as input to another sequencer.... but not so good for predictable use in a live context.