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