Another idea for local copy.
Imagine I have some images on a slow external drive (old 2GB USB 2.0,
network location over 10Mbit/s wire or whatever).
In this case, what I want is that any picture I edit is automagically
"checked out" into the local cache on my fast internal (possibly SSD)
drive and "checked in" (aka: copied back), at the end of the session.
I imagine a group of settings in the prefs, that could look a bit like
this:
cache in local storage if origin is [ ] slow
[ ] in list of slow locations
slowness threshold [ 10 ] MB/s
slow locations [ /Media/truecrypt:
UUID="4CBF-23A2":192.168.0.254 ]
So if 'origin is slow' is ticked, DT would autocache anything
originating from media that have reading speeds below the 'slowness
threshold'.
Additionally, one should be able to specify a list of 'slow locations'
which always get cached.
Autocached images would get copied back (including their XMPs) to their
origin at the end of a DT session, assuming the origin is still
connected. Additionally DT would check for this at startup and sync
then, if necessary & possible.
Alternatively, syncing could be a background task that does this
automatically, whenever the machine is idle for 30 seconds, staring with
the least recently changed, not yet synced images.
Does that make any sense?
.mm
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
