Thanks for the follow-up. At this point, my goal is to simply test the behavior of working with the .qtz format. I'll start by creating a new project in .qtr and then saving it to .qtz for the purpose of making the project portable. I'll document the steps as I go and see where I land...
Create a new project named test1.qtr with the following:
- 3 tracks, each with 4 bars filled with 16th nodes. Each track's notes are sitting on a unique MIDI note number.
- No outputs have been configured as we're only testing how data is saved based on the format used (.qtr or .qtz)
Now, with the .qtr open, I'll save it in the compressed format as test1.qtz
Performing a unzip -l against the .qtz, I can see what I expect in terms of the .qts, and the subdirectory holding the related .mid files
Next, I close everything, move the .qtz to another path and attempt to open it.
This works as expected. This tells me I must have done something dumb and/or reckless when I brought up this issue last week? I'm certain I must have been in a state where the .qts contained references to .mid files that were "outside" the directory of the .qtz itself but I can't seem to piece together the exact steps to recreate the scenario. My takeaway here is that I probably needed to be more careful as I was exploring this awesome feature. I'm totally good with that :)
Thanks for the follow-up. At this point, my goal is to simply test the behavior of working with the .qtz format. I'll start by creating a new project in .qtr and then saving it to .qtz for the purpose of making the project portable. I'll document the steps as I go and see where I land...
Create a new project named test1.qtr with the following:
- 3 tracks, each with 4 bars filled with 16th nodes. Each track's notes are sitting on a unique MIDI note number.
- No outputs have been configured as we're only testing how data is saved based on the format used (.qtr or .qtz)
Now, with the .qtr open, I'll save it in the compressed format as test1.qtz
Performing a unzip -l against the .qtz, I can see what I expect in terms of the .qts, and the subdirectory holding the related .mid files
Next, I close everything, move the .qtz to another path and attempt to open it.
This works as expected. This tells me I must have done something dumb and/or reckless when I brought up this issue last week? I'm certain I must have been in a state where the .qts contained references to .mid files that were "outside" the directory of the .qtz itself but I can't seem to piece together the exact steps to recreate the scenario. My takeaway here is that I probably needed to be more careful as I was exploring this awesome feature. I'm totally good with that :)