3 posts
Page 1 of 1
Hello everyone,

here is a little pain the neck about techniques. I must to set normale if i want to change to another technique, seems like the technique is activated forever along time even I choose another technique in the following measures


First, I set "normale" technique to unset all techniques
Second, I set detache, works fine
Third, I set a2, works fine
Fourth, I need to set normale, and then, set detache again.

I have three rules, file attached. I tried to figure out the reaseon behind this behaviour but I don't understand the internal mechanism related to set and unset technique becasue unset seems to do nothing.

Conclusion, once a technique is set, there is no way to unset until normale is included in the score.

Please, anyone can confirm that? Can be interesting if I can avoid the use of normale to clean up my scores a little bit.

Techniques test.prules
(1.5 KiB) Downloaded 8 times
User avatar
by davidsantamauro on Mon May 03, 2021 3:34 am
This has to do with the definition of the technique: what triggers it and what cancels it. These definitions are found in ExpressionList.tpk and the relevant section for your example is:
Code: Select all
  <packet type="EXPD" name="Expression define">
    <property key="exid" name="Expression ident">deta</property>
    <property key="exor" name="Expression level">140</property>
    <property key="sttc" name="Start technique">deta</property>
    <property key="uicm" name="UI command">xdet</property>
    <property key="syid" name="Style ID">expr</property>
    <property key="extx" name="Expression text">détaché</property>
    <property key="exnm" name="Expression name">Détaché</property>
    <property key="exsh" name="Expression shortcuts">deta</property>

Disclaimer: I'm not a technique guru, so the below is from trial and error.

Techniques come in 2 varieties: Note and Continuous. Note techniques apply to a single note or chord and are easy to spot as they have the "Note technique" property in the definition, e.g., gliss-up-down
Code: Select all
  <packet type="EXPD" name="Expression define">
    <property key="exid" name="Expression ident">glud</property>
    <property key="exor" name="Expression level">90</property>
    <property key="excf" name="Expression conflict">gliss</property>
    <property key="nttc" name="Note technique">glud</property>
    <property key="uicm" name="UI command">xgud</property>
    <property key="syid" name="Style ID">expr</property>
    <property key="extx" name="Expression text">gliss. up/down</property>
    <property key="exnm" name="Expression name">Gliss. up then down</property>
    <property key="exsh" name="Expression shortcuts">gliss up down;glud</property>
    <property key="mwvc" name="Moves with voice">True</property>

Continuous techniques stay in effect until they are cancelled and have the property "Start technique" as in the deta example above. All continuous techniques are cancelled by normale but there are certain techniques that cancel others, e.g., the properties of solo:
Code: Select all
  <packet type="EXPD" name="Expression define">
    <property key="exid" name="Expression ident">solo</property>
    <property key="exor" name="Expression level">320</property>
    <property key="excf" name="Expression conflict">solo</property>
    <property key="sttc" name="Start technique">solo</property>
    <property key="entc" name="End techniques">solo tutt a2vc a3vc</property>
    <property key="syid" name="Style ID">expr</property>
    <property key="extx" name="Expression text">solo</property>
    <property key="exnm" name="Expression name">Solo</property>
    <property key="exxr" name="Expression xrefsym">263</property>

... so the techniques tutt a2vc a3vc cancel solo.
User avatar
by lvarodelgado on Tue May 04, 2021 3:58 am
Thanks so much for explain this, this open a new world for me.

I understand that this set up was defined because "a2" can be set within "detache", becasue one technique applies to the style played by the performer and the other one indicate a specific way to read and play the score in that staves or phrase, anyway this logic must be taking into account before rules programming, that file is the key considering that in Notion we can not edit CC data like a DAW without susing the "extra stave trick", so a close understanding of the use of techniques can provide the tools to achieve a proper playing.

So, I need to redefine the rule to be more precise for better consistence between sound performance and score anotations, and set "Solo" after the "a2" phrase ends, but now, the score gain a lot of sense when the player see the anotation "Solo" insted of "normale", and I can avoid the work to hide the "internal operations" in the final score.

That was an amazing post, really.

Thanks a lot.

3 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest