Hello All,
I'm working on a new rule set for my IRCAM Solo Instruments, and I'm seeing some problems, even with the most basic playback. I've followed the tutorial video and set up "ord" and staccato rules. Both are using <key-switch type="note-on-prefix" ..., but the changes are happening *after* the notes. So, with a bar of 4 quarters, with staccatos on notes 3 and 4, the staccato change happens at note 4, not note 3. If I add more "ord" notes after, the switch back to ord is also delayed by a single note. I've had similar problems to this in Sibelius, and I'm going to be pretty disappointed if Notion just winds up having the same problems as Sibelius. Is there anything I can try? I've removed the Rules folder, just to check that it's being recognized properly, and it clearly is at least *trying* to make the switches (the articulation does change). It's just that the switches are being made *after* the note has already started.
Any help appreciated.
J.
- It is currently Mon Jun 16, 2025 5:12 pm • All times are UTC - 5 hours [ DST ]
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
New rules file problems
8 posts
• Page 1 of 1
Re: New rules file problems
...Just to double-check, I created the same set-up, from scratch, on my laptop, with the same results. The sound changes after the note to which the articulation is assigned. Not feeling good about this, so far...
Mac Pro (Early 2008), 16GB RAM, 10.6.3
Macbook Pro (Mid 2010), 8GB RAM, 10.6.4
J.
Mac Pro (Early 2008), 16GB RAM, 10.6.3
Macbook Pro (Mid 2010), 8GB RAM, 10.6.4
J.
- jbm
- Posts: 14
- Joined: Wed Jun 23, 2010 2:39 pm
Re: New rules file problems
The problem might be UVI itself. Here's a quote from a user review on the NS forum:
"The UVI seems to have a custom keyswitching system which is clearly an essential function. The bad thing is that it doesn't work. The ready-made KS patches do what is expected, but I can't get the UVI to change between normal patches. I can set up the keyswitches but pressing them won't change the articulation."
"The UVI seems to have a custom keyswitching system which is clearly an essential function. The bad thing is that it doesn't work. The ready-made KS patches do what is expected, but I can't get the UVI to change between normal patches. I can set up the keyswitches but pressing them won't change the articulation."
Bill Reed
Notion 4, Sibelius 7.5, Finale 2011/14, Overture 4, Cubase 7.5
Win8 x64, 32GB RAM
M-Audio ProFire 2626
Kontakt, VSL VI Pro, VE Pro, EWQL Orch, Choirs and Pianos
Notion 4, Sibelius 7.5, Finale 2011/14, Overture 4, Cubase 7.5
Win8 x64, 32GB RAM
M-Audio ProFire 2626
Kontakt, VSL VI Pro, VE Pro, EWQL Orch, Choirs and Pianos
-
wcreed51 - Posts: 754
- Joined: Wed Oct 07, 2009 10:50 am
- Location: Berkshires, MA USA
Re: New rules file problems
Well, I don't know about the precise timing of the switches, but they definitely work as expected when played manually at the keyboard. I tested this without any surprises. And, as I say, the switches do happen, they just happen too late. Basically, it's what I would expect to get if I entered "note-on-suffix" instead of "note-on-prefix", I suppose... The change happens *after* the staccato note, not immediately before it.
J.
J.
- jbm
- Posts: 14
- Joined: Wed Jun 23, 2010 2:39 pm
Re: New rules file problems
I had this with EW when I first tried to figure out how the rules worked, but I can't remember what the problem was, but it had to do something with me thinking about it the wrong way. Can yu post the whole rule you have the problem with?
Actualy not just the rule, but the entire section, because the order of the rules is very important.
Actualy not just the rule, but the entire section, because the order of the rules is very important.
- Erufailon
- Posts: 155
- Joined: Sat Jan 30, 2010 2:32 pm
Re: New rules file problems
Well, there really isn't much to it, yet... I've just added a default and staccato, as a test
Hopefully you'll see something obvious, as I'd really like this to work.
Obviously, this is just a section of the file.
thanks,
J.
<plugin id="1431718231"> <!-- Enter PluginID here or use <midi-out id="X"> where X = A,B,C or D for MIDI out port rules-->
<!-- Plugin ID's Menu -->
<!-- Vienna Instruments: 1448299603 -->
<!-- Vienna Ensemble: 1448299589 -->
<!-- Vienna Ensemble Pro: 1987274096 -->
<!-- PLAY: 1886151033 -->
<!-- ARIA: 1195463233 -->
<!-- Miroslav Philharmonik PC : 1346908464-->
<!-- Miroslav Philharmonik Mac : 808536144-->
<!-- IRCAM Solo Instruments : 1431718231-->
<setup>
<velocity-map id="xxxx" /> <!-- choose dynamic map by id -->
<hairpin-map id="xxxx" />
<hairpin-cc value="11" />
<!-- uncomment to set return CC value for hairpins. Useful when both velocity and CC control volume as well as timbre -->
<!-- <hairpin-anchor value="75" /> -->
</setup>
<!-- Example Rules. Feel free to edit, copy and paste to create rules to suit your needs -->
<rule>
<key-switch type="note-on-prefix" midi-pitch="36" velocity="1" />
</rule>
<rule name="staccatto">
<!-- Tests -->
<if articulation = "staccato"/>
<!-- Instructions -->
<key-switch type="note-on-prefix" midi-pitch="37" velocity="1" />
</rule>
</plugin> <!-- use </midi-out> if you used <midi-out id="X"> in the start of the document-->
Hopefully you'll see something obvious, as I'd really like this to work.
Obviously, this is just a section of the file.
thanks,
J.
<plugin id="1431718231"> <!-- Enter PluginID here or use <midi-out id="X"> where X = A,B,C or D for MIDI out port rules-->
<!-- Plugin ID's Menu -->
<!-- Vienna Instruments: 1448299603 -->
<!-- Vienna Ensemble: 1448299589 -->
<!-- Vienna Ensemble Pro: 1987274096 -->
<!-- PLAY: 1886151033 -->
<!-- ARIA: 1195463233 -->
<!-- Miroslav Philharmonik PC : 1346908464-->
<!-- Miroslav Philharmonik Mac : 808536144-->
<!-- IRCAM Solo Instruments : 1431718231-->
<setup>
<velocity-map id="xxxx" /> <!-- choose dynamic map by id -->
<hairpin-map id="xxxx" />
<hairpin-cc value="11" />
<!-- uncomment to set return CC value for hairpins. Useful when both velocity and CC control volume as well as timbre -->
<!-- <hairpin-anchor value="75" /> -->
</setup>
<!-- Example Rules. Feel free to edit, copy and paste to create rules to suit your needs -->
<rule>
<key-switch type="note-on-prefix" midi-pitch="36" velocity="1" />
</rule>
<rule name="staccatto">
<!-- Tests -->
<if articulation = "staccato"/>
<!-- Instructions -->
<key-switch type="note-on-prefix" midi-pitch="37" velocity="1" />
</rule>
</plugin> <!-- use </midi-out> if you used <midi-out id="X"> in the start of the document-->
- jbm
- Posts: 14
- Joined: Wed Jun 23, 2010 2:39 pm
Re: New rules file problems
Nope, I'm sorry, nothing that should make it not work. The only thing is, do you have the velocity map "xxxx" defined? It shouldn't stop it from working, but I just can't try it now, and that's the only thing that doesn't seem normal. I'll try this later, but I have to get to work now. Anyhow, until then, try to define that dynamic map.
Ok, took some time to try this. For me it does nothing, unless I define the dynamic map and the rule-set version. So add this to the beginning of the file if you don't have it already:
These go to the very beginning, before the plugin id:
<?xml version="1.0" ?>
<rule-set version="1">
<dynamic-map id="dvel">
<dynamic dynamic="ppppp" value="0" />
<dynamic dynamic="pppp" value="10" />
<dynamic dynamic="ppp" value="30" />
<dynamic dynamic="pp" value="40" />
<dynamic dynamic="p" value="50" />
<dynamic dynamic="mp" value="75" />
<dynamic dynamic="mf" value="85" />
<dynamic dynamic="f" value="100" />
<dynamic dynamic="ff" value="104" />
<dynamic dynamic="fff" value="112" />
<dynamic dynamic="ffff" value="120" />
<dynamic dynamic="fffff" value="127" />
</dynamic-map>
This should be the final line in the file:
</rule-set>
And of course change "xxxx" to "dvel".
If you already have these then I have no idea what's the problem, I copy pasted your rules, added these and tried it with EWQLSO, and it works as intended. If I don't have these it doesn't even apply the rules, so it's still not the behavior you are experiencing, soo if it doesn't work like this neither, then I have no idea what's the problem, but it's either in IRCAM or the way N3 handles IRCAM specificaly , so contact support then. (And BTW, I know it's stoopid to even ask, but you have the rules inside a "rules" folder in the folder where you have your score saved, right? And you close and reopen N3 everytime you change anything, right (Tho I don't if this is neccesary or not, but I do it anyway) ).
Ok, took some time to try this. For me it does nothing, unless I define the dynamic map and the rule-set version. So add this to the beginning of the file if you don't have it already:
These go to the very beginning, before the plugin id:
<?xml version="1.0" ?>
<rule-set version="1">
<dynamic-map id="dvel">
<dynamic dynamic="ppppp" value="0" />
<dynamic dynamic="pppp" value="10" />
<dynamic dynamic="ppp" value="30" />
<dynamic dynamic="pp" value="40" />
<dynamic dynamic="p" value="50" />
<dynamic dynamic="mp" value="75" />
<dynamic dynamic="mf" value="85" />
<dynamic dynamic="f" value="100" />
<dynamic dynamic="ff" value="104" />
<dynamic dynamic="fff" value="112" />
<dynamic dynamic="ffff" value="120" />
<dynamic dynamic="fffff" value="127" />
</dynamic-map>
This should be the final line in the file:
</rule-set>
And of course change "xxxx" to "dvel".
If you already have these then I have no idea what's the problem, I copy pasted your rules, added these and tried it with EWQLSO, and it works as intended. If I don't have these it doesn't even apply the rules, so it's still not the behavior you are experiencing, soo if it doesn't work like this neither, then I have no idea what's the problem, but it's either in IRCAM or the way N3 handles IRCAM specificaly , so contact support then. (And BTW, I know it's stoopid to even ask, but you have the rules inside a "rules" folder in the folder where you have your score saved, right? And you close and reopen N3 everytime you change anything, right (Tho I don't if this is neccesary or not, but I do it anyway) ).
- Erufailon
- Posts: 155
- Joined: Sat Jan 30, 2010 2:32 pm
Re: New rules file problems
H
Oh, yeah... Sorry, this code was just a pasted excerpt of the complete file. I used the template, so the velocity mapping is unchanged from that. I'll try programming some switches for my VSL stuff, just to check whether it then works as expected.
Thanks,
J.
Oh, yeah... Sorry, this code was just a pasted excerpt of the complete file. I used the template, so the velocity mapping is unchanged from that. I'll try programming some switches for my VSL stuff, just to check whether it then works as expected.
Thanks,
J.
- jbm
- Posts: 14
- Joined: Wed Jun 23, 2010 2:39 pm
8 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 25 guests