I have tried that, but these parameters are not remembered when i restart the standalone app, or the host app (in the case of the plug-in.) Actually, I can't restart the host app (Digital Performer) because the newer beta from about a month ago (that's still the newest, right?) won't pass DP's (or Logic's) AU test.
I was told that these problems would be fixed in the next release. Please correct me if I'm mistaken? thanks.
Until then, I have not been using v.2, but going back to v. 1 which at least remembers controller maps, and will pass AU inspection.
PS - I hope when the parameter mapping IS fixed, the same CC# will work for both the upper and the lower sound in a split or a dual, depending on whichever (upper or lower) is currently in edit mode.
If we have to assign 2 different cc #'s - for example, cc71 to Upper VCF cutoff, and cc72 to Lower VCF cutoff, that will cut in 1/2 the number of controller knobs available, and will make the VI much less like the real hardware synth - which used the same slider (for example) to control VCF, whether it was for the Upper or Lower sound - it didn't have 2 separate sliders - the Upper/Lower switch determined which parameter was being addressed by the same slider.
: )
EDIT - it's been fixed - well, the standalone and au plug ins in J8v2, now recall from one launch to the next, Midi CC assignments. But that's not to say that the Automap/available for automation feature that paulbinns refers to has been fixed/corrected/added. Hopefully they will be revived in an update.
