suggestion: find common ground / levels of working together with chris from knobcraft

[markusschloesser]

I recently discovered knobcraft ( https://github.com/christofmuc/KnobKraft-orm ) and imho it might makes sense to figure if you can work together. Possible scenarios:

1. use Elektra as a device to remote control knobcraft (e.g. patch selection)
2. use knobcraft for Elektra preset management (can also be offline!)
3. sysex patch management and parsing: I don't know exactly what might come out of it, but I have a feeling that it might be good things :-)
4. etc I really really like that both of your ways of working (open source, using github etc). I will make the same suggestion at his github

[christofmuc]

Hi, I am the author of the KnobKraft Orm sysex librarian, and thank you to Markus for suggesting this! I had discovered the Elektra actually only last month, and really like it - actually I need it ;-)!

I commented some ideas I have in addition to yours in the ticket over at the KnobKraft repo: https://github.com/christofmuc/KnobKraft-orm/issues/23

[christofmuc]

Just to add - I did an experimental integration of Electra One preset management into the KnobKraft Orm - basically what you could do is to also store the Electra Presets in the Orm database, and send them into the Electra. This is item 2) from Markus' list above.

If I understood the sysex docs correctly, the Electra One does allow requesting and sending the "edit buffer" only, there is no way to access the stored presets? What you can do is to rename the patches - the code parses the json and will recreate a new preset with the new name.

If you are interested, this is a deep link to the Electra One code I needed to write.

https://github.com/christofmuc/KnobKraft-orm/blob/master/adaptions/ElectraOne.py

Disclaimer: I don't have an Electra One (yet), so this is untested, but gives you an idea.