I have introduced a number of improvements in the optical corrections, namely:
better auto-matching of camera/lens combo using on EXIF data. This is based on a looser association heuristics in the LensFun code, so it needs to be tested to see if this is not introducing too many false matches
the vignetting correction has been moved after the highlights reconstruction. Otherwise the highlights recovery was sometimes confused by the increase in luminance introduced by the vignetting correction
the focus distance now defaults to 1000 m when not available in the EXIF data. Before it was set to zero, thus de-activating some of the corrections.
The new code is available in both the stable and v0.3.1-rc1 branches.
This lens is actually not present in the LensFun DB (and not precisely described in the EXIF data).
The previous, more strict code would give an âunknown lensâ, while the new one shows the closest match⌠I have to see if there is some sort of âmatch scoreâ criteria that we can use to reject clearly wrong matches.
Hi there,
I just wonder whether âinsert image as layerâ menu might allow resizing (or even stretching, tiling) the inserted image. Then, it can be a real time saver for those looking for such a tool.
One of my first feedback was about this. I prefer to import first, then adjust. Import is possible but moving layers on canvas, cropping, tiling, resizing and defining borders arenât available or unstable.
Exactly!
It can be done elsewhere in a rather complex way but in current Photoflow, this may become second nature (as playing with tansparency and selecting various overlays are already there).
After quite some time of silent programming, here is an update of PhotoFlowâs features:
I have finally fixed a long-standing issue with EXIF data in exported TIFF files, which were for example seen as multi-page TIFFs by GIMP. Now EXIF data in TIFF files is saved correctly, apart from a small remaining issue with the copyright string being null that I am going to fix soon.
the stable branch now offers the possibility to save 16-bit or 32-bit EXR files. The ICC primaries are stored in the EXR file so that colors can be interpreted correctly, and EXIF data is also stored in a way that is recognized by at least GIMP and Darktable. The image data is automatically linearized upon saving if it is not already in a linear colorspace.
@Carmelo_DrRaw This is a gentle reminder to place the continuous releases to a more prominent position on GitHub. I use a bookmark but it shouldnât be difficult for others to find.
Thanks for the reminder! I have finally managed to find out how to refresh a git tag, so that the continuous release gets moved to the top of the list. Now itâs done:
It should be possible to open the file with the latest package from 2020-08-04, which includes an update of the raw decoding engine. Could you please check?
@heckflosse The day a raw processor can pwn a rival by demosaicing its package would be glorious indeed. Demosaicing itself while in a archive is something else entirely.
@heckflosse The unzipping of the archive is slow. Used the term decompression instead because it is more polite. BTW, this is also the case with @Carmelo_DrRawâs build-archives of RT. I make these observations from time to time but I donât know the cause of this problem. Could be the number of small files, archival settings or even how the app is assembled.
@Carmelo_DrRaw I just noticed that the camera and lens are unknown under lens corrections.
Will find out later in the afternoon.