indeed; there just aren't enough hours in a lifetime :)
Yes, my approach is a little strange but sys-ex is a big part of my plugin. I could (should maybe) have gone with a standalone as this is partly an editor / patch manager but it's also an attempt to turn Roland modules into a live configurable
instrument using a midi controller. I had some initial success with routing midi back to the host, but once I started to expand my host list it all became flaky and unreliable (much to the distain of some of my user 'base'). So I borrowed another hero's work
- Les Sanford's Midi toolkit. As long as the user is aware that their DAW can't lock the module midi port everything seems alright.
I'll see what happens with nulling the Audioprocessor but I imagine it'll work with some DAWs but not all; fingers crossed. It's a pain that host implementations are not all equal.
I've tested with Ableton, Sonar 8 and X1, Cubase, VSTHost (of course) and an old version Protools - all good so far. It looks hideous (I'm no graphic designer; it's all windows controls) but its working pretty well. Lots more to do but it's enough to
take back to the Roland groups and re-interest them - hopefully. It might mean that some of them can upgrade from Windows 95 / XP and still edit their modules :)
Kind regards and thanks again for your input and help,