MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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.
When Calibrating and Integrating Subs from Multiple Sessions and using Two Different Cameras how do I load a BadPixelMap for each Camera? If I load two BadPixelMaps will APP differentiate between them and assign them to the correct camera and the proper corresponding Session?
Â
Thanks
You want to make that data in 2 sessions then and assign one bpm to 1 and the 2nd bpm to the other camera.
Hi Vincent,
Yes that's what I would like to be able to do.
The actual project that I am working on consists of three sessions of NB data from 2018 taken by camera A that I would like to combine with two sessions of NB data captured in 2020 from camera B. When calibrating the data I can load master flats, bias and darks seperatly for each camera (or session) but it appears that I can only use one BadPixelMap and it is then applied to all sessions (clearly not useful for one of the cameras).
Bill
Is it? I must say I have not done a lot of multi session processing, but that's exactly why that would be the way to go, you can't assign the bpm to a session? (if not, I'll ask Mabula straight away). 😉
Ah you're correct, just tried myself. Let me get back to that.
Ah ok, got an answer back. It should automatically assign the BPM to the correct sensor. If the dimensions of the chip are exactly the same, the capture software should add the name of the sensor to the header, otherwise APP wouldn't know indeed. Basically it would recognize the darks for another camera then also automatically like that. Sessions are more for the same sensor, with different calibration files for that session of that sensor.
Ok, but in my case the sensor size of the two individual cameras are exactly the same and I cant see any differentiation between the two in the FITs header. Wouldn't it be easier to treat the BPM in the same manner as the other Master calibration files and simply designate what sessions you want each BPM to apply to?
Â
What I have done as a work around is to calibrate each camera group seperately, save the calibrated subs and then reload both groups for registration and integration. This seems to work but adds a couple of additional steps and time to what is an otherwise wonderful and fully automated process.Â
I'm interested too in this possibility, that is: let me choose to add and assign each BPM freely to each corresponding session, as i normally do with all other calibration files...
Thanks Mabula if you can do thisÂ
Yes, when the sensor is exactly the same in dimensions and no name is given (you may have a look if the capture software can provide that, normally they should) the best is to process that data separately. It might be interesting to see if this can be changed somehow.
