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.
Hi,
how can I achieve this? APP does not do this, in registration it just stops (no specific error shown). Both files are rgb 32 bit fits data with a nikon dslr, lens 105mm and the other lrgb in 32bit rgb format done with a asi 6200mm and a 550mm focal length. Done with APP.
Â
is it too far apart (resolution wise etc) or should it in principle work?
Â
stefan
Anyone here?
Â
so, again, now I put some more info in here:
screenshots of the data and the typical errors message I get are shown. No suggested setting works.Â
Â
I would like to know, if in principle it should work and if yes, how?Â
When I use 400mm focal length data with the nikon dslr, registration works right away.
So it must be due to the resolution, meaning 105mm with 36 megapixel will not match 550mm with 61 megapixel...
Â
400mm/Nikon:Â Â Â 2,5 arcsec/pixel
105mm/Nikon:Â Â Â 9,6 arcsec/pixel
550mm/6200mm: 1,4 arcsec/pixel Â
Â
if so, what would be the shortest focal length used with a nikon d810a, pixelpitch 4,88 mju, to match a imx 455 chip, 3,76 mju using a 550mm scope?
Â
Â
Probably the best way would be to split the RGB frames and save them as R, G and B. These are then also mono and can be added like that. Load each camera and its data (including calibration data) into its own session. These should then result into integrated mono stacks. It should be possible to combine, but I'm not 100% sure this will work for all FOV's.
Probably the best way would be to split the RGB frames and save them as R, G and B. These are then also mono and can be added like that. Load each camera and its data (including calibration data) into its own session. These should then result into integrated mono stacks. It should be possible to combine, but I'm not 100% sure this will work for all FOV's.
hi vincent,
Â
since it works, see my post, with 400mm, it is not neccessary to do this ...
Â
Â
Â
Ah right, sorry missed that. There are a few ways to get the same result, my workflow is what I tend to do, but not required indeed. So if registration doesn't work there may be a limit, would you be able to share the data perhaps? I can check as well on my end and then let Mabula know.
@vincent-mod am uploading 2 files now, takes 20 min ...
Thanks, I have some data to process but will come back to you asap.
So I looked at panels, what I think is happening is that there are very little star pairs to properly align them. That or it is indeed too different.
So I looked at panels, what I think is happening is that there are very little star pairs to properly align them. That or it is indeed too different.
OK, thanx... guess in case trial&error then
Â
