View Issue Details

IDProjectCategoryView StatusLast Update
0007554ardourbugspublic2020-07-03 05:19
Reporterkmchen Assigned Topaul  
Status closedResolutionfixed 
PlatformKeynuxOSdebianOS Versionstretch
Product Version5.12 
Summary0007554: TRanspose on duplicates error
DescriptionRegion midi transpose multiplicated by the number of copies
Steps To ReproduceCreate a midi region
duplicate it 2 times
select the 3 regions
transpose -1 octave
The 3 regions are transposed down 3 octaves
Additional InformationCould argue that you maight select only one and then tranposition works.
Imagine a big project with hundreds of copies and unlinked copies. You'll have find out whitch are copies, whitch are originals or unlinked...
TagsNo tags attached.


related to 0007542 new Midi Transpose fails on duplicated region 



2018-02-10 05:00

developer   ~0020151

I can confirm this issue in the 5.12 release.


2018-02-10 05:19

developer   ~0020152

Also present in master@8046f40f1


2018-12-16 18:09

reporter   ~0020536

Same issue here with semi-tones also in 5.12. This is an unexpected behaviour.

I guess the expected behaviour would be for the transpose routine to run only once on every unique midi region, not once for every copy of the region (which cause them to be transposed multiple times).


2020-05-24 22:23

reporter   ~0024262

Bumping this - still reproduces in Ardour 6.0.rc1.332 (rev 6.0-rc1-332-ga9fff59229)


2020-05-31 09:16

reporter   ~0024318

I confirm that the bug is also observed in Ardor 6. And this is actually a terrible bug.


2020-07-03 05:18

administrator   ~0024579

Fixed in commit ad6de3c23371 (Ardour 6.0-196-gad6de3c233)

user "error" : "select the 3 regions" ... code error: fixed.


2020-07-03 05:18

viewer   ~0024580

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.


2020-07-03 05:19

administrator   ~0024581

Note that if you make linked copies then edit them enough, this may still break. However, this is such intentional behavior that I'm not going to put in the (extremely complex) code that would be needed to stop it from doing that was happening before the fix for this bug.

Issue History

Date Modified Username Field Change
2018-02-10 03:14 kmchen New Issue
2018-02-10 05:00 timbyr Note Added: 0020151
2018-02-10 05:00 timbyr Status new => confirmed
2018-02-10 05:00 timbyr Relationship added related to 0007542
2018-02-10 05:19 timbyr Note Added: 0020152
2018-12-16 18:09 bilka412 Note Added: 0020536
2020-05-24 22:23 lutzky Note Added: 0024262
2020-05-31 09:16 inFlowiaLab Note Added: 0024318
2020-07-03 05:18 paul Assigned To => paul
2020-07-03 05:18 paul Status confirmed => resolved
2020-07-03 05:18 paul Resolution open => fixed
2020-07-03 05:18 paul Note Added: 0024579
2020-07-03 05:18 anonymous Note Added: 0024580
2020-07-03 05:18 anonymous Status resolved => closed
2020-07-03 05:19 paul Note Added: 0024581