View Issue Details

IDProjectCategoryView StatusLast Update
0004142ardourbugspublic2020-04-19 20:15
Reporterrealhangman Assigned Tocth103  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0-alpha8 
Target Version3.0-beta3 
Summary0004142: Layering does not work properly, esp. with combine, lower to bottom & stacked/overlaid
DescriptionHi, this is kind of complicated. It seems like

- Consolidate region works as expected
- combine does something else (i.e. the result is not what you heard before, it gets the layering wrong somehow)
- Layering -> "Lower to bottom" does only work in stacked view, not in overlayed

- and some weird other things where "overlaid" and "stacked" behave differently but which I don't understand / can reproduce right now.

This all happens in edit mode "most recently added is higher".

I consider this a "major" bug since it's dangerous if you can't rely on the region layering.

I hope I can provide you with some more details and a sample session tonight.
TagsNo tags attached.

Activities

realhangman

2011-06-28 21:10

reporter   ~0010946

First scenario:
You have 2 regions overlapping each other (creating a short crossfade) in overlayed layer track mode. Since the 2nd was recorded later, it is layered above the first one (first/second refers to the time line), so you won't hear parts of the first region.

Now try to raise the first region via the region menu -> layering -> raise or raise to top. Neither works.

If you switch to "stacked" layers via the track menu, using -> layering -> raise to top works, but it is not represented graphically, i.e. the first region is still underneath the second but is played now. Right click the track, and voila, the regions switch graphically to what they should look like (first being above).

If you try the same with the second region (try "lower" and "lower to bottom"), it's the same, just vice versa.

realhangman

2011-06-28 21:24

reporter   ~0010947

Last edited: 2011-06-28 21:28

Second scenario:
Start with the same 2 regions where the later (second) region is higher than the first one, so you won't hear everything of the first region.

"Combine" them, maybe it will work - I had some tests where I heard the first but not the second region during the formerly overlapped part, which is wrong - but then undo the action, and the layering will graphically show the first region to be higher, even if you still hear the correct layering (the secong being higher), but if you then move the first region a but, the layering will change (which is not wanted in recently added is higher mode).

It's strange, I know ;)

realhangman

2011-06-28 21:33

reporter   ~0010948

Note: Just play a bit around with 2 or 3 overlapping regions and combine/uncombine it, it is very strange what happens: Sometimes it works, sometimes uncombine alters the layering, sometimes the graphical and audible layering differ (in overlaid mode), and stacked mode draws an uncombining action somewhere above the track into nowhere. Going to bed now, maybe it's just ghosts.

cth103

2011-12-27 13:11

administrator   ~0012470

The layering code has been change significantly in SVN 11088. It'd be great if you could test and open new bugs for anything that still doesn't work. Thanks!

system

2020-04-19 20:15

developer   ~0022634

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2011-06-28 10:58 realhangman New Issue
2011-06-28 12:06 cth103 cost => 0.00
2011-06-28 12:06 cth103 Target Version => 3.0-beta1
2011-06-28 21:10 realhangman Note Added: 0010946
2011-06-28 21:24 realhangman Note Added: 0010947
2011-06-28 21:28 realhangman Note Edited: 0010947
2011-06-28 21:33 realhangman Note Added: 0010948
2011-11-14 22:45 cth103 Status new => confirmed
2011-11-14 22:45 cth103 Target Version 3.0-beta1 => 3.0-beta2
2011-12-27 13:11 cth103 Note Added: 0012470
2011-12-27 13:11 cth103 Status confirmed => resolved
2011-12-27 13:11 cth103 Resolution open => fixed
2011-12-27 13:11 cth103 Assigned To => cth103
2012-01-10 20:45 cth103 Target Version 3.0-beta2 => 3.0-beta3
2020-04-19 20:15 system Note Added: 0022634
2020-04-19 20:15 system Status resolved => closed