XPost intentional, please keep FUP on .devel.
Due to the database split I was thinking about this topic again. As
Tobias states in
https://www.mail-archive.com/[email protected]/msg01237.html,
there are still some things in the db not propagating to the xmps. I am
especially concerned about time corrections.
Am 23.06.2016 um 18:12 schrieb Christian Mandel:
[What's the reason that time corrections are in db only? Can it be changed?]
Am 23.06.2016 um 16:11 schrieb Tobias Ellinghaus:
The request is quite old and I guess everyone agrees that having
something
only in database and not the XMP is bad. However, we haven't found a
way to fix
the issue. Details are here:
>
> https://redmine.darktable.org/issues/10569
K, I got the problem. Unfortunately the proposed patch is gone, I have
to dig deeper in the git to find it.
I checked the patch and it really doesn't solve the underlying problem,
since it will always use the corrected time.
But what about the procedure I was sketching below. If it is not
feasible: why?
Anyway, does something argue against the following procedure while
loading an xmp file:
- Check if the xmp originates from the actual file (e.g. metadata or
filename comparison if file without metadata, I would even do a pixel
data checksum¹)
- If file belongs to xmp, take the correction value in xmp
- If not, silently drop it (it is unlikely that the other file's date
is wrong) or ask the user how to proceed.
This way, processing another file would not break this file's timestamp,
and a user that knows how to load an xmp file with another image is
likely able to respond the proposed user interaction (keep the time
offset?). And IMHO loading a foreign xmp is a rare event compared to
wrong camera time stamps anyway.
¹This could anyway a reasonable feature request :-)
Best regards
Chris
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
