View Issue Details

IDProjectCategoryView StatusLast Update
0004773ardourbugspublic2020-04-19 20:16
Reporterfarbro Assigned Tocth103  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0-beta3 
Target Version3.0 
Summary0004773: Pitch or Stretch manipulates wrong part of cropped region
DescriptionOn SVN:

1. Create a new audio track with a new region.
2. Split or crop the region on both sides.
3. Stretch it out with the Stretch tool.
4. The region is now stretched but wrong part has been modified. Audio outside the former cropped region is included.

Same thing seems to happen when pitch shifting a cropped region.


Output from debugger:

[New Thread 0x7fffb1fee820 (LWP 5599)]
RBEffect: source region: position = 6985440, start = 33075, length = 105840, ancestral_start = 53633, ancestral_length = 908927, stretch 1, shift 0.890899
StretchCalculator::calculate(): inputDuration 105840, ratio 1.55907, outputDuration 165012 (rounded up to 165181), df size 486
total input increment = 105948 (= 486 chunks), output = 165181, ratio = 1.55908, ideal output 165181
(region total = 165181)
[New Thread 0x7fffd37fe700 (LWP 5600)]
[New Thread 0x7fffd2ffd700 (LWP 5601)]
2 threads created
[Thread 0x7fffd2ffd700 (LWP 5601) exited]
[Thread 0x7fffd37fe700 (LWP 5600) exited]
Did find plugin libardourvampplugins:qm-onsetdetector
RubberBandStretcher::~RubberBandStretcher: joining (channel 0x7fffa410c4c0)
RubberBandStretcher::~RubberBandStretcher: joining (channel 0x7fffa410e440)
Did find plugin libardourvampplugins:qm-onsetdetector
[Thread 0x7fffb1fee820 (LWP 5599) exited]
TagsNo tags attached.

Activities

cth103

2012-06-07 21:02

administrator   ~0013410

Does this still happen? It seems ok to me.

farbro

2012-06-09 22:55

reporter   ~0013452

Nope, it's gone! Awesome!

cth103

2012-06-09 23:08

administrator   ~0013453

Thanks!

system

2020-04-19 20:16

developer   ~0022994

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
2012-03-16 00:21 farbro New Issue
2012-03-17 23:36 cth103 cost => 0.00
2012-03-17 23:36 cth103 Target Version => 3.0 beta4
2012-05-23 15:08 cth103 Target Version 3.0 beta4 => 3.0
2012-06-07 21:02 cth103 Note Added: 0013410
2012-06-07 21:02 cth103 Status new => feedback
2012-06-09 22:55 farbro Note Added: 0013452
2012-06-09 23:08 cth103 Note Added: 0013453
2012-06-09 23:08 cth103 Status feedback => resolved
2012-06-09 23:08 cth103 Resolution open => fixed
2012-06-09 23:08 cth103 Assigned To => cth103
2020-04-19 20:16 system Note Added: 0022994
2020-04-19 20:16 system Status resolved => closed