[Digikam-devel] [Bug 126149] Camera stores both jpeg and raw (nef), handle both as one

Axel Krebs axel.krebs at t-online.de
Sun May 22 20:00:34 BST 2011


Axel Krebs <axel.krebs at t-online.de> changed:

           What    |Removed                     |Added
                 CC|                            |axel.krebs at t-online.de

--- Comment #34 from Axel Krebs <axel krebs t-online de>  2011-05-22 21:00:27 ---
(In reply to comment #0)
> Version:           0.8.0 (using KDE 3.4.2 Level "b" , SUSE 10.0)
> Compiler:          Target: i586-suse-linux
> OS:                Linux (i686) release 2.6.13-15.8-default
> My camera can be configured to store both
> jpeg and raw (nef) at the same time. Like this
> rln_0220.jpg
> rln_0220.nef
> So for every picture I have both an JPEG and a raw. (The raw does not show properly but that is another issue)
> Anyway my wish is to be able to configure digikam to view only the jpeg, but > let some operations work on both.
> (NEF should be viewed as a negative and jpg as the processed image.)

If this issue is still available and valid: I support the wish to handle two
versions of one pic simultaneously strongly!!

This refers to several pairs of pic-formats:
Canon: jpg + cr2
Canon: jpg + crw
NIKON: jpg + nef

Maybe an number of other file formats!?

In my case, I have Canon _and_ NIKON- formats and therefore file-pairs (see

I suggest to include the handling of _any_ metadata, flags, exif-data (as far
as technically possible), geo-data and _any_ implicite data in pictures. 

There could be implemented some type of simple editor were a user could define
the bi-directional relations. From that tim on, any possible action refers to
both definied file-types. 

Even on amateur-level, time is limited. The more time-efficient we can work on
pics, the better we can concentrate on creative art-work. Even software is a

I hope ypu find this idea useful!!!


Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Digikam-devel mailing list