I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
[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 5 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.
