Bug 151228 - Whish: Skip / ingore RAW when corresponding JPG exists
Summary: Whish: Skip / ingore RAW when corresponding JPG exists
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Albums-ItemGroup (show other bugs)
Version: 0.9.2
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-23 12:38 UTC by Christian Mayer
Modified: 2021-05-08 12:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Mayer 2007-10-23 12:38:04 UTC
Version:           0.9.2-final (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages

All my RAW images are next to my JPG images when I'm setting my camera to save in both formats at the same time.

When I'm now clicking through the images in digikam I'm allways seeing the same shot twice (once in RAW - which is relatively slow - and one in JPG). It also takes more than twice the time to generate the thumbnails, once for the RAW and once for the JPG pictures.

So my whish is an option so that digikam skips the RAW pictures when a similar named JPG exists in the same folder. The thumbnail can be taken from the JPG. (When I'm developing a JPG out of an RAW I'm taking my time to tweak the options for the best result; an automatic preview can't possibly generate the same quality, and for a quick preview I'm saving the JPG at the same time...)

Note: Bug #147427 is related to this whish but has an different focus.
Comment 1 bmarsh 2007-11-30 00:04:21 UTC
Would like to add to this:   I would like an option to turn off all raw processing .  I use digikam to download my nef raw files but I do not want to do any raw processing in digikam.   Once the digikam sees the raw files on the memory card, it starts to process the raw files.   I always have to kill this.  Would rather have an option to turn off raw process altogether.
Comment 2 Gerhard Kulzer 2007-12-03 22:57:10 UTC
Initial wish:
This is practically implemented now in 0.9.3-svn: There is a quick filter in the status bar that lets you choose "NoRAWFiles", it show all other formats but no RAW files.

Gerhard
Comment 3 Gerhard Kulzer 2007-12-03 22:59:32 UTC
Comment #1:
I don't understand your scenario: digiKam does not process RAW files unless asked to. Don't mistake the extraction of the embedded thumbnail as RAW processing. I think your report is void.

Gerhard
Comment 4 bmarsh 2007-12-03 23:08:52 UTC
The problem I am talking about is when getting the pictures off a camera or a memory card.  When Digikam connects to the camera/card, it shows the pictures that are found on the camera/card and it will begin to make thumbnails of all those raw files.

If there is a way to turn off the generation of thumbnails while downloading files from a camera/card, then this would solve the problem.

You are right...  I am only talking about the generation of thumbnails, which I really would like to turn off for ALL types of files (jpg as well) when downloading pictures from a camera/card.
Comment 5 Christian Mayer 2007-12-04 08:58:41 UTC
@bmarsh:

your request sounds a bit different to the request of this whish (but I do fully support it, have a look at http://bugs.kde.org/show_bug.cgi?id=107316#c29 that also goes at the same direction but also has a slightly different focus)

@Gerhard:

this filter sounds like a great idea. 
But how do I access the corseponding RAW for my JPEG to open it in a raw processor? Do I have to change the quick filter and loose CPU resources during thumbnail generation?

Could it be possible to add an entry to the context menu: when clicking on the JPG it shows in the context menu "Open RAW with..." that opens the RAW with the same file name (but different extension, of course) with the selected program.
This context menu together with the quick filter solves this whish :)

Comment 6 Arnd Baecker 2007-12-04 09:21:58 UTC
To me the grouping of images, http://bugs.kde.org/show_bug.cgi?id=121310 ,
sounds like the reals solution
(see also http://bugs.kde.org/show_bug.cgi?id=147427#c3).

Of course, in the mean time one could add such a pop-up menu
(though this is already considered to be pretty full ...).
Not sure whether there would be any technical problems
because the image editor would use an image which is not the currently
marked one in the album view, but I think it should be ok.
Comment 7 Christian Mayer 2007-12-04 09:51:53 UTC
You are right, the grouping of pictures could also solve this whish (and is even more generalized, I like it)

But grouping offers a new problem: in a slide show or for generating tumbnails only one picture of the group should be taken, as I want to see only the JPG and not the RAW (for duplication and performance reasons).
But in a general group (e.g. for pictures taken during a short period of time, multiple JPGs that were processed differently from one RAW, source pictures for panorama stiching, etc.) I problably want to see all pictures of that group during screening or a slide show.
So the generalisation brakes here :(

So please implement grouping for its general usefullness. But also implement the treatment of JPG and RAW as one picture if both share the same name in the same folder (digiKam should use only the JPG internally but offer both for working with external programms, e.g. by two entries in the context menu)
Comment 8 Arnd Baecker 2007-12-04 10:14:58 UTC
Reply on the grouping added at http://bugs.kde.org/show_bug.cgi?id=121310#c4
Comment 9 caulier.gilles 2007-12-04 11:22:22 UTC
*** Bug 147427 has been marked as a duplicate of this bug. ***
Comment 10 Eric Vaandering 2007-12-04 14:13:36 UTC
I see my bug was just made a dup of this one. A quick scan shows there are other bugs that might have been better to make it a dupe of.

What I want is to treat the RAW as a master repository of the meta-data: rating, comments, tags, etc. Then, if I regenerate the JPG for some reason (cropping, exposure, white balance) digikam will detect that and re-apply the settings from the RAW file to the JPG.
Comment 11 Arnd Baecker 2007-12-04 14:55:17 UTC
> A quick scan shows there are other bugs that might have been better to make it a > dupe of. 

What do you mean by this?

Concerning the properties of an image obtained from editing a RAW or
other jpg/png: This seems to work fine, all properties (comment, rating, tags)
are transferred from the original file to the new file.
(Just tested with current svn).
Comment 12 Victor-Philipp Busch 2008-06-23 13:36:50 UTC
The idea, a JPEG to use as a RAW-thumbnail ist great. A lot of tools (like LightZone http://www.lightcrafts.com/products/index.html) use the same method: the program creates a JPEG from a RAW and then you can work with the JPEG. At the end of using LightZone (for example) all of your manipulations will be adopt to the RAW. Very cool. And very fast! It would be great, if digikam will be able copy this behaviour too.
Comment 13 caulier.gilles 2008-06-23 13:48:49 UTC
To victor, #12,

All RAW file has a jpeg preview embedded by camera. It's a waste of time to create a new jpeg from RAW to render thumbnail... digiKam already handle embeded JPEG from RAW to generate thumbnails or to display preview (F3 from Albumicon view): it's very fast.

Unforget than RAW file are container where you can find RAW image data, preview image as JPEG, Exif metadata, Makernote metadata, and sometime and ICC camera color profile.

Gilles Caulier
Comment 14 Arnd Baecker 2008-06-23 14:08:06 UTC
On Mon, 23 Jun 2008, Victor-Philipp Busch wrote:

> A lot of tools (like
> LightZone http://www.lightcrafts.com/products/index.html)
> use the same method: the program creates a JPEG from a RAW and then
> you can work with the JPEG. At the end of using LightZone
> (for example) all of your manipulations will be adopt to the RAW.
> Very cool. And very fast! It would be great,
> if digikam will be able copy this behaviour too.


Could you file a separate wish for this, as otherwise
this idea will get lost in the context of the wish here,
which is related, but still quite different.

Best, Arnd
Comment 15 Neil V 2008-07-15 22:30:42 UTC
*** This bug has been confirmed by popular vote. ***
Comment 16 Mikolaj Machowski 2009-05-10 21:41:25 UTC
This bug is similar to Bug 126149 . Scope is somewhat different so I hesitate to mark as duplicate but in essence this is still about RAW+JPEG handling.
Comment 17 caulier.gilles 2009-06-19 14:25:43 UTC
*** Bug 164756 has been marked as a duplicate of this bug. ***
Comment 18 caulier.gilles 2009-06-19 14:27:14 UTC

*** This bug has been marked as a duplicate of bug 126149 ***
Comment 19 caulier.gilles 2021-05-08 12:48:53 UTC
Fixed with bug #126149