The MIDI standard doesn't really provide for overlapping notes, so when importing standard MIDI files, REAPER has to guess which note-on event is linked with which note-off, and REAPER will inevitably guess wrong sometimes.
It is best to avoid overlapping notes altogether when working with MIDI. Even while working in REAPER itself, you will encounter problems if you try to run actions such as Humanize on overlapping notes.
EDIT:
That said, REAPER can probably be smarter when guessing matching note-ons. Always assume that the next note-off is matched with the first remaining unmatched note-on.
Also, in order to handle overlapping notes beter, REAPER can move away from the plain MIDI standard, as I wrote elsewhere:
Quote:
Originally Posted by juliansader
REAPER is step-by-step moving away from the plain MIDI standard: First, MIDI events got flags for selected and muted, then notation was added, and now CC envelopes.
Perhaps this is a good time to completely re-think how REAPER stores MIDI data.
In particular, notes can be transformed into miniature "items" that store more than just a note-on:
* Instead of separate note-ons and note-offs, each note event can store the note length. This will avoid all the problems with overlapping notes that get infinitely extended or chopped off.
* Each note can store its own polyphonic aftertouch events, which will allow REAPER to eventually develop something similar to Cubase's "note expression".
* Each note can store its own notation, so that scripts don't have to search the MIDI stream for a matching notation event.
|
Overlapping note import error!
Linear Mode
