Hello,
It seems to me that GP provides extensive support for processing incoming MIDI data in scripts, but not as much for outgoing data. I hope I am missing something, but if not, consider this a feature request.
For some background, I have a FCB1010 with the Eureka PROM, which is the only one I know of that allows you to control the LEDs on the FCB1010. The downside is that the PROM uses an unconventional MIDI mapping. Instead of each pedal and LED having its own CC number, all pedals send CC104 when pressed and CC105 when released. The value sent is the pedal number, so pressing pedal 1 sends CC104, value 1. Pedal 2 sends CC104, value 2. Similarly, to control the pedal LEDs, you send CC106 with a value corresponding to the LED number to turn an LED on, and CC107 to turn it off.
This makes it impossible to directly bind the pedals to widgets in GP since each widget expects a unique CC number. I can create a scriptlet that converts incoming midi to something more useable, e.g. when pedal 1 is pressed, the scriptlet converts the incoming CC105, value 1 to CC1, value 127. I can also do this in a Gig file script via InjectMidiEventViaRigManager. However, I can’t find any way to capture midi going to a MidiOutBlock (typically from a widget binding) and convert it before it is sent to the actual MIDI out port. Is this possible?
To summarize, what I need is full bidirectional midi translation between GP4 and an external midi device.
Thanks,
Tom