View Issue Details

IDProjectCategoryView StatusLast Update
0001935ardourbugspublic2020-04-19 20:12
Reporterjerome Assigned Tocth103  
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionfixed 
Product Version2.0 
Summary0001935: Layering issue
DescriptionArdour is supposed to be able to record a region on the same track and at the same time than another. Then, depending on opacity, both regions are heard or only the one on top is heard. That is, several layers are supposed to be recordable, so as to modify a part of the track.

This sometimes work on my installation, but after some time (this can be from the creation of the session or appear later), it stops working this way, and each new region created is placed after the one under it.

Moreover, if ardour's behaviour was normal at the beginning of the recording, I have a stack of a few regions in layers. Then it stops working and when I record a new region on top of that, all the regions are unstacked and set one after each other in time, as if layering was not supported anymore.
Additional InformationTo reproduce:

create a new session
create a track
record a region
move playhead back
record again on the same track

Sometimes I get the expected result: two layers.

Sometimes I get what I suspect to be a bugged result: the second layer is recorded up the first (or so it seems to be, considering the place the curves are drawned at) but at the end is shifted until the end of previous region so as not to overlap.

Again, this is not systematic. But after spending some time searching, I can't find any setting that would imply this behaviour.

TagsNo tags attached.

Activities

jerome

2007-10-25 22:50

reporter   ~0004506

Version used is 2.0.5-1~getdeb1.
And it says (built from revision 2234).

cth103

2009-10-20 22:27

administrator   ~0006801

Is this still a problem for you?

cth103

2009-12-04 11:29

administrator   ~0007239

Closing this due to a lack of feedback. Please re-open if it is still an issue.

system

2020-04-19 20:12

developer   ~0021572

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
2007-10-25 22:47 jerome New Issue
2007-10-25 22:50 jerome Note Added: 0004506
2009-10-20 22:27 cth103 Note Added: 0006801
2009-10-20 22:27 cth103 Status new => feedback
2009-12-04 11:29 cth103 cost => 0.00
2009-12-04 11:29 cth103 Note Added: 0007239
2009-12-04 11:29 cth103 Status feedback => resolved
2009-12-04 11:29 cth103 Resolution open => fixed
2009-12-04 11:29 cth103 Assigned To => cth103
2020-04-19 20:12 system Note Added: 0021572
2020-04-19 20:12 system Status resolved => closed