I’m missing SysEx, Variables and Logic Structures in the MidiHub. I just programmed the things I need with the Bome Midi Translator Pro and it can do all that. Probably MidiHub can do things the Bome cannot do, but for my personal purposes, the Bome serves better for me. There was a lengthy discussion of how to implement SysEx. I think you just can look up there how they’ve done it and implement a similar thing.
Maybe something like a Script pipeline for those who want deeper control?
2 Likes
Was going to say the same thing.
One more here! I’d like using MIDIHub as a translator from CC to Sysex for old synths, like Stereoping hardware controllers. I hope to see this function in next releases.
Thank you
1 Like
THIS!!! +1000000
1 Like
I agree completely, these features should be top priorities!
I fully support your statement. It would be an even more fantastic tool after such upgrade.
Yes please, SysEx would be so great, and for that it really needs some ability to script as well.
Came here to say this.
Script pipe would be best.
At a minimum, if you had a pipe that converted midi cc value to a sysex string with value inserted into the string, that would solve my main issue.
Eg:
In: CC 25 VAL 0-127
Out: 00 00 00 00 VAL 00 00, or whatever other arrangement of fixed string bytes and VAL you wanted. Probably would need some kind of scaling or min/max on in and out since some sysex parameters represent a handful of categories or weird ranges