Unified MIDI editor interface (CC and notes)

[Timtam]

Hello there,

this is kinda a discussion starter which I might have already discussed with Scott, but i'm not sure. I still find it hard to add and properly edit CC events within the MIDI editor. You can only select CCs by cycling through them, which takes... quite a long time really if you want to get to a specific CC lane (maybe i'm missing something here as well). But we do already have the left/right arrow navigation + note preview, which is fine. Why not add the following to this set of features:

• Use the next/previous CC lane shortcuts we already have and add a final CC lane to it - the notes lane. Now the shortcuts will select what kind of events we want to see while pressing left or right arrow in the MIDI editor. E.g. we select CC 11 and instead of seing/previewing notes when pressing left/right we'll jump between CC 11 events within the MIDI item
• Ctrl+F2 will allow us to edit CC events as usualy, that is already there I guess
• Maybe add a dialog which allows us to quickly select a specific lane without having to cycle through all of them, something like the jump to time dialog, but much simpler
• use pitch cursor command to do basically the things we do for notes right now (scroll up/down the note / CC event value) and announce the value that is going to be inserted to the MIDI editor
• change I and Shift+I to insert an event of the type we've currently selected, either note or CC event of the currently selected lane

That'd give a much better and simplified interface that is much more streamlined, and maybe we could clean up the keyboard map in the MIDI editor that way too, although i'm not entirely sure on that one.

Just an idea that keeps floating around in my head here, thought it'd put it out there for discussion.

[ScottChesworth]

There are issues with CC navigation that need fixed in the API covered in #730. Keeping this open because the description of the UI is good.

[MatejGolian]

This is, of course, a good idea. In fact, I believe that someone made a similar suggestion in the past in a comment, although I forget who. As Scott rightly pointed out however, there still are a couple of things that need to be addressed. For instance, I have been requesting a new native Reaper action for setting or inserting CC events at edit cursor, but so far it hasn't generated much traction.

[jcsteh]

One thing to consider is the naming of the commands here. We're essentially overloading the left and right arrows to do two rather different things, especially if you consider that they currently move through chords, not individual notes. So what do we call these commands now? Move to next chord isn't correct. Move to next chord/CC (depending on selection)? Hmm.

Also, we currently rely on REAPER's pitch cursor actions. We'd need to define new OSARA specific actions instead. Same for insertion.