1_
Saving versions becomes dangerous. If I modify a MIDI file in version 5 (or worse still, rename the session), all previous versions are broken, rendering the functionality useless.
2_
The problems with dependency files that can disappear at any given time.
...
Back to the post:
I think I've found a smooth way to solve this.
The default project folder is set by the template. I think this isn't documented, and it was driving me crazy: where does that default "proyect path" value come from?... But I finally figured it out.
The way I solve it: The project path in the templates is,
myPath/Projects/.TEMP
This is how I tell Qtractor that I want all temporary recordings to be saved there.
When it's time to record, the annoying session window appears.
I put anything in the name. For example, "x".
The reason for the annoyance and the "x" as the solution:
1- I'm testing workflows: the project isn't meant to be saved, it doesn't need a name.
2- I'm doing improvisation exercises: the project isn't meant to be saved, it doesn't need a name.
3- I'm inspired. I know I want to do something to be recorded, but I don't know what it is yet. It will be defined as I sketch. It's not the time to name it. That window interrupts inspiration...
A name? What name? You're still brewing, my creation. I'll name you John Doe like your grandfather... Where were we going? Oops, I forgot. Inspiration is lost.
(The question is really annoying at that moment.)
4- I know exactly what I'm going to do, it's a defined project, and it has a name. Okay, no conflict here. But that's 0.1% of cases.
This is why I think that in the case of .qtz, it's not necessary to ask for a directory and name.
Qtractor could create a .temp file on the fly. And as for the name, the user can edit it at any time. The default could be the file name when saving.
That would avoid the question.
However, I understand that Qtractor already has a defined way of working that works for both qtr and qtz.
You can seamlessly switch between formats on the fly.
Changing this doesn't make much sense either.
So I'm sticking with the "myPath/Projects/.TEMP" template trick.
I've decided to work only in .qtz.
Qtr presents some conflicts:
1_
Saving versions becomes dangerous. If I modify a MIDI file in version 5 (or worse still, rename the session), all previous versions are broken, rendering the functionality useless.
2_
The problems with dependency files that can disappear at any given time.
...
Back to the post:
I think I've found a smooth way to solve this.
The default project folder is set by the template. I think this isn't documented, and it was driving me crazy: where does that default "proyect path" value come from?... But I finally figured it out.
The way I solve it: The project path in the templates is,
myPath/Projects/.TEMP
This is how I tell Qtractor that I want all temporary recordings to be saved there.
When it's time to record, the annoying session window appears.
I put anything in the name. For example, "x".
The reason for the annoyance and the "x" as the solution:
1- I'm testing workflows: the project isn't meant to be saved, it doesn't need a name.
2- I'm doing improvisation exercises: the project isn't meant to be saved, it doesn't need a name.
3- I'm inspired. I know I want to do something to be recorded, but I don't know what it is yet. It will be defined as I sketch. It's not the time to name it. That window interrupts inspiration...
A name? What name? You're still brewing, my creation. I'll name you John Doe like your grandfather... Where were we going? Oops, I forgot. Inspiration is lost.
(The question is really annoying at that moment.)
4- I know exactly what I'm going to do, it's a defined project, and it has a name. Okay, no conflict here. But that's 0.1% of cases.
This is why I think that in the case of .qtz, it's not necessary to ask for a directory and name.
Qtractor could create a .temp file on the fly. And as for the name, the user can edit it at any time. The default could be the file name when saving.
That would avoid the question.
However, I understand that Qtractor already has a defined way of working that works for both qtr and qtz.
You can seamlessly switch between formats on the fly.
Changing this doesn't make much sense either.
So I'm sticking with the "myPath/Projects/.TEMP" template trick.