View Issue Details
|ID||Category||Date Submitted||Last Update|
|0008397||bugs||2020-09-06 00:55||2020-09-21 17:45|
|Reporter||Jose Luis Quiroga||Assigned To|
|Fixed in Version|
|Summary||0008397: Operation "Selected Regions > MIDI > Remove Ovelap" does it for only ONE region.|
|Description||If more than one region is selected the operation|
"Selected Regions > MIDI > Remove Ovelap"
does it for only one region.
|Steps To Reproduce||1. Draw more than one region|
2. Draw a few notes on each region that ovelap.
3. Select the regions
4. RIght click over one of the selected regions and choose "Selected Regions > MIDI > Remove Ovelap"
The most common case is tail to head overlapping. And the usual intention of the user is to have two notes NOT one long one.
Specially when importing multi-track MIDI files like symphonies.
What I find missing in MIDI policy is the policy of NOT removing sounds for the usual intention of the user when "dirty" overlapping happens.
Ardour should just make a new note for every overlapping section.
- 10 notes overlapping in a section? Make the section a new note.
- 2 notes overlapping in a section? Make one new note for that section.
So for the usual case leave three notes: one new one for the overlapping section and keep the non overlapping sections as separate notes.
Do not remove sound (it is almost never the intention of the user).
And give and additional option to remove in selected regions all notes with less than an specific length.
That will let the user sanitize any MIDI file by removing very small new notes generated by the overlapping removal in the most common head to tail case.
Thanks for all your work !
These revisions STILL have the bug:
tarball in webpage
I have not look into it but it seems just a loop limit kind of bug. Fairly straight to solve if it is that.