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.
Hello,
when doing a mosaic like the one in Mabula's big tutorial with my data and I use two different cameras, how do I do this? I realized that my unmodded Nikon D750 is quite ok with AP but needs different treatment in star color analysis than my D810a. Usually you proceed in stacking each setting before using the stack (panels) for combining them into a mosaic. This is done without previous lightpollution or Sc-calibration. But when I combine stacks of different cameras with like different green cast as with the 2 Nikons wouldn't I get into trouble?
stefan
Data taken with different camera's and setups shouldn't be a problem at all as this was part of the extensive testing Mabula did in the beginning. He created some stunning results with data taken by a lot of different people into 1 image. So what you could do is try to go with the data at once and deselecting "same camera and optics" in the register module (4). Or, integrate them seperately and combining the stacked results. In the post-processing, the background neutralisation and color correction tools should take care of the rest (as well as the LNC or Local Normalisation Correction in the integrate module).
Data taken with different camera's and setups shouldn't be a problem at all as this was part of the extensive testing Mabula did in the beginning. He created some stunning results with data taken by a lot of different people into 1 image. So what you could do is try to go with the data at once and deselecting "same camera and optics" in the register module (4). Or, integrate them seperately and combining the stacked results. In the post-processing, the background neutralisation and color correction tools should take care of the rest (as well as the LNC or Local Normalisation Correction in the integrate module).
if that works then it'd be great. just thought that local mixed colors due to implementation of different sensors in a mosaic could influence this. LNC etc. would be indeed powerful. Light pollution correction does not influence star colors that much so I thought here could be a problem ...
It shouldn't be a big problem, unless something very specific causes an issue between the data. The proof will be in the pudding!
Hi Stefan @elgol & Vincent @vincent-mod,
In my experience, if you shoot the data from the same field of view with 2 different camera's then there should be no problem in combining this properly.
Howeverm if you are creating a mosaic, and you shoot the mosaic panels with different camera's, then things might start to become complicated very quickly, especially is the difference between the camera's is big. A Nikon D810a and a Nikon D750 are a bit different, the D810a will show H-alpha regions much more prominent. Some holds for combining data into a mosaic where 1 panel is done without a filter and the other panel is done with for instance a LPS filter. Then you will run into problems normally.
Kind regards,
Mabula
Ah right, good catch, yes those are problematic ofcourse as the data itself is then not comparable anymore.
