View Issue Details

IDProjectCategoryView StatusLast Update
0000865ardourbugspublic2005-02-16 07:22
Reporterv2 Assigned Topaul  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0000865: Crossfade detection can make a whole region seem like it is overlapping
DescriptionI've tested this with:
 * Different regions recorded in the same take (using the channel record
   arming to take multiple punches)
 * Using a region and a copy from it (the other one has to be trimmed a bit)

So the basic situation is that you have two regions matching these rules (I will add more if necessary / I bump into them). The other one has to be shorter than the other one.

If the longer region is moved to the exact same position (the start of the session is the easiest), the whole region will be marked as "crossfadeable". If a crossfade is marked from the context menu, the crossfade will start from the beginning of the shorter region and end at the end of the longer one.

I haven't tested if it's audible, but you can see it happening at least in the gui. A few screenshots to help me make myself clear.. :)

Ardour/GTK 0.565.3 running with libardour 0.861.4

In these cases, having two regions of different length start from the same position, the
TagsNo tags attached.

Activities

2005-01-23 01:01

 

strange_overlap.png (22,643 bytes)   
strange_overlap.png (22,643 bytes)   

2005-01-23 01:01

 

strange_crossfade.png (28,950 bytes)   
strange_crossfade.png (28,950 bytes)   

paul

2005-02-15 03:46

administrator   ~0002017

is this still relevant after recent changes to xfade code?

v2

2005-02-15 21:07

developer   ~0002020

Not relevant. If you'll "resolve" it, I'll close this issue.

paul

2005-02-16 00:37

administrator   ~0002021

see bugnotes.

v2

2005-02-16 07:22

developer   ~0002022

closed.

Issue History

Date Modified Username Field Change
2005-01-23 01:01 v2 New Issue
2005-01-23 01:01 v2 File Added: strange_overlap.png
2005-01-23 01:01 v2 File Added: strange_crossfade.png
2005-02-15 03:46 paul Note Added: 0002017
2005-02-15 03:46 paul Status new => feedback
2005-02-15 21:07 v2 Note Added: 0002020
2005-02-16 00:37 paul Status feedback => resolved
2005-02-16 00:37 paul Resolution open => fixed
2005-02-16 00:37 paul Assigned To => paul
2005-02-16 00:37 paul Note Added: 0002021
2005-02-16 07:22 v2 Status resolved => closed
2005-02-16 07:22 v2 Note Added: 0002022