Yea, I've always struggled with the "auto magic" portion of the "save as" work-flow. I don't personally use .qtz but probably agree with the points raised (I briefly skimmed).
Honestly, for as long as I remember, I just settled on using the work-flow as is and then manually "fixing" it. Let's say I have a project that lives in /projects/foo. I'll manually create the /projects/foo/session directory and then 1) move all the .mid files to that session directory then 2) change the session.properties.directory value to that path. The point is, I want my .qtr to live in a "clean" location as opposed to being scattered with among a bunch of other files. Of course, that doesn't really matter (aside from neatness) and doesn't speak to the larger point being made about why it's so disruptive and confusing to simply bootstrap a new project.
I raised the point some time ago which is a bigger deal. The point about that session.properties.directory element requiring an absolute path. That's a big deal because it makes it more difficult to restore a piece of work when restoring on a new system. That system's file system would need to exactly match the system where the data was created in order for things to work. G3N-es, you're not having to deal with that because you're using .qtz files which are (essentially) relative.
All my nits aside, I've always wished saving a work in Qtractor was less user-friendly? Of course, every time I pause to try to think of how I'd like it to work, I realize there are edge cases and I start debating myself. Though, at a minimum, I do think the following would make sense and be more intuitive to work with (when working with .qtr files at least).
Single panel "Save as" dialog where all the data is collected (rather than spreading the work among 2 panels) with no automagic logic.
Resulting .qtr file persists the session path in a relative fashion rather than absolute.
Yea, I've always struggled with the "auto magic" portion of the "save as" work-flow. I don't personally use .qtz but probably agree with the points raised (I briefly skimmed).
Honestly, for as long as I remember, I just settled on using the work-flow as is and then manually "fixing" it. Let's say I have a project that lives in /projects/foo. I'll manually create the /projects/foo/session directory and then 1) move all the .mid files to that session directory then 2) change the session.properties.directory value to that path. The point is, I want my .qtr to live in a "clean" location as opposed to being scattered with among a bunch of other files. Of course, that doesn't really matter (aside from neatness) and doesn't speak to the larger point being made about why it's so disruptive and confusing to simply bootstrap a new project.
I raised the point some time ago which is a bigger deal. The point about that session.properties.directory element requiring an absolute path. That's a big deal because it makes it more difficult to restore a piece of work when restoring on a new system. That system's file system would need to exactly match the system where the data was created in order for things to work. G3N-es, you're not having to deal with that because you're using .qtz files which are (essentially) relative.
All my nits aside, I've always wished saving a work in Qtractor was less user-friendly? Of course, every time I pause to try to think of how I'd like it to work, I realize there are edge cases and I start debating myself. Though, at a minimum, I do think the following would make sense and be more intuitive to work with (when working with .qtr files at least).
oh and yay me, I remembered my forum password :)