Hi all... new to the forum!
I took a nice dive into HISE a month ago, primarily for its gui design for use in creating dummy panels of knobs for use in cubase. Combined with cubases Midi Remote API (which links midi i/o for e.g. a mapped hardware controller to control vsts, and vice versa). This combo of midi remote API and HISE has finally allowed me to map a hardware synth to a midi remote API panel (I create), and then link that to a hise panel I've made for that synth... the result is seamless integration of hardware synths in cubase and I'm pumped. Honestly... after decades, this is the first time it's actually been possible without serious caveats...
HISE is a joy to use as a basic gui designer for me. But creating the panel in hise, doing it again in midi remote API, and then a third step of linking each controller one by one is a little tedious (well... mind numbing after the excitement dissipates).
What I've started on is a python script that parses midi parameter and layout data to HISE scripts and midi remote API scripts and links them together (in MR API) in one step. It's beyond proof of concept, but still has a way to go. It's still pretty nifty... tabulated parameters and basic layouts parse nicely in hise default layout and a corresponding midi remote API all linked up in one press of a button :)...
Long read already lol... sorry... I'll get to the point!
Id love to know or explore HISE's own midi out capabilities more to see if i can use HISE in standalone as a synth editor / librarian. There's this thread:
How do I send MIDI to the MIDI output?
I made a simple transposer and built it as a VSTi. When I test the plugin, it has a MIDI out but it does not pass any MIDI. How do I get the MIDI out (both t...
Forum (forum.hise.audio)
Seems promising in terms of basics (HISE can send midi out). So does that mean I can link a parameter to a midi out function and have it send ANY midi message like Cc, rpn, nrpn, sysex... or is it Cc only??
I also think i recall reading that sysex has been dropped for optimising... so i suspect it'll be Cc only or limited??
Possibly a stupid follow up question... but if sysex is dropped, how impossible would it be for me to hack it back into a custom hise build???... is it an API object/function from JUCE framework, or is it a little trickier than just swapping in a more fully functioning midi i/o?
I think it would be handy for standalone and other non midi remote API platforms to have the actual HISE plug capable of sending midi (but I'd need complex long sysex for that to be work as intended).
Sorry for the long first post!