I have this on my list of requests too, it’s difficult to program the mutes from external sequencers like hapax and oxi one. Cc 127 on, 0 off is preferred for any toggle type control, like mute/follow/chord select etc

Thanks for the feedback, I do think I can adjust, but I thought I would bring it up in case there was something that could be done to tweak it. Like I said in one of my other comments, a single click not registering randomly is more problematic because it is a click type encoder. Turning to click should advance the parameter.

Here is the single knob issue: https://www.dropbox.com/scl/fi/7jajhczs5i9td5em6ierg/Single-knob-turns-missing-value-change.MOV?rlkey=x1reehcv9yxna0467wz9snac6&dl=0 Here is the big turn inconsistency: https://www.dropbox.com/scl/fi/4ywfcyto3yjeq9z461rg4/Big-knob-turns-not-consistent.MOV?rlkey=h0cbd3ay1ht24fxgitw293j03&dl=0 If you cant take videos this way please let me know how to submit them, Im watching the youtube link you provided now.

As an add on number 3. I wasn’t looking to do multiple scales or change the global setting for seed or arp generation. Just simply to allow more than one midi channel to send in notes. Specifically to set a channel per arp. I would be sending from a sequencer that also adheres to a global scale but is sequencing devices on different channels.

Thanks 1. On knobs I have tissue paper that tightens them fine, if I have to send back for some other reason I would consider at that time. 2. I can work with how it’s exponential on turning, but it seems less consistent on the larger turns, on big range parameters, trying to fast turn gives different results each attempt, just not as consistent as I prefer but I can work around it. A bigger issue for me is missing single parameter changes on individual clicks. Some turns just don’t register. 3. Thanks 4. Thanks 5. I was thinking, but didn’t mention, mute on release is a good way to work. Which would also let you cue up single or multiple mutes and or solos for single handed operation on the button Combo. 6. Ok, it’s just different than expected that when I stop playing a sequence into it, that another sequence begins, the seed takes over. I can work with it with mutes. 7. I’ll check it out. Thanks for the replies, I am enjoying the unit I just had some thoughts, maybe I am early in my usage to propose changes.

Is it one cc per channel, i think a 16 cc matrix per arp channel would be good. Keep 4 arps with note data and add a cc matrix to sequence for 16 ccs per arp. Then lfo, velocity and pitch are nice, but LFOs/envelopes need a variety of shapes and control parameters to create interesting non basic shapes. Temporal Warp, amplitude, reverse, invert, duration, loop rate synced and unsynced, phase, fold, Sustain point (reaches a point in shape and holds until the next trigger), loop loops within when sustain point reached if enabled. Encoders would be useful to draw our own shapes with the ability to stretch the shape over a time division, then have a looping, single one shot, retriggered or unlinked state. Attenuation, offset and inversion per cc envelope/lfo shape is needed to keep the shape but still be able to attenuate/increase/invert/ positive or negative shift its values. Ability to assign these ccs LFO shapes internally to midicake arp parameters or externally to devices. Copy paste as I imagine if you do the above there are a lot of parameters to tweak that may be repetitive.