"Library" version, for incorporating into other interactive programs?

Hi, this looks really useful, thanks for sharing it. I've been working on a Teensy-based sequencer/arranger/Eurorack/USB/MIDI-interface thing for a while, and already have some BeatStep functionality in it ([over here](https://github.com/doctea/usb_midi_clocker/blob/main/include/behaviours/behaviour_beatstep.h)) - for example I can advance the currently playing pattern, change pattern length and direction etc.

I'm interested in adapting your code to handle some of the trickier bits that you've already got working (loading/saving presets would be quite handy, since I find the Arturia software very clunky!). I can see there may be some changes needed to allow this (eg making the getter asynchronous, instead of sleeping while waiting for a response, so that it can be used in an interactive context).

Do you have any plans to take it in a direction like this already, or would I just be better off forking and adapting the code I need?

Cheers,

Review the 16-comment discussion and the existing command-line implementation, then compare its behavior with include/behaviours/behaviour_beatstep.h from the linked project. Before coding, establish an agreed library boundary and asynchronous interaction model; the issue does not currently define a concrete change or completion test.

Written by the indexing model from the issue text.