2026-10-09 APP 2.0.0-beta48 has been released !
This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.
2026-10-03 APP 2.0.0-beta47 has been released !
This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂
And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.
Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.
RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.
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
Â
