Non-coder question

[gtrm8kr]

Any way to develop an API toolkit that essentially lets folks tick boxes corresponding to the buttons on your controller, and then the "tool" assembles the code for you?

Brilliant idea or stupid question?

[evanBeta]

I think something like that is far more complicated than you might think.
Sorry for being blunt, but I think it's a stupid question.
The fully documented API is the brilliant idea IMO.

[gtrm8kr]

Sorry for being blunt, but I think it's a stupid question.

No worries. Quick question, though. If my controller has a rotary encoder that I want to control pan, and your (different) controller has a rotary encoder that you want to control pan, what's the difference between the JS I need to write and the JS you need to write for that?

Thanks.

[u-u-u]

If my controller has a rotary encoder that I want to control pan, and your (different) controller has a rotary encoder that you want to control pan, what's the difference between the JS I need to write and the JS you need to write for that?

When the program is made in a clever way it's not more than changing the CC-adress of the encoder.

Of course it depends a little bit on how the specs are in detail:
- is it really just one rotary encoder? Or do you want to control a bank of tracks with a row of encoders?
- some controllers need some sysex message to be in controller mode or something like that. But this is required for only a few controllers.

I think the best would be if you would post a picture of your controller. Then it would be a lot easier to estimate the complexity.

[evanBeta]

Yeah the JS would be the same except for the MIDI CC that it's looking for. If you can change the CC sent out fro the controller, the JS could stay the same.