View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007791||ardour||bugs||public||2019-08-23 17:04||2021-04-19 11:48|
|Summary||0007791: Combine & uncombine messes up region layering|
|Description||Sometimes, uncombining a combined region seems to mess up the region layering, changing it so that it effectively becomes 'later regions are higher', even if later regions were layered below before combining them.|
I haven't been able to reproduce this in a test session by just combining & uncombining regions: there's some other piece of the recipe that I don't know yet, but it has happened to me during some fairly extensive editing in a session with four combined regions of ten or so constituent regions each on three grouped tracks.
|Steps To Reproduce||I wish I knew...|
|Tags||No tags attached.|
combine-bug.gif (372,104 bytes)
The fundamental issue: uncombine restores the original regions with their properties before combining.
A related issue is duplicated compounds: Uncombine can vanish those.
Overlap two compounds, then uncombine. The original layering of the compound is restored, but since it's overlapped with another compound it becomes inconsistent. It may even be ambiguous what should happen.
Another bug: Also a compound may have some "missing" layers. e.g. at the time you've made the compound you've combined regions of layer 1 + 3. Elsewhere on the track some layer 2 existed. Uncombine later would try to add a 3rd layer and fail (see gif animation). -- That's likely a won't fix.
Bug still present in 6.5.0:
Edit some region, with superpositions, change the layering, "combine": the layering reset to default in the xx-compound region.