https://bugs.kde.org/show_bug.cgi?id=375645
Bug ID: 375645
Summary: Altered files cause digiKam to scan always
Product: digikam
Version: 5.5.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Usability
Assignee: digikam-de...@kde.org
Reporter: forgivenb...@gmail.com
Target Milestone: ---
When Metadata -> Behavior -> all disabled -and- Miscellaneous -> 'Scan for new
items at startup (makes startup slower)' is disabled.
If metadata is altered by an external program (exiftool, exiv2, xnView, etc),
digiKam rescans all of the altered photos.
This is time consuming. When working with a large number of albums and photos,
excessive rescans can severely slow productivity. (Sadly, this is why I have
time to create this bug report)
Expected behavior is digiKam should only alter the database (digikam4.db) upon
demand (photos are untouched and not scanned) and can be synced (photos altered
and scanned) overnight.
Ideally 'Use lazy synchronization' would work similar to this, however altering
large amounts of metadata using lazy synchronization takes just as long or
longer as without lazy. DigiKam seems to be configuring the exiv2 statements
to queue which is a time consuming process. Configuring the exiv2 statements
should be done at the time of synchronization, not before.
All scanning should be able to be disabled so working with the database is not
interrupted.
--
You are receiving this mail because:
You are watching all bug changes.
