The advanced sequencer in NINA uses _0000.fit for the 1st frame in a sequence and appends according. When I add these frames to Siril using conversion the image frames in the sequence start at 0001.fit.
I initially like to review the frames by eye and remove the bad ones by deleting the image file(s), I then run siril scripts from a CLI to preprocess the good files. Alas the mismatch in frame numbers makes this error prone i.e. to delete the file for Siril’s frame target_0002.fit and need to remember to delete the file target_0001.fit.
Wondering if anyone figured out a solution in either NINA or Siril to get the sequence numbers to align i.e. get NINA to start at 1 or Siril to start at 0.
In the past we were starting by 00000, but we changed it. Indeed, for SER file and FITSEQ it was more logical to start with frame 1 rather than 0. This is why we’ve changed it for regular FITS too, in order to be more consistent.
in fact the simple solution is to not rely on NINA file numbering, for most people it’s full of dynamic data like dates or temperature anyway, and use an extra conversion before loading the sequence in siril. For example link light in the directory will be fast.