On Mon, Sep 2, 2013 at 12:18 PM, Pascal Obry <[email protected]> wrote:
> 2013/9/2 johannes hanika <[email protected]>:
> > how did you trigger the xmp writing? mark 2k images and tag them at the
> same
> > time?
>
> Right. Doing just that.
>
> > that should indeed go into a bg job, where the bg job executes the
> > tagging and will lock the image only for a short time while it writes the
> > xmp? we'll need to make sure we write the xmp as part of dropping the
> write
> > lock though.
>
> Ah, if I understand correctly it will be wrong to only write the xmp
> in the bg job
> but it is fine to do the whole work (tagging + write xmp) in background?
>
> Note that the same issue happen for metadata as changing the author for a
> large set of image.
>
> Right?
>
yes, that should be fine. at least if the xmp is written while holding a
lock on the dt_image_t struct (dt_image_cache_write_release() writes the
xmp if called with the right flag). explicitly calling dt_exif_xmp_write
does not lock anything and will probably sooner or later corrupt your data.
-jo
>
> Pascal.
>
> --
> Pascal Obry / Magny Les Hameaux (78)
>
> The best way to travel is by means of imagination
>
> http://v2p.fr.eu.org
> http://www.obry.net
>
> gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
