Strange integration...
 
Share:
Notifications
Clear all

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.

 

Strange integration result using latest release APP 2.0.0-beta25

5 Posts
2 Users
1 Reactions
1,000 Views
(@rkottink)
Main Sequence Star
Joined: 6 years ago
Posts: 18
Topic starter  

I'm using a NTFS disk.

I combined 3 sessions of lights (90 subs in total), 1 masterflat and 1 masterbias

 

I tried multiple times and every single time the result was the same:

Screenshot 2023 10 09 213358

In the version 1.083.4 no problems with the same lights, masterflat and masterbias and the result was:

Screenshot 2023 10 09 213439

 

I don't know what went wrong.

 

 

 

 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5308
 

Hi Rob @rkottink,

You will need to turn on the cosmic ray/noise reducer in 3) Analyse stars and set it to a value of 10-16 and it will be good 😉

The reason for this issue, is that APP is locking on to hot pixels as stars and then misalignment happens. This issue is on our list to fix, but I must point out and ask why you are not using darks and/or APP's BPM function. The Bad Pixel Map would have solved this probably and it is always recommended to use at least Bad Pixel Mapping in every data calibration workflow because it nevers harms data and only fixes bad pixels immediately. You can create a good BPM from a couple of darks and then use that BPM for all your data without using darks.

Mabula



   
ReplyQuote
(@rkottink)
Main Sequence Star
Joined: 6 years ago
Posts: 18
Topic starter  

@mabula-admin Thanks for your quick reply.

I will add the BPM in the workflow. And give it a try in de latest Beta version.

Still love using APP, and after 2 years still learning how to use all the functionality 😀 

 

Kind regards,

Rob

 



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5308
 

Hi Rob, @rkottink

Excellent, and please use the noise reducer in 3) if needed. Did you try this already?

Still love using APP, and after 2 years still learning how to use all the functionality 😀

That is really awesome, thanks for the feedback 🙂 !!

Mabula



   
ReplyQuote
(@rkottink)
Main Sequence Star
Joined: 6 years ago
Posts: 18
Topic starter  

@mabula-admin Just to let you know. The noise reducer did the trick. I didn't need a BPM.

 

Rob



   
Mabula-Admin reacted
ReplyQuote
Share: