Weird/terrible artifacts introduced during registration

Thank you for sharing the files, I'll download some and see if I can see what you mean. Can you post a screenshot what the issue exactly is and what APP version you use on which machine? Thanks. I see you added drizzling, I assume you dithered the lights properly then as well..

I can post the screen shot a little later (currently running a new batch of frames through). I am using 1.078 on a windows machine. Dithered every 3 frames, which should be enough, as it has been working for my other stacks. 

Thanks for your help!

I saw a weird white balance setting in sharpcap last night so I tried resetting it and am hoping it solves the problem (my white balance was WAY out of whack and was completely set to blue, so maybe it was so blue that APP could not accurately stack?). I tried shooting the same target, so hopefully it works itself out. 

Ok, please upgrade to 1.079 as well as quite a few bugs were solved in between.

Here is the issue screen shot. I will upgrade and try again.

This banding is with the data from last night, which had the white balance issue fixed, so something is amiss... hopefully the software update fixes it!

Wow, I've never seen that before. I don't think the upgrade will solve that as it seems a data issue. I'll be having a look later at the data, thanks for sharing.

I think the update fixed the issue! I do not believe this is a data issue, because Pixinsight (sorry for using the P word here) was able to stack no problem. 

I got through normalization with everything looking normal!! I will report back once integration finishes. 

Oh, very interesting. That would be very interesting, maybe a setting that's different now (many are now set to "automatic" in 1.079). Thanks for trying!

And no worries, Pixinsight, DSS (don't use that though 😉 ) and others are used as well so they are part of many people's workflows. I can't give support on those, but I'm not thinking everyone is only using APP. 🙂

It looks like the software upgrade fixed the problem. Would it be possible to add this to the release notes? I imagine I am not the only one seeing this, and it was very frustrating, especially when the CLS filter was working fine!

Thank you

Well it's not something we specifically fixed as we didn't see this specific issue before. I think it might be a setting that helped your dataset.

Well whatever it is... magic seems to have happened :).

Thanks for always updating this software so frequently!

We'll add magic to the improvements. 😉

Got that banding issue again... trying to understand what is possibly going on. Is there anyway to review the data I uploaded from last night?

Test Frames: https://drive.google.com/open?id=1OBNBaomtY33YSFzS2GJiq7YVVtNWhNsW

Master dark: https://drive.google.com/open?id=1CvXHGqCFBjNAga6l5GY2aDYJf_2L-YTO

Master flat: https://drive.google.com/open?id=1pqHanItC8dectgB0HcLt8bHSCDktnk-Z  

It is starting to look like a bug as the integration came out fine, and the normalizations when re-loaded do not have the banding. 

Ok, I will get your recent data as well and will see what I get here and if it's something in your data or an APP issue, thanks for sharing! I hope to have something tomorrow.

Thank you!

I also spoke to my astronomy club (Amateur Astronomers Association of New York, AAA.org) about APP and I will be doing a tutorial for them of the software. I would love to provide them with a link to a bulk discounted rate, if that is possible. If this is not possible, no problem at all!

You guys have made a great piece of software and I am excited to share it with my group. 

Ok, sorry for keeping you waiting, things got in the way. I'll have a look today.

No problem. If it is too much trouble, I can just skip that data- things seem to be working now.

Yeah, it's been a bit random today sorry. I'm still going to check it first thing tomorrow anyway. 🙂