Hello,
I have been digging a little deeper for the las two hours, and still cannot understand the philosophy of this all.
First, yes, I did understand that I had to set and save sequences that I would launch later and thatt would do the jobs I had set up. And I had done this already.
They do not appear on the screenshot, because at that time I was only testing the preview, in order to see how the thing behaves, where and how its stores the files.
For the two last hours, I have been trying to understand how it works when the sequences are run.
My conclusion is that it is not consistant. whether I set it to local or distant, it behaves two different ways.
As you can see ont he screenshot, I set the folder to Pictures for local shots and to Images for distant ones.
Though, there again, I still cannot understand the difference between each, as they both result in saving to the PI. And, yes : I know the time is not correct, I was too lazy to set it for my testings.
But let this for later, and let us focus on my main issue : get a consistant behaviour.
- The target %t is M42, and
- I want it to be stored to the distant folder Images,
- in a subfolder nammed upon the target name %t,
- then to another subfolder nammed upon the type %T,
- and finnally the shot itself nammed upon the sequence name (ASI30s) %f, timestamp %D, exposure %e and sequence number on three digits %s3.
- This results in Images/%t/%T/%f_%D_%e_%s3 and should give me something like Images/M42/Light/ASI30s_2023-07-12T02:21:54:975_30_secs_001.fit
But, as you can see, the result I get is far from what I could expect.
If I then try to store to local, with the same scheme, I actually get the correct naming.
Where is the problem ?