1. //! c=short-dark i=spiccato o=cc:32,42/cc:32,48
43 super spiccato
2. //! c=short-dark i=spiccato o=cc:32,42/48
43 super spiccato
3. //! c=short-dark i=spiccato o=cc:32,42,48
43 super spiccato
Only the first syntax is correct. Multiple output events are separated by a /, so #3 is ruled out. And with #2, the second output event is just "48" which isn't valid. So #1 is the right syntax, but ...
In SS I'm able to manually shift-click several articulations so that they're layered, but I can't seem to figure out how to do it in reaticulate. I'm sure I'm doing something wrong but nothing seems to work. Here's what I've tried using both locked UACC and locked UACC KS
... you won't be able to do that using UACC because it doesn't have a way to layer from a MIDI event perspective. You send discrete CC32 events with no real way to signal they should be batched together. I suppose the Spitfire patch itself could have some logic like "if I get N events within 10ms process them all as layered articulations" but it doesn't behave like this.
I was actually going to say something similar about UACC KS. The idea is similar, except instead of CC32 we're sending a single note at different velocities, and the velocity value controls which articulation is selected. (It's
supposed to be the same values as regular UACC but now that I look at it, with the patch I'm testing with, longs have a different number. It's 1 for UACC, and 32 for UACC KS. Sigh.) So it's different than with traditional keyswitches, where you can have a sequence like:
note 30 on, note 31 on, note 32 on, note 32 off, note 31 off, note 30 off
With UACC KS you're sending the same notes:
note 0 vel 30 on, note 0 vel 31 on, note 0 vel 32 on, note 0 off
I actually didn't expect it to layer, but in fact the Spitfire patches do support this with UACC KS. I tested this with Chamber Strings Ensembles:
Code:
//! c=long i=note-whole o=note:0,32
1 long
//! c=long-light i=con-sord o=note:0,7
7 con sord
//! c=long-dark i=sul-pont o=note:0,18
18 sul pont
//! c=long-dark i=note-whole o=note:0,7/note:0,18/note:0,32
126 super combo
And now that I
RTFM (in my defense TFM is pretty new!), layering is explicitly supported. Excellent.
So if you were not getting correct results with UACC KS, the likely culprit was your output event syntax. Hopefully the above examples helps.
I might be tempted to switch all the factory banks over to UACC KS for this reason, except that, it must be said, in past UACC KS was a
complete mess, and I'm reluctant to make that kind of a leap without thorough testing.
Great question!