#Data and model coupling pianoteq windows#

Consideration should be given if midi data already exists in CC 11.ģ. Dynamics would be best mapped to CC 11 (expression) and maybe velocity, but again, should be adjustable/optional (already easy to map CC with JSFX). Percussion mapping to general midi is a good default but should be editable.Ģ. I'll also suggest using a single source for notation standards (Behind Bars by Gould has been mentioned elsewhere and is excellent).ġ. Using industry standards (for both notation and midi) is a good place to start. One other thing to take into consideration: some of this indications are applied to all the notes that follow them until a new indication override it, while some others apply only to the not they are attached to.Īs others have said, different libraries have different methods of triggering articulations, dynamics, etc. Being able to assign articulations in a visual and consistent way without having to remember all the keyswitches and channels is a huge workflow improvement.

And then we would simply need an 'articulation lane' in the piano roll editor and we would have a tool as powerful as the Expression Maps in Cubase. Having a way to link the articulations to this would give us a extremely powerful tool. There are three main ways to switch between them depending on the instrument: MIDI channels, keyswitches, and velocity range. While that would be very nice for dynamics, most VSTi used different patches for different articulations. A few points however need to be taken into consideration. This would help very much for drum maps that are all over the place, which means you could list all snare articulations in one group of notes, then all hihat articulations in another group of notes, and so on.

So that we don't have a linear chromatic piano roll, but notes would be reordered/remapped according to the note name file visually - in piano roll view (not notation!). (This is written in raw MIDI but that does not mean the user interface will be.)Ī good idea here, if expanding the note name file type is in order, is to allow us to REMAP the pitches however we see fit. Staccato articulation is linked to the note C0 with volume 127. Meaning, FFF articulation is linked to CC volume 127. We could potentially add a new interface to support mappings like this: For example, a staccato marking triggering a key switch, or a crescendo marking triggering CC volume messages. Linking articulation and dynamics to MIDI messages. A MIDI note with pitch 44 will be displayed in the piano roll with the name 'Hat pedal' and displayed in the notation editor with pitch 62 (D4) and an 'X' note head.Ģ. Meaning, a MIDI note with pitch 36 will be displayed in the piano roll with the name 'Kick', and displayed in the notation editor with pitch 64 (F4). We could potentially expand the existing MIDI note name interface to support mappings like this: Percussion notation, or any situation where the written notation differs from the desired MIDI output.

#Data and model coupling pianoteq windows#

The most useful thing to think about from our point of view is the not the interface seen on the screen, or what dialog windows or file formats are used, but instead the specification of what types of data need to be linked to what.ġ. It's also most helpful to us if the discussion is focused on incremental steps rather than a giant wish list. Please keep in mind that the notation editor is in early development and nothing too exotic will be implemented until the basics of notation are stable. This thread is for discussing potential special MIDI handling features in the notation editor.