here's the scenario.
I put down a few tracks, make a trkarch, and send it to my collaborator. He opens the trkarch, and adds some bits. Now if he sends me the whole thing back, and I unpack it into the same directory I sent it from, it will overwrite the existing files, including the trkedit file.
not an overly big deal, as we don't destructively edit audio files.
Of course I would lose any tweaks I'd made to the edit since I sent it to him, and it's pretty redundant for him to send me all those audio files back again.
So what I'll have him do is create a copy of the edit, and delete all the old tracks from that copy. Then make sure he *saves* that edit before he exports a new trkarch, as it exports the last saved state of the edit.
Now when he sends me this, I can open it into the right directoy, and copy the tracks into the original edit. This works but is an elaborate and fragile system. Say, for example, that he forgets to save before exports the trkarch, and I overwrite my original audio files with copies that have been trimmed with handles. Or that we both have copies, and his copy number happens to overwrite the version of the edit I was working on etc. etc.
So what I'm asking is you could *please* implement the existing incrementing number system when *unpacking* a trkarch, so that at least the edit files are *never* overwritten?
sorry about the excessive *emphasis* but I just lost yet another song to this little quirk, and I'm not the only person this has happened to (iirc it happened to Lunch Money, but I can't remember, it was months ago)
preferably before T2

