In what ways were you hoping to be impressed by it? I find it very similar in terms of quality to my X-S10 26MP sensor, but it gives me extra cropping room, especially for wildlife. So, there’s no real downside to it for me as I was wanting an X-T camera anyway.
I think a lot of people were expecting much better “detail” from it, but I’m not really sure that’s something you can really see until you zoom right in and compare it to a lower resolution sensor.
I have a X100VI here for testing. Now I changed the cameras.xml to open the files in darktable.
Its fine, but I see a slim black bar in every picture on the right side.
My X-T5 does not have this “problem”. I think they have the same sensor.
Is there anything I can do?
Thanks! I replaced /var/lib/flatpak/app/org.darktable.Darktable/x86_64/stable/2b7e2831adcca9d30ac01acdbe8a96ad50ed70adba4dc3bb025b3f61dc8551e8/files/share/darktable/rawspeed/cameras.xml with rawspeed/data/cameras.xml at develop · darktable-org/rawspeed · GitHub and I get the black bars on the top and right hand side. I’ll try to edit the cameras.xml with your <crop />. How come the X-T5 doesn’t need <crop />?. It’s the same sensor as the X100VI. Just curious.
It’s does, it was there to begin with for dt <= 4.6. You replaced it w/ a new version that doesn’t have it.
While usually you can just pick changes in cameras.xml from rawspeed develop branch (and I really do mean pick, not overwrite the entire file), sometimes they also go together with other actual and significant rawspeed source code change. In that case it’s best to just wait for the next dt release.