Attention:

Welcome to the old forum. While it is no longer updated, there is a wealth of information here that you may search and learn from.

To partake in the current forum discussion, please visit https://forums.presonus.com

Possible design flaw in custom rules

Possible design flaw in custom rules

Postby renochew » Sun Jul 01, 2012 2:36 pm

Hi all,

This is my first post here, I am a new user for notion, very happy about it so far compare with my experience with other similar package.

Anyway, I have problem of setting up custom rules for my kontakt string samples, here is a snippet of the code:

<rule name="pizzicato">
<if technique = "pizz"/>
<channel-change channel="5"/>
</rule>
<rule name="spiccato">
<if technique = "spic"/>
<channel-change channel="4"/>
</rule>

which is pretty straight forward except it doesn't work!

Say, I have a passage which have some spiccato notes follow by pizzicato notes (indicated by express entry in both case). Only spiccato technique are picked up and play probably, meaning Notion ignore the pizzicato technique. The strange thing is if I switch the order of the two rules they appear in the rule files, the passage will play fine. So I guess Notion interpret the rules in a way that the spiccato rules override the pizzicato rules.

Can someone tell me why is that and possible work around?

Thanks!

R
Last edited by renochew on Mon Jul 02, 2012 7:12 am, edited 2 times in total.
renochew
 
Posts: 10
Joined: Sun Jul 01, 2012 2:22 pm

Re: Possible design flaw in custom rules

Postby cbandla » Mon Jul 02, 2012 1:36 am

I've found it useful to set a default sound at the top of the sample selection block. This is from a rule set for using Kirk Hunter's Pop Rock Strings with Kontakt 5 Player.

Code: Select all
   <!-- Select techniques: detache, legato, pizz, trem -->

      <rule name="default_detache">
         <channel-change channel = "02"/>
      </rule>

      <rule name="legato">
         <if condition = "under-slur"/>
         <channel-change channel = "01"/>
      </rule>

      <rule name="pizzicato">
         <if technique = "pizz" />
         <channel-change channel = "03"/>
      </rule>
cbandla
 
Posts: 19
Joined: Fri Nov 04, 2011 3:07 pm

Re: Possible design flaw in custom rules

Postby renochew » Mon Jul 02, 2012 7:27 am

[I have edited my original post, hopefully making the description of the problem more clear]

Hi Cbandla, thanks for the reply, very much appreciated.

I did try adding a default rule, but unfortunately it still didn't work..

I think the problem will manifest when you are using consecutive express entry to denote two playing technqiue. In my case:

spic --> pizz

I guess Notion will maintain the "spic" state even when it read the "pizz" express entry, so if my rules order is something like the following:

pizz rule -> spic rule

The spic rule will eventually override the pizz rule since it appear after the pizz rule. This is my theory anyway and that is what I mean when I said possible design flaw. So the question is, is there any way that I could clear the state of each note before notion start to interpret the rules?

I try using some flag rules to work around the problem, unfortuately, without success.

Again, any help would be very much appreciated. Thanks.

R
renochew
 
Posts: 10
Joined: Sun Jul 01, 2012 2:22 pm

Re: Possible design flaw in custom rules

Postby pcartwright » Mon Jul 02, 2012 8:25 am

There is a file called ExpressionList that is found in the Support > Lists folder. Open this in Notepad or something similar and look for the following block of code:

Code: Select all
  <packet type="EXPD" name="Expression define">
    <property key="exid" name="Expression ident">pizz</property>
    <property key="exor" name="Expression level">130</property>
    <property key="excf" name="Expression conflict">strings</property>
    <property key="sttc" name="Start technique">pizz</property>
    <property key="entc" name="End techniques">arco pizz legn pont tast bhnd</property>
    <property key="uicm" name="UI command">xpiz</property>
    <property key="exct" name="Expression categories">Strings</property>
    <property key="syid" name="Style ID">expr</property>
    <property key="extx" name="Expression text">pizz.</property>
    <property key="exim" name="Expression imports">pizz;pizzicato</property>
    <property key="exsh" name="Expression shortcuts">pizz</property>
    <property key="exxr" name="Expression xrefsym">204</property>
  </packet>


You need to change the "End techniques" to include "spic," something like this:

Code: Select all
  <packet type="EXPD" name="Expression define">
    <property key="exid" name="Expression ident">pizz</property>
    <property key="exor" name="Expression level">130</property>
    <property key="excf" name="Expression conflict">strings</property>
    <property key="sttc" name="Start technique">pizz</property>
    <property key="entc" name="End techniques">arco pizz legn pont tast bhnd spic</property>
    <property key="uicm" name="UI command">xpiz</property>
    <property key="exct" name="Expression categories">Strings</property>
    <property key="syid" name="Style ID">expr</property>
    <property key="extx" name="Expression text">pizz.</property>
    <property key="exim" name="Expression imports">pizz;pizzicato</property>
    <property key="exsh" name="Expression shortcuts">pizz</property>
    <property key="exxr" name="Expression xrefsym">204</property>
  </packet>


This will cause the pizzicato rule to stop once spiccato is applied.
pcartwright
 
Posts: 796
Joined: Sat Dec 05, 2009 2:47 pm

Re: Possible design flaw in custom rules

Postby renochew » Mon Jul 02, 2012 3:07 pm

Hi pcartwright

It works! Thanks a lot!

I can go back to work out my template now, wohoo!

Cheers

R
renochew
 
Posts: 10
Joined: Sun Jul 01, 2012 2:22 pm


Return to Custom Rules Discussion

Who is online

Users browsing this forum: No registered users and 8 guests