The action to explode MIDI note rows to separate items is broken if NON-CC data (pitch bend, aftertouch, program change, etc.) events are contained in it. It creates way more items than necessary in this case, up to more than a hundred if the stream of these events is dense! I didn't notice it until this thread:
http://forum.cockos.com/showthread.php?t=190669. The project is attached in post #25, but this can be recreated even with an empty project and some added MIDI data.
Also, I think it's not a cool behaviour that CCs don't get copied to the exploded items. Say if we have some MIDI CC data in the original item, only the first exploded item gets them, the others get nothing. This is pretty important if pitch bend events are part of the game here.
This action is pretty broken right now, so it needs an urgent fix.
1. It should only create as many items as there are notes in the original item.
2. Each exploded item should get the EXACT copy of all pitch/aftertouch/CC data over.
3. Meta-events (text, sysex, notation) should get their own item. Perhaps it would be better to have a variant of this action that explodes meta-events as well (the current action could ignore them altogether).