Two BPM files creat...
 
Share:
Notifications
Clear all

Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.

It did take a long time to have the work finished on this and it  will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...

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.

 

Two BPM files created for DSLR

1 Posts
1 Users
0 Reactions
1,336 Views
(@maxthebuilder)
Red Giant
Joined: 8 years ago
Posts: 39
Topic starter  

Hello,

When I stack DSLR (Nikon 5500) images, APP produces two BPM files.

(APP doesn't do this for my ZWO ASI camera).

One is called BPM-Nikon_DSLR_DSC_D5500-6016x4016.fits and is essentially flat with no bad pixels.

The other is called BPM-NIKON_D5500-6016x4016 and looks like a BPM.

The first one is redundant (?).

I wonder why it is created.

Thanks!



   
ReplyQuote
Share: