UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
hi,
I have a set of 40mm DSLR data which seems more difficult. APP does not allow me to search the comet. I see the first screen shortly, than APP tries to find Neowise by itself for all frames. Maybe a "force manually finding the comet" would be good. I attach one of the errors encountered processing the data and a single frame.
stefan
Ok, so the actual error is that it skips the manual selection? Didn’t see it do that yet (at this point it actually is a requirement), are you sure you didn’t click in a wrong place (just to be sure)?
Ok, so the actual error is that it skips the manual selection? Didn’t see it do that yet (at this point it actually is a requirement), are you sure you didn’t click in a wrong place (just to be sure)?
repeated this several times, first thought so, too. but no, did not click every time I am quite sure
Interesting, would be great if you can share this data with us to check.
Go to https://upload.astropixelprocessor.com and use upload1 (or upload2 till 5) as username and password will then be the same as the username.
Create a directory named “elgol-COMETselectionissue” and upload in there. Thank you!
Interesting, would be great if you can share this data with us to check.
Go to https://upload.astropixelprocessor.com and use upload1 (or upload2 till 5) as username and password will then be the same as the username.
Create a directory named “elgol-COMETselectionissue” and upload in there. Thank you!
hi vincent,
the login does not work after 3 attempts. maybe try this here:
https://c.web.de/@357527908165622470/L4XbE1XuS8q9Nt2x2Q00UA
stefan
Oh that is weird, you did use upload1 as username and upload1 as password?
I’ll give your link a go this afternoon, thanks.
@vincent-mod
so, I guess the comet algorythm has problems with the foreground. I cropped it and everything worked fine. Maybe insert something that stops this irritation.
this is done with the data in 3 different stacks: forground, stars and comet merged in photoshop
stefan
Thanks for sharing that, I'm starting to work on it today, have a bit of a data backlog. 😉
Ok had a look at the data, loaded everything in, went to the register tab and selected "comet" registration and it did ask me to point to the comet. Worked fine with the foreground. So unfortunately I can't reproduced your issue at the moment.
I can get a bit of that blue tail out of it, nice. But your combination above makes it much better even. 🙂
