Glad to hear that it works!
For other parameters, generally yes, if there is a benefit having them in the filename. Please be so kind and open a new thread regarding this in the wish list section of the forum.
- Wolfgang
Read More...
I'm not 100% sure, since I cannot find an explanation in the log. Could it be that Part 2 is the last one that could be executed before dawn? All others seem to be postponed to the next night.
Read More...
The explanation is that in the fourth iteration the third job's autofocus failed. Therefore this job was marked as aborted and not considered any more.To prevent such cases, you need to change the aborted job management from "None" to "Immediate:
The rest in our log looks good, Parts 1, 2 and 4 are cycled through as expected.
HTH
Wolfgang
Read More...
A fix has been merged and will be part of 3.6.7. If you want to test it earlier, you need to build yourself from sources or take the nightly build of tomorrow.
Thanks again for reporting.
Wolfgang
Read More...
Max, your scheduler file references E:/_Astro_in/Targets/5x360-ASI2600.esq, not the 15x120 file you posted in your zip file. I guess there is nothing surprising in it, but please post it as well.
Read More...
We are still trying to find the reason what causes this binning problem. Currently, only binning has been reported to be incorrect.
Do you have logs and both scheduler and capture sequence file to share?
Read More...
Please keep an eye on it. I would be surprised if the root cause has been fixed. But nevertheless good to hear that it works for you.
I took a closer look at our log file. It seems _sometimes_ when the capture sequence gets loaded, the binning isn't used from the file but it uses the setting from the alignment (or focus) process before. The only explanation for this is a concurrency issue, but I'm not really sure. It's remains under investigation...
- Wolfgang
Read More...
Thanks Max, please share the logs and both scheduler and capture sequence files you are using.
Just an idea: I would try to minimize the number of captures defined in the capture sequence and would increase the repeats in the scheduler accordingly. This might increase the chance that the binning is at least correct after several frames. But as long as we don't know what creates this fault, its just an educated guess...
- Wolfgang
Read More...