Thread: Notation API
View Single Post
Old 02-17-2016, 06:13 PM   #16
snooks
Banned
 
Join Date: Sep 2015
Posts: 1,650
Default

Personally I think making use of named notes for artics makes sense.

Using named notes could give a per-track palette of artics to choose from in the notation editor using data that's already has a sensible place to live with no chance of spelling mistooks. Not showing named notes also solves the other issue of hiding keyswitches.

If the corresponding note (on) for the named note name inserted as an artic in the NE was played when encountered then the problem is solved with minimum fuss. Of course the sending MIDI bit could be done with a plugin, even if just the palette of artics available in the NE was taken from named notes. Ideally though, inserting from a palette of named notes would actually insert a real named note and those could be optionally chased in all MEs (on play and edit).

That way artics can be fully compatible with the PRV, since inserting a named note in the PRV would mean an artic pops up in the NE.

Mapping from notes to CCs/channels or whatever could then be done from a plugin for instruments (or players) that don't do keyswitches. And managing and setting named notes could be a job for a Lua script.

-------------------

Anyhoo, here's a tiny test script that might save somebody a few seconds...
Code:
desc:Notation

@block
while (midirecv_str(offset,#str)) (
   str_getchar(#str,0)==$xFF && str_getchar(#str,1)==$x0F ? (
      //we have a notation event
      match("*_F",#str) ? (
        midisend(offset, $xB0, 64+(127<<8)); //send sustain ch 1 127
      );
      match("*_P",#str) ? (
        midisend(offset, $xB0, 64); //send sustain ch 1 0
      );
   );
   midisend_str(offset,#str); //send everything on
);
... which also brings up the issue that some chasing might be nice for notations plugins use anyway.
snooks is offline   Reply With Quote