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.
[Solved] Image size in APP is not original size of taken image
In my late image processing sessions I started to see final images coming out with a longer ratio then accustomed. First I didn't pay too much attention. But after looking at specific patterns I realized that the images loaded into APP already had a narrowed field of view then the originals. What is the reason for this cropping in first place? How can this be avoided? I have added a file showing original size of taken image and the size of loaded image into APP. I am curious how to avoid this and make use of full image scale.
Thank you Georg
EDIT by Mabula: solved, camera settings is not using default aspect ratio of sensor as shown by CR2 metadata.
This topic was modified 4 years ago by Mabula-Admin
Could you explain what kind of data exactlt you're trying to load in and what steps you made before loading in the data? APP never crops an image during loading.
In the attachment, the bluish image is the CR2 image from my Canon T6i camera. I load the CR2 files via LIGHT button into APP and I see the more greenish, cropped in height image. The processed image has the same ration. It looses top and bottom information from the beginning.
In the attachment, the bluish image is the CR2 image from my Canon T6i camera. I load the CR2 files via LIGHT button into APP and I see the more greenish, cropped in height image. The processed image has the same ration. It looses top and bottom information from the beginning.
Dear Georg, thank you vey much for sharing your data issue here.
I have investigated the issue. From the dimensions that APP reports, you can clearly see the raw dimensions and the cropped dimensions, right?
So you see that APP crops almost 700 pixels in height on your images. Now this actually is not APP making a mistake here... let me explain:
My test image of the Canon EOS 750D shows the normal image aspect ratio for your camera:
Notice at the bottom the image dimensions reported by APP: 6000x4000 - 6096x4056 and to the left of the image, you can see the metadata of the CR2 file, the Canon Makernote shows AspectInfo: 0 6000 4000 0 0
Now we check your frame, shows 6000x3376- 6096x4056 and Canon Makernote shows AspectInfo: 7 6000 3376 0 312
So APP is doing what you told the camera to do, you must have set your camera to use a different aspect ratio of the sensor 😉
If another application is showing it differently, then that application is having an issue clearly.
Many photographers play with this, some use only part of the sensor, like using APS-C format with a Full-Frame camera because the optics can only illuminate an APS-C sensor. If we would not follow these settings set in camera by the user, it creates more issues as you can imagine so we need to follow this.
Apologies and thank you for pointing me in the right direction. I suspect one of the nights in December while I imaged, I must have clicked on the menu and accidentally changed the ratio while searching for another setting in the dark. Dahhh.... Never good to change things in the dark. I only realized this change in the last processing while I was trying to identify a tiny object crossing the lower part of the image, an area that was not in the finished image. But now I see that other images from mid December have same ration too. So, yes. My fault. Apologies again and thank you.
Apologies and thank you for pointing me in the right direction. I suspect one of the nights in December while I imaged, I must have clicked on the menu and accidentally changed the ratio while searching for another setting in the dark. Dahhh.... Never good to change things in the dark. I only realized this change in the last processing while I was trying to identify a tiny object crossing the lower part of the image, an area that was not in the finished image. But now I see that other images from mid December have same ration too. So, yes. My fault. Apologies again and thank you.
