3 When <dfn>copying a MIDI region</dfn>, Ardour has to decide whether to make the
4 copy refer to the same data as the original or not. If it does refer
5 to the same data, then editing either the copy or the original will
6 affect the both of them. If it refers to an independent copy of the
7 data then each one can be edited without affecting the other.
10 <h2>Changing dependent/independent copying for the entire session</h2>
13 <kbd class="menu">Sesson > Properties > Misc > MIDI region copies are
14 independent</kbd> can be used to control the default behaviour when
15 making a copy of a MIDI region.
18 When enabled, every new copy of a MIDI
19 region results in a copy being made of the MIDI data used by the
20 region, and the new copy of the region will refer to that data.
23 When disabled, every new copy of a MIDI region will refer to the same
24 MIDI data, and thus editing any copy will change the contents of all
28 Changing the status of this option has no effect on the existing
29 dependent/independent status of existing region copies.
32 <h2>Making an existing copy of a MIDI region independent</h2>
34 Context-click on the MIDI region you want to be
35 independent. From the context menu, select <kbd class="menu">MIDI > Unlink From
36 Other Copies</kbd>. The copy is now using an independent version of
37 the data, and edits to the copy will affect only the copy. Other
38 copies will continue to share data.
42 Note that the copied data only covers the extent of the region when
43 the copy is made. If the region was already trimmed and then a copy
44 is made, an independent copy will have no access to data that is
45 earlier or later than the bounds of the region it was copied
46 from. Put differently, if you make an independent copy of a trimmed
47 MIDI region, you cannot "untrim" it to a larger size.