Fuji X-T1 image sizes incorrect
I have recently bought a Fuji X-T1 and have testing the raw conversion in Aperture, Lightroom and Capture One Pro.
While making some comparisons I noticed that CO reduces the file size when exporting.
The files from the camera are 4896 x 3264 pixels. Both Aperture and Lightroom export full size jpg images at this size but CO exports a full size jpg as only 4728 × 3152.
The exif data in all 3 applications shows the raw file as 4896 x 3264.
CO is not cropping information from the edges of the file, it is just creating a smaller image. If I set the lens correction to 0% then the file is exported at the correct size. Both Aperture and Lightroom have lens correction applied as default.
It appears the lens correction in CO reduces the file size but not in the other apps which is rather annoying because if lens correction is applied to several shots taken at different apertures then the full size jpg sizes vary from shot to shot on export.
While making some comparisons I noticed that CO reduces the file size when exporting.
The files from the camera are 4896 x 3264 pixels. Both Aperture and Lightroom export full size jpg images at this size but CO exports a full size jpg as only 4728 × 3152.
The exif data in all 3 applications shows the raw file as 4896 x 3264.
CO is not cropping information from the edges of the file, it is just creating a smaller image. If I set the lens correction to 0% then the file is exported at the correct size. Both Aperture and Lightroom have lens correction applied as default.
It appears the lens correction in CO reduces the file size but not in the other apps which is rather annoying because if lens correction is applied to several shots taken at different apertures then the full size jpg sizes vary from shot to shot on export.
0
-
I guess this needs to be reported to the PhaseOne as a Support Case.
I havent bothered to look in detail at the image pixel sizes from my XT1 conversions.0 -
The amount of pixels as reported in EXIF is recorded before lens correction, and as a result is it the same for all images from a camera.
The lens correction applied in CO7 seems to be derived from the image file, not from the lens database in CO7, as you can see at the Profile field in the Lens Correction tool.
Lens correction comes at the cost of pixels. CO7 is able to compensate for it by up-sampling, but apparently does not do that automatically when lens information is taken from the file.
This is just a guess from my part. It would be interesting to hear back from Phase One support when you open a case on the issue.
Bottom line is, do you want lens correction or do you want pixels (that is, a fixed amount)? Your call. I downloaded a file from Dpreview, and looked at it in CO7 with/without lens correction. Lens correction is doing an amazing job on the 18-55mm lens. And if you like to compare to other software, compare the output as well, not only pixels, unless that is what you are interested in most.
Would be interested to hear back.0 -
The lens correction data is in the raw file for these cameras, CO is not really doing anything that clever, it just has to apply it. The other 4 apps I have tried manage this without changing the file size.
The CA "Analyze" button is also missing so that can't be corrected properly either.
I haven't had any luck getting anything fixed when raising support requests 😭0 -
CO will not try to fake the data-loss that happens when you digitally distortion-correct an image due to the cropping. What matters is level of detail, not the amount of pixels. The distortion correction in CO maintains a very high degree of detail when correcting.
If needed to match the exact same pixel dimensions, I would create a recipe upscaling the image slightly.
The missing CA analyze button is a Xtrans-pipeline limitation.
A lot of stuff coming from our Support Team (which means coming from customers) does get fixed or implemented. A lot of prioritization goes into deciding what needs to be fixed or implemented, as we cannot satisfy all incoming requests due to limited resources.0 -
The re-sizing explanation does make sense, I guess the other applications must up-res a bit to maintain the pixel dimensions.
"The missing CA analyze button is a Xtrans-pipeline limitation."
As you say its not a limitation of X-Trans itself, its a limitation of CO (pipeline) not handling X-Trans to the same degree as Bayer, do you think this will be a feature that will be added in the future ? it would be very welcome and X-Trans is rising in popularity pretty fast.
Having compared many raw convertors over the last few days I have to say that CO does seem to handle the X-Trans files better than most.
Cheers Nik0
Post ist für Kommentare geschlossen.
Kommentare
5 Kommentare