[KPhotoAlbum] Raw workflow

[Robert Krawitz]

On Tue, 28 Aug 2012 20:22:18 +0300, Miika Turkia wrote:
> On Tue, Aug 28, 2012 at 7:52 PM, Robert Krawitz <rlk at alum.mit.edu> wrote:
>> On Tue, 28 Aug 2012 19:37:55 +0300, Miika Turkia wrote:
>>> On Tue, Aug 28, 2012 at 4:55 PM, Robert Krawitz <rlk at alum.mit.edu> wrote:
>>>> On Tue, 28 Aug 2012 16:46:30 +0300, Miika Turkia wrote:
>>>>> On Tue, Aug 28, 2012 at 4:03 PM, Robert Krawitz <rlk at alum.mit.edu> wrote:
>>>>>>
>>>>>> Consider it an RFE that it be possible to specify stacking order,
>>>>>> somehow.  I'm not sure precisely what that should consist of -- perhaps
>>>>>> a list of regular expressions, and each image name in the stack is
>>>>>> matched against the list, and the stack order matches the order of the
>>>>>> regexp list.  For example:
>>>>>>
>>>>>> .*\.(cr2|crw|nef)
>>>>>> .*_modified\.jpg
>>>>>> .*.jpg
>>>>>>
>>>>>> Suppose we have the following files:
>>>>>>
>>>>>> img_0000.cr2
>>>>>> img_0000_modified1.jpg
>>>>>> img_0000_modified2.jpg
>>>>>> img_0000_xxx.jpg
>>>>>> img_0000.jpg
>>>>>>
>>>>>> We match each of those filenames against each regular expression in the
>>>>>> list, resulting in the following (image,index) pairs:
>>>>>>
>>>>>> img_0000.cr2              0
>>>>>> img_0000_modified1.jpg    1
>>>>>> img_0000_modified2.jpg    1
>>>>>> img_0000_xxx.jpg          N/A
>>>>>> img_0000.jpg              2
>>>>>>
>>>>>> The following rules then define the stacking order:
>>>>>>
>>>>>> 1) Images with lower indices stack above images with higher indices.
>>>>>>
>>>>>> 2) Images that do not match any of the regular expressions stack at the
>>>>>> bottom.
>>>>>>
>>>>>> 3) If there is more than one image with the same index, they are sorted
>>>>>> in lexicographic order (in whatever locale is most appropriate in this
>>>>>> case).
>>>>>
>>>>> In my workflow the current model to stack the latest find to the top
>>>>> works fine. However, it really sounds that it does not support new
>>>>> users for the autostacking feature. Of course small "errors" can be
>>>>> fixed manually but your case really sounds like there should be at
>>>>> least an option to select that the top image should not be RAW.
>>>>
>>>> Some people would want the RAW to be the top of the stack.
>>>
>>> True. A current workaround is to search for RAW only. The disadvantage
>>> is that the whole stack is not available in this case and thus you
>>> cannot annotate the full stack. For me the developed JPG on top is
>>> ideal and still gives me access to the RAW easily with the
>>> open-raw.pl.
>>
>> There are a lot of different possible workflows.  The key is to not have
>> artificial restrictions on what people can do.
>>
>> One other thing that would be useful would be to allow selecting images
>> from a stack based on file extension, regexp, what have you.  So I could
>> select all RAW images matching a keyword, all JPEGs, what have you.
>
> The Label based search is too restrictive to my liking also. Even
> including the file suffix there would mostly solve my need, but a true
> regexp would be even better.

But be more confusing to people not familiar with regular expressions.
I'm OK with regexps for now; kpa users are pretty advanced.

But what I really meant was that a common workflow might be to select
all images with a given label, and then export or whatever the RAW (or
JPEG) image from each stack.

>>>>> The replace text is tried in order if there is multiple strings
>>>>> separated with semicolon. Thus .jpg;.crw would first try to replace
>>>>> the regex match with .jpg and if not found with .crw. It looks to me
>>>>> that your suggestion would not work as you have to change the prefix,
>>>>> and not keep it intact. I believe you should use following when using
>>>>> the search regex as you defined it:
>>>>> Replace: img_\2.jpg;crw_\2.crw;crw_\2.cr2
>>>>
>>>> That's definitely not obvious from the description, and it doesn't match
>>>> the example.
>>>
>>> I hadn't seen a case like yours so I thought matching the suffix to be
>>> sufficient. More examples and clearer explanation is definitely
>>> needed. Basically we are talking about normal regexp like
>>> s/\.raw/.jpg/ but instead of writing multiple regexes the latter part
>>> can expanded automatically.
>>> s/\.raw/.jpg/ and s/.\raw/.tif/ can be compressed into s/\.raw/.jpg;.tif/.
>>>
>>> Of course everything becomes quite messy when you take the different
>>> versions and sources into account and need to match suffix and prefix.
>>
>> I suggest that rather than a semicolon to separate components (a
>> semicolon could be a significant character) that it use some kind of
>> list entry, with the possibility of moving things up and down the list.
>>
>>> BTW did you get your problem solved?
>>
>> If autostacking doesn't work, I can't fix it.
>
> Autostacking works when you have images on KPA database and search for
> new images. I thought you had that case since you have the JPGs
> already in but had the ignore RAW ticked. It does not work in case you
> import two new images simultaneously that should be autostacked.

I see.
-- 
Robert Krawitz                                     <rlk at alum.mit.edu>

MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four!
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --    http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton