Hi @jon,
I have a proof of concept running on linux.
It only requires changes to mod-host, all changes are in effects.c.
Basically:
- Adds jack midi output port to mod-host
- Add
int8_t midiOutValueto `MIDI_CC_T’. This will hold the 7 bit normalised param value or -1 for no change. - Change
effects_init()to set allg_midi_cc_list[].midiOutValueto -1 (no value) - Change
effects_set_parameter()to checkg_midi_cc_list[]and ifMIDI_CC_Tmatches parameter setmidiOutValueto correct CC value. - Change
ProcessGlobalClient()and add code to handle Midi Out. Check theg_midi_cc_list[].midiOutValue, if positive then send the midi message and set back to -1.
Automatic connection of the jack output midi port is not yet done, also probably needs a quicker comparison of symbol names in g_midi_cc_list, maybe a simple hash stored.
So now I am at the stage where I thought I would look to build and deploy something to test to the Dwarf and I have hit a bit of a wall. I hoped maybe you could help?
On the dwarf I can see mod-host using jack_lsp but I cannot see a process, I can also see /usr/bin/mod-system-control /dev/ttyS3 1500000 running, I have had a look around but can’t seem to work out exactly what this is.
How is everything setup on the Dwarf?
Next issue is building for the Dwarf, is there a setup somewhere for cross compiling mod-host with the control chain stuff?
Cheers
Andy