Quote:
Originally Posted by gofer
Although 127 divisions does seem overkill
|
Yeah, that would definitely be impractical. The main benefit for the velocity split naming is for libraries which have differing numbers of velocity layers.
For example, the Vienna Symphonic Library patches I use have anywhere between 1 and 5 velocity layers for the same musical instrument. So if the staccato patch has 5 velocity layers, but the sforzando patch only has 1 velocity layer, you could use the appropriate velocity split preset within REAPER's velocity lane for each patch.
One cool addition to this FR would be a way to have REAPER switch between different velocity or CC splits based on the current Bank/Program values. If you're using a Kontakt Bank with multiple patches loaded into the Bank, sending a Program Change message from REAPER switches the loaded program within the Kontakt Bank. But imagine if REAPER would also switch its velocity or CC lane split state as a result of the Program Change message as well! Your velocity and CC split points would, when configured properly by the user, always match the loaded Program within Kontakt (or whichever sampler you're using for Program changes within a Bank.)
This would mean you would always know how many velocity splits you have, where they're at, as well as what your CC messages would do, such as Modwheel crossfades from piano to forte dynamics or toggling from crescendo/diminuendo.
I'm not sure how to write this into the FR, because you'd somehow have to tell the .ReaBank file to communicate with REAPER to switch the velocity/CC splits based on something like Edit Cursor or Play cursor position.
Any ideas on how/if that could work?