Yes, that's what I did. I opened songA.qtr, made changes, and then saved it into another directory naming the new version of the song as songB.qtz
Aside from songB.qtz being a SGML document, the "clips" are still pointing to the original .mid locations. I've been able to work around this by combining all clips on a track into a new clip and then changing the path when prompted. That's fine for now but new clips are still being saved to the original directory location. Is there a way to change the "parent directory" location for a given song?
Overall, I still see what happens behind the "save as" as a very dangerous operation. I can't imagine a casual user would think saving a "forked" version would result in shared data. I'm just glad I know about this from a previous situation since I can now take additional steps to safeguard my work.
Yes, that's what I did. I opened songA.qtr, made changes, and then saved it into another directory naming the new version of the song as songB.qtz
Aside from songB.qtz being a SGML document, the "clips" are still pointing to the original .mid locations. I've been able to work around this by combining all clips on a track into a new clip and then changing the path when prompted. That's fine for now but new clips are still being saved to the original directory location. Is there a way to change the "parent directory" location for a given song?
Overall, I still see what happens behind the "save as" as a very dangerous operation. I can't imagine a casual user would think saving a "forked" version would result in shared data. I'm just glad I know about this from a previous situation since I can now take additional steps to safeguard my work.