this thing is so good. i was trying to approach like a looper but the one shot mode (and envelope previews) has seriously broken my brain. have not had time to look at code yet.
i’ve hit a bug a few times: something weird with the alternate rec buffers.
i had something going in buffer 1 and switched to buffer 2. recorded into buffer 2, then switched bank 2 to buffer 2 using alt. all pads display buffer 2 on the grid , but the first handful play back sound from buffer 1, and in and out display goes haywire. i had pattern recording enabled on the arc when i recorded and suspect that may be involved but can’t reproduce.
filters:
we were talking past each other on this one, sorry! my suggestion was specific to the UI, let me try to rephrase:
“problems”:
a. HP and LP share freq value, so switching from LP at ‘full bypass’ to HP results in a muted signal instead of a bypassed one.
b. sweeping through the freq value on the arc appears to be linear–a change between 10k-12k takes identical input as one between 0-2k, but human ears are much more sensitive to the latter. (assuming these values have some computery meaning and aren’t literally hz, but holds true in practice)
c. the arc has so much resolution that performing a complete filter sweep takes a long time, and commonly, what you’d want is at the very end of the sweep.
d. both low and high passes are extremely useful tools depending on the material
“a solution”:
at the script level, make low pass and high pass accessible from the same knob, by default at bypass, and scale them exponentially instead of linearly. when the knob is in bypass state, counterclockwise input sets the filter type to lowpass and sweeps down exponentially from 12k, while turning clockwise sets filter to high pass and sweeps up from 0 exponentially.
makes more sense as a video:
(on the op-z, the little flash of green is the bypass state.)
a couple fresh suggestions:
–some kind of visual indication of bpm if quantize is on but set to internal. (would love to be able to extrapolate bpm from duration of a looping pad but could accept that this is too niche 
)
–during pattern, check for key press on banks when performing zilchmo gesture, if a key is pressed, apply zilchmo to the pressed pad rather than active step. (use case: changing the octave of a specific pad without affecting other pads, kind of a simplified param lock)
sorry for the wall of text, this thing is really exciting… fingers crossed once winter break obligations wrap up i will be able to help out a little on some quality of life improvements! at minimum i know once i have my head around the code it will be easier to explain.
