vst~ and SysEx and you.
Jan 13 2020 | 11:48 am
I'm posting to call attention to what seems to me to be a limitation of the vst~ object in that it cannot accept sysex data.
I'm also posting to humbly request that this limitation be lifted. Perhaps doing so by default could cause compatibility or stability issues - so maybe a switch to enable at user risk and user control?
Too risky? Then a separate object, say . . . sxvst~ that the user would have to invoke specifically.
I'd be interested to know if there's much support for such capability. I have specific reasons for needing this, but surely I can't be alone?
Anyway, thanks for taking the time to read, hope some folk will help form a discussion around the topic.