Bug 310270 - Assign camera color profile while importing
Summary: Assign camera color profile while importing
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Import-PostProcessing (show other bugs)
Version: 3.0.0
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-18 02:49 UTC by Juergen Karbach
Modified: 2016-07-16 16:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Karbach 2012-11-18 02:49:43 UTC
Taking photographs over a day will almost need different camera profiles in case of changing locations and light situations. Therefore it will be convinient to have a workflow that matches all images of each certain light situation (task) with their camera profile automatically.

Short explanation: http://www.youtube.com/watch?v=Q89NW8jtn_8&feature=related
More detailed explanation: http://www.youtube.com/watch?v=_m44L8o2Fwk

But this (LR)workflow isn't as convinient as it could be and 
the profiling program is only available for Windows and OS-X.

And, why this few manually clicks?
Only the (man readable) naming of the metadata template is needed.

Here a possible automated workflow.
To assign the images to the right profile you need to tag the colortarget photo first
(e.g. the first image of the task subdirectory - canon105, canon106, ..., 
or - if no subdirectories possible - the target images can determined by its "Date and Time" Exif-Tag.
At the point of  import into digikam its necessary to create a profile (via lprof ?) 
and then create a new metadata template, which will be assigned to the followed images
as long as the next colortarget image is detected or the last image has been processed.