We will have MIDI support "out of the box" with JUCE. However, when we actually write the driver code for the GPIO stuff, we will end up needing to decide which MIDI CCs our software will respond to.
This means that external MIDI controllers would be supported but their CC mapping would have to be changed to match our which is not possible with a lot of MIDI controllers.
The keys, sustain etc will work, but changing a knob on the external controller wont necessarily change anything in the synth engine (unless the CC happens to line up).
A custom MIDI mapping feature would make it possible to use the synth fully from an external controller.
This could happen at first by reading a file stored on the potato that will set the midi mappings of everything to match up to the synth.
A better solution we can implement later will be proper runtime remapping.
We will have MIDI support "out of the box" with JUCE. However, when we actually write the driver code for the GPIO stuff, we will end up needing to decide which MIDI CCs our software will respond to.
This means that external MIDI controllers would be supported but their CC mapping would have to be changed to match our which is not possible with a lot of MIDI controllers.
The keys, sustain etc will work, but changing a knob on the external controller wont necessarily change anything in the synth engine (unless the CC happens to line up).
A custom MIDI mapping feature would make it possible to use the synth fully from an external controller.
This could happen at first by reading a file stored on the potato that will set the midi mappings of everything to match up to the synth.
A better solution we can implement later will be proper runtime remapping.