Testing

@konsumer I had to set the midi device manually with "-d 2", which took me a while to figure out. in the original js version this was default. you should include it in the options list in the next update for those who don't know...

after that all the commands worked. I only tried it with one pad, but I don't see any reason why it wouldn't work on other controls. the preset was saved and loaded back (again I only changed the value of one pad in the .beatstep file)

thanks! I'll fiddle around with the code and keep on posting issues and suggestions as they come along

Start by inspecting the CLI option definitions and comparing the MIDI device default with the original JavaScript version. Done means the device represented by "-d 2" is included in the options list or default behavior, and the CLI still executes commands and preserves BeatStep presets as reported.

Written by the indexing model from the issue text.