Here we have the combination of note markings that would need to trigger different keyswitches (slur, slur + bow marking, slur + tremolo). A bow change would be indicated on a note as either a down bow or up bow marking (although doesn't look like Reaper currently supports that?) similarly, tremolo is a note marking. Legato is notated with a slur between notes. Let's consider these just in the legato category: Here we have a Kontakt instance with 4 patches and about 50 different articulations, but there is some interesting overlap to use as a case-study. Just pulling up my 1st violins from Spitfire's Sable library. In other words, I'd mark the top voice (say) on channel 1 as con sord, and the bottom voice on channel 2 as normale. The "con sordino" and "normale" directions make sense as track directions which would apply to different MIDI channels. I might want channel 1 playing con sordino, and channel 2 playing normale (senza sordino). The use-case I mentioned on the pre5 thread was divisi writing, where I have channel 1 and channel 2 playing different violin parts. I think I see more of a need now than ever to be able to assign a MIDI channel to a specific track text notation instance. This makes sense from a philosophical / purist perspective, but it does, I think, mean that track notation needs to be fully baked because I expect it would be used quite often. When using "channel" coloring, color of articulation is fixed to channel 1 even when note is assigned to other channels.įixing, thanks. The map file entry needs to exactly match how the notation is displayed in the piano roll notation lane, or event list.Ĥ.
The text events need to be in quotes if they have multiple words, not otherwise. I think that's because of the quotation marks. See below where "normale" is not being sent. Articulation events aren't always being properly sent. Track dynamics and track text notation will be chased separately, so the last dynamic and the last text notation will both be sent when playback starts from a new location.ģ. Track notation isn't chased in pre6 but that should be fixed for pre7. Later if we define a default articulation, that would be sent if playback starts while no notes with articulations are playing. This seems consistent with the idea that articulations only affect the note they are attached to. Note articulations should be chased if playback starts while the note is still playing. # spectral peaks: obey peak antialiasing optionįull changelog () - Latest pre-releases ()ġ. # Tempo markers: insert tempo marker box uses current BPM, linear transition state for initial settings # MIDI editor: prevent overeager marquee selecting of text/bank/program/sysex/notation events below another CC lane () # MIDI editor: disregard snap when running actions to insert note or advance cursor using current note length division type () # MIDI editor: display context menu when clicking empty space in piano roll notation lane # Articulation map: don't process articulation mappings during glue () + Transport: improve inserted marker attributes when adding tempo markers from BPM field () + Transport: do not apply unedited text fields when enter is not pressed () + Notation editor: improve tuplet autodetection or you could say (seeing as there are lots of forum post references :)):
0 kommentar(er)
