kelldammit wrote: however, if i go back to drawing in keyswitches
You don't have to draw them, just create the rules so notion will take care of it. I've even created a rule editor for this purposewith a GUI, so you don't have to write xml files (tho I haven't updated it since the latest 2 patches, due to lack of interest). N3 works, and it is very simple to use, and it is very easy and though it requires a little bit of work while creating your setup, afterwards while composing you only need to compose, and u don't even have to think about any technicality. Truth be told, I'm just surprised, because I did all this when it wasn't even documented. OK, I'm more technical, but still, it wasn't that hard to figure it out for myself. Now it's even well documented, and I just don't know how people can't get it to work. And I even feel sorry about that, because N3 is the easiest solution I know, and I'd hate to see it go down.
Obviously they should make it x64 and they should create a graphical interface to edit rules inside Notion, and on the fly ASAP. If I was CEO of Notionmusic, I'd make this top priority and stop everything else 'till it's done. But I'm not, I'm just a customer, and even though it's not perfect now, it is definietly working as it is, better than anything else.
ccmusicman:
Why couldn't you set it up? Very simple, use a virtual midi cable (for win7 x64 presently the only one I know of is loopbe), and use it to connect N3 to your x64 host (for example cantabile lite, which is free, or directly to EW play). That's it, then you midi-out staff will send their midi messages to you x64 host. Simple.
As for the rules, the documentation isn't that hard. For midi-outs I have a GUI for editing them posted somewhere around here (which was a source of frustration for me, because people keep complaining they can't edit the rules, it's too techy, so I created a GUI for it, so you'd only have to click -I even took the time to learn java just for this-, pretty self-explanatory, yet for the exception of a few, ppl didn't even look at it, just kept complaining), but besides that, u just have to use the if midi-channel expression to decide which channel the rule affects, and you have to write those rules like this:
<midi-out id="A">
<setup>
<velocity-map id="dvel" />
<hairpin-map id="dvel" />
<hairpin-cc value="1" />
</setup>
RULES GO HERE
</midi-out>
Of course you have to define "dvel" as a dynamics map as seen in any examples, and you have to make 4 of these sections, one for each midi-out. Hairpin-cc value is the control code u want the hairpins to affect, in this case I set it to 1, so it affects the modulation wheel, by default the N3 rulesets have it as 11, expression.
And yes, you could also try Jbridge instead of all this, I haven't had any success with it, when I tried, because each instance of play would take 500MB of RAM even when empty, but I haven't tried it with play 2.0, that might behave differently, but I'm not upgrading anything, because my present setup is perfect.