19 June 2021: Our upload server https://upload.astropixelprocessor.com/ has been migrated successfully to our new office with higher upload and download speeds (nearly 10MByte/sec up/down ) ! We now have 1 general upload user called: upload with password: upload. The users upload1 - upload5 have been disabled.
31 May 2021: APP 1.083-beta2 has been released ! APP 1.083 stable will follow soon afterwards. It includes a completely new Star Reducer Tool, New File Saver Module, Improved Comet registration and much more, check the release notes here!
Star registration fail question
I am still within the 30-day trial window - that's how noob I am - but am very excited about what I've seen so far. I've run into a couple of quirks, but one that stands out is failing star analysis for frames that previously did not fail. UPDATE: This is for version 1.075. I just purchased and installed 1.077 but haven't done the stacks yet.
I shot M97 over several nights with my unmodded Nikon D5300 and stacked all the data. There were a few frames didn't load completely for some reason, maybe 3, and APP rejected these for failing star analysis. Okay, fine.
Night before last, I shot one night of M97 using my modded Nikon D5100, and I stacked the data. 1 frame failed star analysis - broken frame. I had already gone through every frame so wasn't sure what happened.
I decided to combine the two and added the D5100 frames to the D5300 frames as a new session and let it rip. It failed star analysis on perhaps 40+ frames.
I'm wondering why suddenly did so many frames fail star analysis? Is it because they were read over my network???
Thanks for buying APP! Did you get it to work with 1.077?
No. 1.077 crashes without warning. Just vaporizes.
I went back to 1.075 and reran slightly smaller versions of the stacks I was previously working with, except I had copied everything to a fast SSD in the system to eliminate the network. 1.075 handled things fine - except the star analysis. I lose quite a number of frames due to star analysis failing. Of course, I am very new to this app, and I am pleased I was able to get a result at all. 😉
Thanks for replying!
Maybe try it again with the data on the fast SSD? It still shouldn't just vaporize. 🙂 1.077 does have a better star analysis algorithm so that might help. Not sure if it could be the network, but it might cause some issues, we never recommend using that as the working directory.
1.077 crashes when using the fast SSD as well, so it's not a network glitch issue.
I am using 1.075 presently, and it has not crashed.
The star analysis failure is a bit annoying, but there is probably a logical reason for it. I know from DSS, the number of stars in my shots can be low, like 10-20. Using a long focal length (2032mm) f/10 doesn't always show tons of stars.
As a suggestion - when star analysis fails, have the "fail" popup contain the list of frames rather than having to scroll through the frame list at the bottom of the screen hunting. Sometimes the failed frames are clustered together, and sometimes not making them a bit harder to spot. Then give the user the option to "Continue without these frames? Yes/no."
Nice suggestion indeed, I'll pass it on. Crashes are beyond my diagnostic capabilities as Mabula actually codes it, so I've passed it along.
@khobar95 This happened to me yesterday after having the trail , all worked okay. Now bought and have registration issues
You mean the registration issue in the other post? That isn't a crash, but a data issue. Let's continue the discussion in that thread. 😉