03-03-2017, 05:02 AM
(This post was last modified: 03-03-2017, 01:25 PM by Paul Battersby.)
(03-03-2017, 03:15 AM)Samulis Wrote: The cool part is you can assign it to any CC- just change "11" to anything else (e.g. "1" might be a popular choice too).
I considered CC1, but that's for a mod wheel by default, which I'm already using for another patch. CC11 is labelled as expression, which goes along with CC7 (volume) and I figure those are typically controlled by adjacent sliders because you'll want to move both around at the same time if adjusting volume and expression live.
(03-03-2017, 03:15 AM)Samulis Wrote: You may find you get better or worse results from overlapping the crossfades partially versus completely.
I found that to be true of normal crossfading of velocity layers (for brass at least). For expression (even for brass), it seems best to have a complete overlap because you can set the volume and overlap to anything you want. I can then mix in any amount of each sample I want and adjust it's volume, but I may experiment further with that. I may have phasing issues as I try this on other brass instruments but so far (after minimal testing) it seems to work fine for french horns, solo and section.
(03-03-2017, 03:15 AM)Samulis Wrote: How did you stop normal velocity from affecting the crossfade? Is that automatic?
EDIT: On closer inspection, there is still velocity sensitivity affecting volume. By default, it appears the CC7 slider (in sforzando) sets the maximum volume. That combined with the key stroke velocity determines the actual volume. I removed the velocity sensitive cross fade opcodes so both layers play at the same time, but are faded together based on the CC11 setting. That's why key stroke velocity no longer affects crossfade. Hope that makes sense.
Paul Battersby
My free orchestral sample library: Virtual Playing Orchestra @ http://virtualplaying.com
My free orchestral sample library: Virtual Playing Orchestra @ http://virtualplaying.com