View Issue Details

IDProjectCategoryView StatusLast Update
0003351ardourbugspublic2020-04-19 20:14
Reporterdanboid Assigned Tocth103  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Target Version3.0-beta1 
Summary0003351: 'Move relevant automation when regions are moved' niggles
Descriptionre 'Move relevant automation when regions are moved' under Edit -> Prefs -> Editor tab - I would strongly advocate we have this turned on by default as I don't understand why anyone would want to move a region with moving its corresponding automation. I'm sure there are cases where someone would want to do that but I'd think they're quite rare.

Secondly, this option only applies to audio tracks as MIDI automation gets moved when you move a MIDI region even when this is disabled.

This was the case as of 7468
TagsNo tags attached.

Activities

cth103

2010-08-03 23:54

administrator   ~0008700

This is a little awkward, as (most) MIDI automation cannot exist without a region, whereas Audio automation can.

danboid

2010-08-04 06:58

reporter   ~0008707

OK - forget about being able to move MIDI automation separately as I don't think I'd want/need to be able to do that anyway but what about the other point I raised as to what should be the default here.

Could someone please explain to me the reasoning behind having 'Move relevant automation when regions are moved' turned off by default? I think Ardour would become more noob friendly having this on by default.

cth103

2010-08-11 02:28

administrator   ~0008800

I can't think of any reasons why we shouldn't default to move-automation-with-regions, but I'm happy to hear them :)

cth103

2010-08-12 00:37

administrator   ~0008813

SVN has patches to modify the automation-follows-regions option description to reflect the fact that it only applies to audio regions. Also automation-follows-regions is now the default.

system

2020-04-19 20:14

developer   ~0022174

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
2010-07-22 09:38 danboid New Issue
2010-08-03 23:08 cth103 cost => 0.00
2010-08-03 23:08 cth103 Target Version => 3.0-beta1
2010-08-03 23:54 cth103 Note Added: 0008700
2010-08-04 06:58 danboid Note Added: 0008707
2010-08-11 02:28 cth103 Note Added: 0008800
2010-08-12 00:37 cth103 Note Added: 0008813
2010-08-12 00:37 cth103 Status new => resolved
2010-08-12 00:37 cth103 Resolution open => fixed
2010-08-12 00:37 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0022174
2020-04-19 20:14 system Status resolved => closed