kortezzzz wrote:Brilliant, Trog
No words. Thank you!
Well, I probably shouldn't take the credit - I think it's something migrated over from my old SM toolbox, so it might well be the work of long-lost gurus from the olden days. It's been that long since I made a VST plugin that I'm rather surprised I even thought to search my toolbox for it!
kortezzzz wrote:Just one more off topic: is there any advantage in using preset array
None that I can think of. In fact, I'd say that keeping them separate would be more useful for a "universal" toobox module. In most cases, you'd want them to have different default values (the module uses an out-of-range value to represent "unassigned"), and it can be useful to have CC bindings stored by the host as VST parameters, but not as part of a preset, so it would be handy to have that option be an independent property.
lalalandsynth wrote:Stupid question ...does anyone use cc to control anything anymore ?
You can bind to any parameter with the daw.
It depends what I'm doing. I've made a few things which I quite often use as stand-alone applications, so there's no choice with those. I use DAW bindings for transport/mixer controls and when I'm explicitly tweaking automation data - it's certainly very handy when you have limited hardware controls. But I'm a big fan of old-school one-knob-per-parameter tweaking, and I don't like switching between "music hardware" and keyboard/mouse/monitor all the time (especially if re-binding involves opening menus and drop-down lists). So for synth bindings, it's just more intuitive to me that my knobs are always controlling the same thing as the music keyboard, and are always the same regardless of which host I'm using - remapping all 60+ controls on my master keyboard can be a bit of a bind (if you'll excuse the pun!
)