Hey, it seems that I came across another bug (the previous one was the range export freeze, which has just been confirmed by hamal).
Say I have 4 or 5 tracks. I enter the range mode in the track editor window, select a given range along the time line, across many tracks (same thing would be to define range markers, and select “Select in range” of the range marker menu). Now, I control-C the whole thing, put the editor head (blue line) to where I want to paste that selection, and control-v at the edit cursor. All regions are pasted but not in the right order. It looks like the order is reversed : the track1 region is pasted to track5, track2 region to track4, etc. Or maybe it’s more random than that. But definitely in the wrong track order. I am using ardour ongoing svn, with VST support on a 32bit intel machine.
Did anyone notice this ? if not, should I file a bug report ?
I cannot confirm/unconfirm the bug, but I can give you a workaround.
There is another way to copy tracks, by simply dragging them holding down the CTRL key while doing so, and dropping the tracks where you want them to be copied to.
I have never tried to copy the way you describe, but imagine that it is better suited for copying over a larger distance. But the method I just described works perfect (with the right order) when copying over shorter distances, using the snap grid.
Mind you what I just described is from the 2.0-ongoing svn branch, and if there is indeed a bug as you described, it might also apply to my method too in the trunk branch.
Hi Deva,
Copying tracks as you mentioned works great but this is not exactly what I am talking about, I specifically refer to copying a time range across tracks. Something is definitely fishy when copying a time range. Try (in your own way) to copy / paste a whole session time range and let me know if your pasted range shows mismatched track-region couples. I did it again in my current session and I e.g. get the tambourine region pasted in the bass track, etc. A real mess …
UPDATE: now I’m a bit confused. I redid it as I described in my first post, and it worked fine …
OK. next time I see a misbehavior, I will take a snapshot right away and post it here … but maybe the misbehaving element is … me
