Synchronisation Modes in Peakto

Synchronisation Modes in Peakto

When you make some changes in your preferred cataloging software, Peakto needs to update its database.


Most of the changes are obvious to detect, and Peakto can be updated quickly when you run a Fast Sync. But other modifications like a deletion of a Picture or a Folder are more difficult to resolve quickly. That's why we introduced the Run Deep Sync action in version v1.10.4. This action replaces the Smart Reingest of the previous versions and will perform a thorough scan of all the catalog and detect the changes. When nothing has changed for a specific image, it can move quickly to the next image and will not lose any time computing thumbnails, etc... It therefore takes more time than a Fast Sync but still takes a fraction of the time of the initial ingest.


The following table describes the limitations of Fast Sync for the various types of source:


Catalog Software
Fast Sync limitations
Details
Watched Folder
No limitations
Sometimes, for version from specifics software (DxO Photolab, ON1 PhotoRaw), we can't get the preview of the image, because it is not available in the computer.
Lightroom Classic Catalogs

Deleted files and structure

Fast sync will not detect and update a version that was removed from your Catalog. 
We can't detect changes from your collection Set, all the picture associated to your collection Set are not well synchronized in Peakto. 
When you move a Collection inside another collection Set, we can't associate the versions to the collection inside Peakto, and when you delete a collection set, the collection set stay inside Peakto.
Capture One Catalogs and Sessions
Deleted files and structure
Fast sync don't remove a version that was removed from your Catalog. 
We can't synchronize all the changes in your Users Collections hierarchy and the pictures associated to a folder can be wrong. We don't detect when you remove a picture from an album.

Moreover, regarding your Capture One options, if you are not syncing your metadata inside an Xmp files, we don't detect and synchronize any metadata change to Peakto. In this case yous always should run a Deep Sync.
Luminar Catalogs
No limitations.
All Changes are synchronized, but sometimes we can't get an accurate preview.
Apple Photos
No Limitation for System Library
For your system Library, we don't have any limitations.
For others Librairies, we don't synchronize changes in your album folder hierarchy.
IView Media & Aperture
No Fast Sync
There is no accurate Fast sync for theses catalogs.


    • Related Articles

    • Difference between the various synchronisation methods

      Peakto has been designed to keep track of the changes happening in the underlying catalogs. It will notify you when changes are detected via a dedicated icon in the sidebar, next to the source, but it won't run the sync. This task is left to you ...
    • How to reset Peakto and start afresh

      Sometimes you wish to start from a blank sheet again and reingest content, or rebuild a complete Peakto catalog with your content If you feel like you need to start afresh because of an issue, please contact support first so we can help and prevent ...
    • How to send the Peakto database when the support asks for it

      Peakto saves its catalog structure in a folder that you can define yourself via the Preferences. If you don't do anything special, the default location is : ~/Library/Application Support/Peakto The Peakto catalog consists in several database files: ...
    • 1.3 Adding images to Peakto

      1. Adding images to Peakto You can add 2 types of content to Peakto: Files inside folders Catalogs of one of the supported types (Aperture, Lightroom, CaptureOne Pro, iView Media, all flavours of Luminar) 1.1. Adding folders: Simply drag any folder ...
    • Volume is online but catatogs on that volume appear offline

      There are situations where a volume has been improperly ejected. When the volume is mounted again, the mount point of the previous time is still hanging around, and macOS cannot reuse it. As a result it will allocate a new mount point that has a ...