Desired custom rules functionality

[TOSCANINI]

I don't understand a word !
But i'm a 10 000% agree with you !
Let good people increase Notion and let us also pay them for the work they done !

[pcartwright]

dcd111,

I think some of your requests are available. Would you mind engaging in a series of tests to determine which rules do and do not work?

[Admin]

This is a copy paste from the N4 thread about custom rules....

viewtopic.php?f=2&t=2391&start=20

Dear Forum,

This is Josh, at Notion Music.

I want to take this time to respond to this string in regards to some major enhancements to .xml rules. I have just placed the updated rule sets into Notion 4 that allow users of Vienna Special Editions 1-4 to work as Presets. We have also implemented some new functionality for Notion Rules documents to be based on single instruments and instrument channels when working inside of mixing hosts such as Vienna Ensemble and Kontakt Multis, or even EastWest when working in a multi-channel configuration.

As many of you know, Rules documents used to work using a set plugin id which allowed users to control entire plugins, but not instruments. We now have the ability to insert rules based on the instrument staff that you are using. This sets up individual controls for each instrument when dealing with the factory set Key-switches for most of the major VST providers that are available, or the ability to set up your own presets for Key-switches when using other VST's that allow you that type of control.

These new instrument based rules allow you to set up individual instrument control on a per staff basis. You assign the set of rules to a staff and those rules control the Instrument or MIDI Channel on the staff that the rules have been assigned to.

Here is a step by step description of what has to be done to gain the access to the Rule Sets you are working with.

1. Create a Notion Score.
2. Name it and Save it to a New Folder on your Computer
3. Inside the New Folder you have created, create a separate folder called: Rules
-This is an important step because Notion files look for the Rules that you will be using in that specific Rules Folder
4. Go to: http://www.notionmusic.com/support/downloads.html
5. Click the Additional Tab and Download the NOTION3 Custom Rules Playback Documentation
6. Save these documents in the Rules Folder you created earlier

Now, open the documents in the Rules Playback Documentation. You will need some sort of Text Editor to accomplish anything in this document. I find the color coding of TextWrangler to be organized and efficient.

At the top of the Custom Rules text file, you will notice a bracketed string that displays <plugin ID>.


GroupID for Inst.png (17.83 KiB) Viewed 46 times


Change the string <plugin ID="############"> to <group id="xxxx">. This four letter string is associated with the name of the Rule set through the group ID set by the user and placed in the actual score.


group id.png (23.45 KiB) Viewed 46 times


Next, in the score you will need to insert the string on the staff that you want to use the set of rules.


Use Rules.png (20.25 KiB) Viewed 46 times


1. Press Shift + Y
2. Your cursor will now display the "Use Rules" icon.
3. Place the Use Rules icon on the staff/instrument you are wanting to use.
4. Type in the matching four letter string that corresponds to the <group id="xxxx"> for the rule set you want to use.

Here are some Tips on usage:

This functionality works like the instrument change dialogue when you press Shift + I and change an instrument on a staff. Keep your Group Rules together with your Instrument changes. This makes for easy insertion through Copy/Paste and helps keep track of the instruments/staffs/channels you are wanting to control them throughout the score. In the examples above, the Rule Name corresponds to the <group id="vlns">. I have placed the rule on the Vienna Ensemble Staff and I will use the Rules with the group id [vlns] to control the Vienna Instrument, Orchestral Violins.

It is important to keep your rules files organized by name. You will now have multiple sets of rules that you can use to control each instrument separately.

Enjoy.

Josh

[wcreed51]

A copy and paste from above

"Seems from the post Josh from Notion just put up in the "Notion 4 Ship Date" thread that this item at least has been implemented in Notion 4. Maybe this is a good sign regarding custom rules overall, since I thought this was the least likely improvement of the ones I was hoping for."

[pcartwright]

I have a little demo that shows that note-on-prefix and note-off-prefix seem to work as intended. I adjusted my GPO rules so that I only had one instrument with any rules:

Code: Select all

   <!-- Bassoon-->
      <rule>  <!-- reset to normal-->
         <if instrument-id = "13012"/>  <!-- Bassoon-->
         <duration-change amount="0.97" />
      </rule>
      <rule>
         <!-- legato-->
         <if instrument-id = "13012"/>  <!-- Bassoon-->
         <if condition="under-slur" />
         <cc type="note-off-prefix" controller="64" value="127" />
         <duration-change amount="1.1" />
      </rule>
      <rule>
         <!-- not legato-->
         <if instrument-id = "13012"/>  <!-- Bassoon-->
         <if not-condition="under-slur" />
         <cc type="note-on-prefix" controller="64" value="0" />
         <duration-change amount="0.97" />
      </rule>

I then wrote this little line in Notion:

MIDI Test 1.jpg (9.67 KiB) Viewed 8609 times

I exported the MIDI file and imported into Reaper. I then viewed the MIDI event list:

MIDI Test Event List 1.jpg (70.66 KiB) Viewed 8609 times

As you can see, the rules are written so that the pedal control is turned on after the 2nd note sounds (but before it ends). Sure enough, the control comes in just before the third note is sounded (see the first highlighted line). Also, the pedal is reset to zero after the fourth note sounds but prior to the fifth note (see the second highlighted line).

Given that these events are so close together, these changes are almost impossible to view in piano roll, but the list viewer gives the order of the events.

[pcartwright]

Note: the above example also demonstrates that note length multipliers greater than one (1) are ignored.

[fabiolcati]

Note: the above example also demonstrates that note length multipliers greater than one (1) are ignored.

Happy to see it's not me being unable to have it work.

[pcartwright]

There is also the possibility that conflicting rules may be an issue as well. An articulation that triggers a keyswitch or CC change before the note would not work if a rule later in the file for the same articulation triggered the keyswitch or CC after the note.

[pcartwright]

- Proper passing of CC changes to the right channel. This is not really a custom rules issue, because it also applies to the integrated plugins like Miroslav. Right now if either the custom rules or the integrated plugin ruleset developed by Notion changes the MIDI channel, it will not change the channel to which CC data is sent, not even the CC data assigned to hairpin changes. I would be particularly disappointed if this is not fixed in Notion 4, since it affects their own integrated presets for Miroslav.[/i]

I have experienced the same problem, and I do not know a fix at the moment. I do think a workaround is available if this issue is not addressed in Notion 4.

With the expansion of custom rules to group IDs explained by Josh, we should now be able to write rules for VST chain plugins (plugins that can actually host multiple VSTs in one instance which can usually be chained together so the output of one VST feeds the input of the next). In short, I think we could easily add a plugin that copies CC data to all MIDI channels followed by the instrument VST. If there isn't one already, a plugin that copies CC data could be written fairly quickly in ReaJS from Cockos.

It is an extra step, but most VST chain plugins (like chainer and VSTBoard) allow the user to save setups as presets for future use.

[wcreed51]

This might also be of interest...

http://www.bewaryprods.com/software/pro ... sMIDIfier/