Am 18.11.2015 um 13:56 schrieb Patrick Shanahan:
> * Christian Mandel <c.man...@gmx.net> [11-18-15 03:58]:
>> is it possible to write crop metadata (see
>> http://photo.stackexchange.com/questions/43893/how-to-store-tilt-rotation-and-crop-information-in-metadata,
>> xmp parameters for crop values) instead of actually performing the crop?
>> I guess it is not a standard feature (at least I did not find it) but
>> maybe it is possible with lua?
>>
>> The background: I do a lot of design work with photographs from dt
>> (calendars, photo books, etc.). Therefore, the photographs have to fit
>> within given frames. When I crop in dt (e.g. in 2:3 format) and use it
>> in a 4:5 template, I have to crop again, which is often not possible due
>> to losing important image parts. For these situations it would be better
>> to be able to "add" some picture at the other edges. Therefore, I have
>> to go back into darktable, crop different, export again and reuse the
>> image, which is cumbersome.
>
> Make yourself a "master" image, everything but the crop.  Duplicate the
> "master" image and crop and export the dup.  Now you have two copies of
> the same image in your database/library but only one "master" and an
> exported/cropped jpg and two xmp files, one for each.  The dup of your
> master is only an entry in your library and an xmp file.
>
> Every time you need another, different crop, go back to the master and
> make another dup (a library entry and an xmp) and export it at the
> different crop.  You may even be able to configure export to automagically
> assign a number or letter designation representing the image's crop ratio.

Of course this would work but it has some drawbacks. 1. it pollutes my 
database and therefore my lt with many similar entries. This is 
bothersome especially since I use duplicates for different edits of the 
same image, e.g. different color styles or color and b/w edit or 
landscape and portrait crop etc. To detect the master image(s) out of 
all these entries is not that easy (of course, color codes, but all 
colors/combinations are already in use, tags are not prominent enough, 
grouping is not flexible enough). 2. at the time of editing in dt I do 
not always know the exact ratio that I need. Going back and forth is 
time consuming and distracts a focused workflow. 3. The idea to write 
the crop into the metadata still sounds too simple to give up that 
early, but unfortunately I am not a programmer and of course I could be 
wrong with my assessment ;-)

Thanks for your suggestions, but there is still hope for a lua solution 
(dreaming of a native solution may be a bit too much ;-)

Best regards

Chris



------------------------------------------------------------------------------
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users

Reply via email to