I understand your pain. I understand your pain. As stated in Changelog: * Bayer images: ensure that even margins have the same COLOR() for both the active sensor area and the full sensor area. The only way to achieve this is to ensure that left/top margins are even for bayer images and multiply of 6 for X-Trans images. Please note, that margins can also change due to firmware update (if margins are read from file metadata). So, the only way to ensure valid darks, master flats, etc etc is to use full sensor area, not active (visible) area for such data. You may be pleased to know that very few cameras are affected by this change. Also you may rollback this change by commenting out these lines in src/utils/open.cpp: https://github.com/LibRaw/LibRaw/blob/master/src/utils/open.cpp#L618-L640 This will not preserve from margins change due to firmware update. -- Alex Tutubalin @LibRaw LLC reply
I understand your pain.
As stated in Changelog:
* Bayer images: ensure that even margins have the same COLOR() for both the active sensor area and the full sensor area.
The only way to achieve this is to ensure that left/top margins are even for bayer images and multiply of 6 for X-Trans images.
Please note, that margins can also change due to firmware update (if margins are read from file metadata).
So, the only way to ensure valid darks, master flats, etc etc is to use full sensor area, not active (visible) area for such data.
You may be pleased to know that very few cameras are affected by this change.
Also you may rollback this change by commenting out these lines in src/utils/open.cpp: https://github.com/LibRaw/LibRaw/blob/master/src/utils/open.cpp#L618-L640
This will not preserve from margins change due to firmware update.