Yes, I'll add sample scores and manuscript papers ASAP.
As soon as I get a chance I'll throw together an example score to demonstrate concepts, plus people could export the dictionary as a style.
In fact, if someone has a Sibelius score of a nice orchestral piece (or a portion of one) that also has soloists representing all the string sections I can get permission to include with the soundset (or maybe something in Sibelius format from the public domain) It'd speed things up for me big time! Please email it to me or throw up a link :)
Meanwhile, I'll attempt to better explain the logic.
First understand that by default Sibelius already adds some common nodes as they occur in the score.
If there is a staccato dot on a note it adds the node "staccato".
strings.violin.staccato
If there is slur on a note it adds, "legato".
strings.violin.legato
If there is a housetop it adds, "marcato".
strings.violin.marcato
If a note has both a staccato and a slur it adds "portato".
strings.violin.legato.staccato.portato
And so on....
Note you CAN change these defaults in your Playback Dictionary, but unless you have a special case, you don't need to with my soundset. Instead, we just add sticky stuff on the end.
My sticky nodes are designed so that they get tacked onto the end of these defaults.
I.E.
Lets say you set a couple of my sticky nodes like "stacc" and "lmart"...they are intended to stay there. So as Sibelius goes through the score it sends stuff like:
strings.violin.stacc.lmart (No match, plays default sustain)
strings.violin.legato.stacc.lmart (Closest match is legato, so CC68@127)
strings.violin.staccato.stacc.lmart (Match! Staccato key switch engages)
strings.violin.legato.staccato.portato.stacc.lmart (Match! Martele key switch engages)
strings.violin.pizzicato (Match! Pizz key switch engages).
etc...
My soundset is watching for this particular match in order to use the 'staccato key switch' provided by new GOS strings.
+staccato +stacc
If there's no short bow mode like "+stacc, spicc, mart, etc.", when Sibelius sends "strings.violin.staccato", then it's going to pick my default staccato assignment that's listed under just:
+staccato (I just use a long attack on the regular sustained sound with a short release time)
I've also got ARIA settings in the Soundset's switch types for matches like:
+staccato +mart
+staccato +saut
+portato +lmart
+portato +lsaut
And so on.........
(feel free to open up the soundset in an xml or text editor and look at it...learn from it, add to it, etc.)
When you build an instruction in the playback dictionary you can choose if it will only apply for a single note, or if the node gets 'sticky' and remains part of the stave's SoundWorld ID until such time as you drop the node or send a [reset].
As a general rule of thumb, in this particular soundset if I've given a node a 'shortened' name (I.E. spicc instead of spiccato), it's intended to be able to serve as a sticky node and change 'default interpretation of notes marked staccato until that spicc node is dropped and possibly replaced with something else (I.E. stacc)', so you don't have to go through an entire score and mark every single individual note you'd like played spiccato. Instead, all you need do if you want to change from spiccato to martele, is build a technique or expression that that drops the spicc node and adds the mart note ( -spicc +mart ). From that point on all notes marked staccato (that do NOT live under slurs, use lmart for the notes living under slurs) become martele.
If I've spelled out a node in full. I.E. "marcato", then you should NOT use it as a sticky node. Instead set such techniques, expressions, or symbols to only apply it to the note it is attached.
Here's an example excerpt from Richard's score (I hope he doesn't mind).
https://postimg.cc/image/yh9ef0yvh/
And here you can see playback dictionary entries:
long: (Notice how I drop the other attacks -short, -shorter, shortest, etc...)
https://postimg.cc/image/413hgwdcd/
shortest: (Notice how I drop all the other attacks).
https://postimg.cc/image/nzjcj9y19/
martele: Notice how I drop all the short bow nodes (-saut -stacc -spicc, etc).
https://postimg.cc/image/ywko81kst/
staccato: Notice how I drop all the other short bow nodes...
https://postimg.cc/image/imui55a4t/
Obviously all the nodes I'm dropping in my example techniques above are not always set (my goal is to only ever have ONE of them set at a time)...I just go ahead and put them there so IF they were active they'd get dropped. I can keep using this same technique over and over again in my score this way.
I could have also done something like this, but chose not for the sake of our Con Sordino stuff (would have to reset the +mute all over again if it were applied):
long: [reset] +long
martele: [reset] +mart
As that [reset] clears all nodes down to the default SoundWorld ID for the stave (In this case, strings.violin).
Notice how I just tag the first note in a series that I want played martele, later when I want to change that to staccato I just add a "stacc" technique which adds a +stacc node (while dropping any other relative nodes to staccato notes). It stays 'staccato' until I later change it to something else :)
I know it would seem to make more sense if I'd just spelled everything out in full (spiccato, staccato, etc.) and let Sibelius do all the math where it can. The problem there is YOU don't get much flexibility or control over things that way (sometimes a dot under a slur should mean martele, others it might should mean sautille or staccato, etc.), plus you'd have to spend far much more time tagging every little individual note in the score that you'd want to 'over-ride' Sibelius on. |
GPO5 Soundset Example.sib
Capture d’écran 2019-10-24 à 14.19.37.png