Always get whacky r...
 
Share:
Notifications
Clear all

June 24 2026 APP 2.0.0-beta46 has been released !

Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.

May 27 2026 APP 2.0.0-beta45 has been released !

Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

Always get whacky results attempting to integrate two previous integrations from different captures

3 Posts
2 Users
0 Reactions
947 Views
(@readyjetty)
Neutron Star
Joined: 4 years ago
Posts: 79
Topic starter  

I have both an ASI2400MC and an ASI2600MC and when I try to integrate captures from both together, I get whacky results (see attached).  It doesn't matter if I try to integrate in Mosaic more or Full mode and what setting I have on registration selections like "Same camera and optics" and "dynamic distortion correction".   The results are just bizzare sometimes.    To examples below.  Also are subsamples of the two integrations I'm trying to integrate.   Since I shoot Alt/Az so there is a lot of field rotation my two sub integrations (third and fourth files), so perhaps that's the problem.  I can register them, but APP just can't see to stack them, which is strange because you would think registering them would be the hard part.   Even if I crop both down to nice clean rectangles, I still get the whacky results.

OrionCombined 1 St
OrionCombinedNoLNC St
Orion90Pct StOrigtemp
OrionFullSetAlignedChannelsOrig StOrig

This topic was modified 3 years ago by Steven Miller

   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Normally you turn off same camera and optics and when things look very weird, also turn off dynamic distortion correction. I'm not experienced with alt/AZ photography, but if I would do that I would get a rotator and possibly also something that makes it track properly. Without that it does get complicated fast. But the last image you show does seem relatively ok doesn't it?



   
ReplyQuote
(@readyjetty)
Neutron Star
Joined: 4 years ago
Posts: 79
Topic starter  

Thanks for the quick response!

I don't think Alt/Az is the problem as I take short exposures (4-8 seconds) so I get very minimal field rotation per shot and no visible star elongation on the edges of the field.  For field rotation over an imaging session, APP integrates into a larger frame with “full” integration mode.  The edges are  noisy and undersampled, but that’s it.  The main issue with the above image 3 and 4 is bad coma in one due to a mistake in the coma corrector spacing.  I don’t know why it can’t stack image 3 with image 4 once it can align them perfectly.  I had the same issue with the Horsehead: perfectly aligned but whacky warped integration, so I ended up integrating them manually in affinity photo.  Result was fine:

F273FF5F C180 463C 8C1C DB6F43D5D72E

 


This post was modified 3 years ago 2 times by Steven Miller

   
ReplyQuote
Share: