This way, when Notion reads through the rules, the articulations will be switched to, and then none of the following rules will switch away from it.
![ewql symphonic orchestra gold keyswitches ewql symphonic orchestra gold keyswitches](https://flypaper.soundfly.com/wp-content/uploads/2017/06/Hollywood-Strings-e1431613830853.png)
The LAST rule per instrument always unsets the flag. Then, in each articulation rule, I set a flag called "artc." In all of the technique rules (and the reset rule), I then add. The solution to this was to move all of the articulations to BEFORE the reset rule in the rules so that each time through, Notion will hit the articulations if necessary. Unfortunately, there does not seem to be an "if not-articulation" test, because whenever I try to use one the rules file stops working. This way when an articulation like staccato swaps key switches, the rules reset the key switch to the standard one before the next note is played. In the EW rules (and I can't think of a better way to do it), the first rule per instrument is always a "reset" rule which triggers the standard articulation. I forgot to mention: the articulation tests (rather than the technique ones) presented another problem. Is there a better, faster, more code-wise efficient way to do this? Or alternatively, has anyone else run into this "jerky" problem and come up with a different way to overcome it (changing Play's settings, some kind of performance tweak to your system, etc.)? lazerlike42 Posts: 53 Joined: Thu 12:21 pm Each rule has a long list that looks something like this: My solution, then, has been to start a massive re-edit of the rules adding a long list of tests to every single rule to make sure only one key switch is ever activated per note. Now I'm fairly certain it's all of the key switching, because when I edit the rules in such a way as to make sure a particular phrase is not being key switched to death (e.g., commenting out all rules except the one I want enforced), the phrase plays smoothly and as it should. For quarter notes in a row, or even half notes, can present the same problems at times. This seems to be caused by hitting 3, 4, or 5 key switches at a time in between notes - and it doesn't only happen with fast notes. Some notes don't play on beat, others play on beat but are cut short, etc.
![ewql symphonic orchestra gold keyswitches ewql symphonic orchestra gold keyswitches](https://d29rinwu2hi5i3.cloudfront.net/article_media/7791c5b0-329b-433e-9d32-7c5dfc297611/voe_main.jpg)
Basically, you get a very jerky, off-rhythm playback. This creates a problem, at least on my computer - a quad core 2.8 Ghz machine which should be high powered enough to handle Notion and EW about as well as any other.
![ewql symphonic orchestra gold keyswitches ewql symphonic orchestra gold keyswitches](https://www.tbtos.com/wp-content/uploads/2022/01/1642195917_1362250307_choirs.jpg)
If there is then after that yet a later rule that says if the technique is lyrical and under a slur, use key switch 28, it does that too, and is finally on the correct key switch. If there is then yet a later rule that says if the technique is lyrical, activate key switch 33, it does that.
![ewql symphonic orchestra gold keyswitches ewql symphonic orchestra gold keyswitches](https://thumbs.static-thomann.de/thumb/thumb600x600/pics/bdb/462767/13972601_800.jpg)
If there is a later rule that says activate key switch 25 if under a slur, it then activates key switch 25. If the rules file has a rule that first says activate key switch 24 if the flag is vln1, it activates key switch 24. For example, suppose someone has entered a slurred note with the lyrical technique. The way that Notion handles the rules, it goes through from top to bottom and follows every instruction that it encounters, not just the most "complete" one. As I mentioned in a previous topic, I have encountered a problem with the EWQL lite presets.