Hi. So I managed to sync my Matriarch to Ableton by using Ableton as the master clock. The LED under the Arp/Seq rate knob blinks green, but it's hard for me to understand how the knob works to set the Matriarchs arp and sequencer.
The manual only says that the knob will set it to divisions of the external clock, but it doesn't say what those divisions are, how they map to positions, and if/how they relate to the PPQN global setting. Also I've heard that if you turn the knob while holding shift it uses triplet divisions but can't find anything about this on the manual, except it works like that for tap tempo.
I couldn't figure it out by experimentation. Twelve o'clock doesn't seem to be 1x, the marks on the knob don't seem to mean anything as the rate changes as a I move through them, I can't even tell if the knob is quantized to integer multiples and divisors.
Does anyone know of a post or comprehensive video explaining how all of this works together? Has anyone at least figured out the division and multiplier of the knob for 2 PPQN which is the default?
Thanks!
Need help understanding Matriarch "divisions" on rate/div knob when using external MIDI clock
-
- Posts: 3
- Joined: Tue Feb 02, 2021 11:25 pm
Re: Need help understanding Matriarch "divisions" on rate/div knob when using external MIDI clock
I often find myself wondering the same thing. Generally I just futz with the knob until I find what I'm looking for but yeah, it's a futz.
Would love to see some way of using the keyboard to set the clock division. Maybe while holding the TAP button? That way you could rely on C3 always == 1:1. You could also trigger rhythmic clock jumps live by, say, hitting C3 (1:1) and then C4 (2:1). No idea if the keyboard layout could be evenly mapped to supported clock divisions but...
Would love to see some way of using the keyboard to set the clock division. Maybe while holding the TAP button? That way you could rely on C3 always == 1:1. You could also trigger rhythmic clock jumps live by, say, hitting C3 (1:1) and then C4 (2:1). No idea if the keyboard layout could be evenly mapped to supported clock divisions but...