15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
I am loading 16-bit Tiffs (287 MB each, from Canon 5dsr) into APP but continue to get this message when I get to registration step. I have lowered the "detect above noise level" as far as it will go. I am not using any calibration frames, just lights.
I have successfully run this type file in APP before.
What do I need to do?
I have the same issue. My question is where is the "detect above noise level" I haven't been able to find it anywhere. The dialogue that comes up is a bit confusing. Most likely my issue is not enough stars since I was imaging during a near full moon and lots of moon glow. I used it before as well on another image with great success. Excellent program.
Thank for your time and input.
Kip
If it can't detect enough stars, the data must be problematic. 1.077 has a vastly improved star analysis tool that now detects enough stars in tricky data, so this is probably very difficult to begin with in your case. Can you show a sub?
near full moon and lots of moon glow.
Yes, that might interfere so much, that it becomes too difficult to get a reliable detection.
Dear @vincent-mod
I would love to read the answer to the original question since I have the same issue. And I've just tested with the newest version 1.078 but this doesn't work better.
where is the "detect above noise level"
Sure, so that was made absolete by the rewriting of the analysis algorithms. It wouldn't make a difference which is why it was taken out.
OK, thanks for the answer. Then, may I suggest to remove any mention to this parameter? I've got exactly the same error message as shown in the original post with version 1.077
And how about the star size area? was this parameter also removed completely?
Yes that too, should work in almost all cases now if the data is ok, we tested that by looking at many subs which also had problems in different ways before these versions. If you keep having this issue with other data as well, we can have another look for sure.
I notified Mabula about the warning, I never had it so didn't notice that, thanks for pointing out!
