Hi Dennis,
great to hear that others thought about this as well and even
implemented it. I can understand that one could find it somehow
confusing that some images are ignored, but with proper description of
the options and useful default values I guess it could be reasonable
clear, and it could even be hidden as unfoldable expert setting. I guess
DT has more complicated parts with steeper learning curve.
Concerning duplicates with suffix, I guess these are exported from
darktable, so it would be handy to not import already exported images in
the same folder if not explicitly wished by the user. Coming from
somewhere else, I think they should be imported, since they are maybe
gimp edited versions of the image that should get their final treatment
in dt (OK, unlikely, but just an example). This I guess would be the
least surprise, but to make things clear, dt could respond with a list
of ignored images. One could keep the list readable by detecting
subsequent images and list them as ranges:
The following images have been ignored during import due to the
selected parameters:
IMG0815.JPG (duplicate of raw)
IMG0819.JPG ... IMG0927.JPG (duplicate of raw)
IMG0937_1.JPG (exported by darktable)
...
I guess the exif of exported images will reveal this fact and they could
easily be filtered.
For the gui, I guess the two options
"[x] ignore jpeg files"
"[x] ignore jpeg files only if an accompanying raw exists"
would work very well, if the second is selected, the first should be
automatically greyed out, since the first then makes no sense anymore.
Thanks and best regards
Chris
Am 13.02.2015 11:43, schrieb Dennis Gnad:
> Hi Chris,
>
> I had written a patch for that on a filename-basis [1], which should be
> sufficient as it actually considers the whole path to the file.
>
> It was considered too confusing to the user when I discussed it in IRC,
> but I am also in this opinion in its current state.
>
> It added an additional option,
> "[x] ignore jpeg files only if an accompanying raw exists"
> which worked then together with the current available:
> "[x] ignore jpeg files"
>
> A better way would probably be to have a drop down menu that shows the
> following options:
>
> Import:
> "All RAWs and JPEGs",
> "RAWs only",
> "RAWs and JPEGs without corresponding RAW file"
>
> However, there is something else to consider: It will in its basic form
> only detect the exact same-named jpegs, e.g.
> "DSC_1234.raw"+"DSC_1234.jpg" but import "DSC_1234_1.jpg".
> So, for users who have these multiple jpegs, it might come as a surprise
> that the *_1.jpg, *_2.jpg, etc. files are imported. Not sure if we
> should detect and include them and what the 'least surprise' [2] would be.
>
> Otherwise, if some of the main devs commented on this, I could implement
> it soon.
>
> Best regards,
> Dennis
>
> [1] Please don't try this version of darktable, as it it is quite old,
> it could screw up your current database:
> https://github.com/bluesceada/darktable/tree/jpeg-solitary-import
> [2] Principle of least surprise:
> http://de.wikipedia.org/wiki/Principle_of_Least_Surprise
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
