MIDI_Sort logic

[meta]

What is the logic used in MIDI_Sort? For example, if I have multiple CC events or notes at the same position, how will they be indexed after the sort?

I will spend some time experimenting and trying to figure it out for myself but would appreciate if one of the devs could clarify this.

[meta]

After doing a bit of experimenting and seeing how the internal midi sorting logic works I've come to conclude that an external representation is not adequate enough to track note/cc indexes. There doesn't seem to be a consistent logic to the sort when notes/cc are at the same position and therefore become impossible to track.

Without this feature, it's impossible to write scripts that require continued granular control over individual notes/cc events. Unless I can tackle this problem my current utility is dead in the water. Does anyone have any other ideas about how to go about this?

https://forum.cockos.com/showthread.php?p=2086022 - I've also made a feature request for persistent references to notes and cc events and would appreciate a +1 to get the devs' attention

[mpl]

I`m afraid this is impossible while REAPER follow MIDI standart mostly (rather than FL Studio customized MIDI implementation, for example).

The only thing came into my mind is a possibility to set flags with MIDI data (currently &1 seleced &2 muted), but i tis not possible at the moment (REAPER does not handle modified flags, probably they left it for the future possible improvents like glide note or something).

[_Stevie_]

@meta: what exactly are you trying to do? Maybe I can point you to a script that does a similar task and you can check the code.

[juliansader]

According to the thread Changing channel of a few notes deletes one (random, not always happening):

Originally Posted by schwa

The order should just be the order the events were added, in other words the order the notes were created.

[meta]

Thanks for your replies guys.

Originally Posted by mpl

I`m afraid this is impossible while REAPER follow MIDI standart mostly (rather than FL Studio customized MIDI implementation, for example).

The only thing came into my mind is a possibility to set flags with MIDI data (currently &1 seleced &2 muted), but i tis not possible at the moment (REAPER does not handle modified flags, probably they left it for the future possible improvents like glide note or something).

As far as I can understand, there are internal data structures already representing individual notes/cc events, these just need to be exposed to the API. While this won't be completely persistent between different sessions, it'll still be more than adequate for my needs.

Originally Posted by _Stevie_

@meta: what exactly are you trying to do? Maybe I can point you to a script that does a similar task and you can check the code.

I'm making a MIDI step sequencer where each step is associated with a single MIDI note. This necessitates keeping track of the individual note itself, regardless of changes to its index in the item.

Originally Posted by juliansader

According to the thread Changing channel of a few notes deletes one (random, not always happening):

Thanks for this, it should solve my problem. There is a complication though. When two notes/CCs are at the same position, and the note which was inserted first is moved away then moved back, its index becomes the highest of all at the same position. I'll spend some time figuring out the best way to factor this into my tracking.