If you are in Play Mode then F5 will refresh the playing technique lanes. The rule of thumb for mutual exclusion groups is to ask whether these are techniques that can happen at the same time, or can only one of them be active at a time. For instance, if they select a different vowel or syllable, then only one of them can be active at a time, and so you should create an exclusion group for them. Mutual exclusion groups define what happens when you encounter an instruction in the score, in terms of which previous instructions they cancel.
So for instance with strings, if you had arco followed by con sord, then it’s understood that the con sord doesn’t replace the arco. However a subsequent col legno would keep the con sord but replace the arco.
Thanks Paul,
As I said, I don’t know whether these inconsistencies are because I’m running the computer hard or not. I’ve spent a good few hours trying to resolve this, that I’m going to start a new project and see if I can get the ‘Dominus’ library working by itself. I then will be able to ascertain what’s going on in the more complex score.
The simple rule is – if you have playing techniques which under no circumstances can be logically used together then you should put them in a MEG. There various obvious categories for this such as expression markings in the score like "espressivo"and “leggiero” which would make no sense together or “staccato” and “sostenuto”. With strings, arco and pizz are often quoted. However, if you have done what you can and find you’ve missed something, you can always use the reset switch “nat/ord” which will cancel the playing technique for you and allow you to put in another.
In the PT lane in Play, both the switch and the actual technique name you gave it are shown (just as in “Write” mode when you hover over the articulation in question) I find it much easier in general if both names are the same but there’s nothing to stop you creating a new p.t and allocating it to an existing switch though it confused me when I briefly experimented along those lines!
PS I see just now a new thread has been spreading speculative rumours of a Dorico announcement which I imagine will be neither confirmed nor denied until the time comes. I may be wrong but vaguely remember suggestions from Daniel and/or Paul in another thread on this topic that changes in the way Mutual Exclusion works might not be too far off. Perhaps it might be worth waiting a little if not urgent, just in case something appears which might be useful to you?
PPS I see Paul has beaten me to it in picking up on some of your points.
Thanks dko22 for the reply.
What I’m trying to do on the face of it I could do with a Yamaha QY700 sequencer (which is sitting next to me) over 20 years ago and a sampler. I am simply trying to change the Kontakt key switch of Fluffy Audio’s ‘Dominus’ Choir. The library has 10 slots (allocated to keyswitches). Maybe I’m using the wrong thing (PT) to try to do this. If there’s a better way please let me know. I think there may be something wrong with the PT that I’ve created, because I’ve just started a new project to make sure it wasn’t my struggling PC that was throwing up inconsistencies. I exported the expression map I’d created. I then created a new project and created just 4 players, SATB. I’ve set them up using Dominus (4 instances of Kontakt). I then imported the expression map I’d created and interestingly they don’t show up as PT in the right hand panel when in ‘WRITE’. Neither are they in PT in Engrave or PLAY. However in the ‘Expression Map Data’ window under ‘Techniques and Actions’ the commands are listed as ‘pt.user.key_switch_c0’. Something has obviously gone wrong somewhere in my creation of a PT called ‘Key Switch C0’ and has ‘corrupted’ my export and import of the Expression Map into a new Project.
Has anybody else created new Playing Techniques, created an Expression Map from these then exported them from one project, then imported them into a new Project?
I’ve done all that and at first made the mistake of just saving the Expression Map. When you import it into a completely new project, then you’ll find your custom p.t’s are missing as they are not saved together with the EM. What you need to do is create Endpoint Configurations so everything is saved together. As it so happens, Paul has just written a concise and clear explanation on this topic here
Does that explain at all what’s happening?
Thanks dko22,
I’ll re-visit this after tomorrow but yes, I think I’ve got it with Endpoint Configuration and a template project that holds all the expression maps and any adjustments are are made there. I think I’ll concentrate on getting a template project set up and working, then try creating the SATB subset in the project I want, from Endpoint configurations.