Duplicate (Ctrl + B) should only append to the next section if overdub is enabled. If overdub is disabled, then duplicate should overwrite the section its area of influence lands on. Same with copy/paste (Ctrl + C, Ctrl + V). The result of the paste hotkey should also be directed by whether overdub is on or off. This is what overdub is. Dubbing overtop of existing data, to have more data in the same space instead of making the space of longer time to accommodate new data. It's a shame that it's usefulness is only being utilized by live recording and step edit. The long-standing issue with dragging MIDI scores overtop of existing scores and it overwriting them is solved by the overdub button. And these constructive shortcuts are made better (and proper) by it as well.
Paste should not just plop the pasted data beside its Mother data, or where the view happens to be. The user should have precise control over where paste executes. Namely, the beginning of the event/s to be pasted wherever the play header or time selection is (Or if into a different pattern using the channel rack preview window, the exact part in the previous pattern it was taken from; example: if it was copied starting from bar 4, it will be pasted into the new channel pattern starting at bar 4). Overdub enabled or disabled will determine what happens to the potentially existing data in that range. There could also be an 'insert and paste' and 'insert and duplicate' hotkeys too. Inserts the space of however long the data on the clipboard currently is. It will push the later data down range.
A clipboard feature where you can see all your copied data in the clipboard for the current session, and choose which ones are to be pasted next, would be handy as well. With drag and drop to and from the browser window. Drag to the browser will save the MIDI score to the dropped folder. Drag to the clipboard will copy the score to the clipboard, adding it to the existing list of copied data, and ready to be pasted where the user sets the play header/ time selection. With renaming of these clipboard scores.
MIDI notes that land on the same spot as a preexisting note should be discarded, or at least colored red, or another warning color. There should never be duplicates of the same event existing over top one another, without any kind of visual helper warning. Even a thicker border or icon or something.
Events should never be able to be placed over top another event by a left click. If the user wants to overlap an event on purpose, they should have to create it on another spot on the grid and drag it overtop the existing one. (With the result of a visual warning of some kind) There is no protections in FLS at all against hidden duplicate events.
Post your ideas and suggestions here
1 post • Page 1 of 1
[You can only see part of this thread as you are not logged in to the forums]