Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 07-12-2016, 10:17 AM   #1
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 3,147
Default MIDI editor: Many actions that refer to "all" events do not affect editable takes

There are about two dozen actions for the MIDI editor that refer to "all" events in their names. The meaning of "all" is however inconsistent, and may mislead new users:

For example, the following two actions affect events from ALL (editable) tracks:
* Edit: Select all CC events in time selection (even if CC lane is hidden)
* Edit: Unselect all

Whereas these three affect only events in the ACTIVE track:
* Select all CC events
* Edit: Select all notes
* Unselect all CC events

I think it would be helpful if the names of these actions could be updated to make their effect and scope clearer.

Last edited by juliansader; 12-28-2019 at 04:45 AM.
juliansader is offline   Reply With Quote
Old 09-09-2016, 12:02 PM   #2
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 3,147
Default

The inconsistencies actually go much deeper than just those actions that refer to "all". Some examples are quite curious:

* "Quantize..." affects all editable takes, whereas
* "Unquantize..." affects only the active take

~ "Split notes" and "Split notes at mouse cursor": all editable takes
~ "Split notes on grid": only active take

# "Invert voicing upwards/downwards": all editable takes
# "Invert (reverse vertically) all notes": only active take

- "Delete notes": all editable takes
- "Delete all notes of less than...": only active take

I suspect that actions that are limited to the active take are mostly legacy actions from the years when REAPER's MIDI editor was not yet capable of multi-track editing.

The hard way to solve these inconsistencies would therefore be to update the code. The easy way would be to simply change the names of the actions.

I have compiled a stripped-down Language Pack that appends either "(active take only)" or "(all editable)" to most of the MIDI Editor actions, in order to make their effects and scope clearer. Other users who may find this helpful, can download it from the stash and install it like a normal Language Pack. (Please let me know if there are any errors.) EDIT: The Language Pack can now also be installed through ReaPack.


P.S. I haven't appended anything to the following actions since I am unsure what they actually do:
- Delete trailing notes of less than ... note in length
- Freeze quantization
- Double length of MIDI (repeating contents)
- Remove selected duplicate events

Last edited by juliansader; 12-30-2018 at 10:16 AM.
juliansader is offline   Reply With Quote
Old 01-24-2020, 04:49 AM   #3
juliansader
Human being with feelings
 
Join Date: Jul 2009
Posts: 3,147
Default

Bumping this, three years later.

Actions that do not work on all editable takes can be quite a headache when working with multiple tracks.

Over the past three years there have been several other bug report threads that report individual actions that don't work with all editable takes, and some of these have thankfully been fixed/upgraded, but the problem requires more than a piecemeal approach.
juliansader is offline   Reply With Quote
Old 01-24-2020, 05:58 AM   #4
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Wooleye, Louisiana
Posts: 2,312
Default

it keeps me from using anything beyond basic actions in the midi editor.

i often suggest to consider the same workflow problems as if they were present when editing same track audio items. can you imagine the frustration if actions applied to multiple selected track audio items only worked on the first audio item clicked?

because that's what we have now in the midi editor.

"end the active/inactive item discrepancies"
__________________
° using REAPER as host/arranger/sequencer to write instrumental beat music.
° striving for a loop-based, controller-centric midi recording/editing workflow.
° justice and equality for editable secondary midi items!
mccrabney is offline   Reply With Quote
Old 01-24-2020, 06:00 AM   #5
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,119
Default

It will be a beautiful day when devs decide to buckle down and just make all actions work on all editable items...
EvilDragon is offline   Reply With Quote
Old 01-24-2020, 06:38 AM   #6
mccrabney
Human being with feelings
 
mccrabney's Avatar
 
Join Date: Aug 2015
Location: Wooleye, Louisiana
Posts: 2,312
Default

__________________
° using REAPER as host/arranger/sequencer to write instrumental beat music.
° striving for a loop-based, controller-centric midi recording/editing workflow.
° justice and equality for editable secondary midi items!
mccrabney is offline   Reply With Quote
Old 01-24-2020, 07:51 AM   #7
ovnis
Human being with feelings
 
ovnis's Avatar
 
Join Date: Oct 2011
Posts: 1,470
Default

Inside the midi editor, distinction between active and inative items should not exist. Simpler and faster...

Last edited by ovnis; 01-24-2020 at 01:50 PM.
ovnis is offline   Reply With Quote
Old 01-24-2020, 07:56 AM   #8
dangguidan
Human being with feelings
 
Join Date: Jan 2019
Posts: 161
Default

In the current situation, the most powerful script can only handle the current take. The editing of multi track MIDI data has always been just needed.
dangguidan is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:30 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.