UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
It would be great if the working directory didn't change based on the last files loaded. I (and probably many others) keep their master calibration frames in a different location than the light frames. As it is now, I open APP and set my working directly to where my lights are and load them. Then I load my calibration frames but before I can initiate the process I have to go back and reset my working directory so that the resulting files save to the correct location. Yes I could copy my calibration frames to be in the same place as the lights but that seems like an unnecessary step when the working directory could just be static.
Love APP and the work you're all doing just wanted to get some feedback!
Hi Reginald @regpratt,
Thank you very much for sharing your request.
Actually, I think there is some confusion here about how things actually work.
The Working Directory once set, is static, it does not change when you load frames like masters from different folders. I always keep my masters and integrations in separate folders, like I do also with lights, darks, flats etc...
So if you set the working directory to the folder where your lights are, and then load masters from a different folder or even a different drive, then the Working Directory is not changed at all, it still points to the folder of your lights.Â
When saving calibrated lights, registered, normalized files, there is a button to overrule the save directory. If you do not overrule it, it will always save in the static Working Directory. Same applies for your integrations/stacks. If you do not overrule with the Set Save Directory, button the results should be saved in the static working directory unless you overrule it yourself.
Does this make sense, can you double check the behaviour and let me know if all is okay or not?
Mabula
So I double checked and what was happening is that after loading files from a different directly, if you then click the working directory button Windows explorer opens up to the last folder from which you loaded files, not the original working directory I set. I always took that to mean if I continued with the workflow that last directly is where the stacks would save. However, I just ran a test stack and you are correct, the stacks did save to the original working directory even though that's not what comes up if I click the working directly button or any of the override buttons. Thanks for clearing this up!
Hi Reginald @regpratt,
Thanks for your feedback. Yes, this is the expected behaviour actually 😉 the working directory is static, but any new file chooser that is opened will open in the last location that was used in the file/directory chooser.
Mabula
