|
|
How do you delete the track, context-menu? global menu?.. Perhaps both tracks are selected when you initiate the delete operation? There should be a dialog asking you if you really want to remove the track or tracks. Does that say "Do you really want to to remove 2 tracks" or just a single track? |
|
|
example.png (62,191 bytes) |
|
|
I've noticed this too. I just attached a screenshot. The track labeled "MIDI 3" was obtained by right-clicking the track labeled "MIDI" and clicking "Duplicate" and using the default options. Then I selected the recording in the bottom track ("MIDI 3") by left-clicking it, and then right-clicked to open the context menu, and took a screenshot. You can see in the screenshot that only the recording in the bottom track is selected (at least that's how it appears). However, when you click "cut", both recordings, the one in the track "MIDI" and the one in the track "MIDI 3", are cut. The same happens if you try to delete only one of them. |
|
|
randomuser226: This is likely normal behavior. The second midi region is linked with the first one. To unlink select the region as shown in your screenshot and hit Alt+1 and then delete it. Result: Only the second region is deleted. Btw. this has noting to to with deleting / removing tracks. |
|
|
If also edit operations are shared, it seems the tracks share the playlist. On the duplicated track use the "P" (Playlist) button in the track-header and use "New copy". That will make the tracks independent. |
|
|
Ah OK, I was confused about the default behavior here, but I see now its in the documentation. (I was just used to other DAWs which make independent copies when you duplicate a track). I guess aurelienbmusic should clarify whether this solves their problem. |
|
|
Sorry for interfere, but can you give me link on this place in manual, which tell about duplicating tracks and sharing playlists. I sometimes have similar problems and I cannot find it in the manual yet. |
|
|
http://manual.ardour.org/working-with-midi/copy-midi-region/ |
|
|
Hi everyone, sorry for late reply, I was not able to try the given solutions and tell about my progress here. But I'm back and will perform a few tests today. Thank you for your help. |
|
|
This has been fixed in git master (not in any release). |
- Anonymous
