Bug 92783 - Usabilitiy of RAW file support
Summary: Usabilitiy of RAW file support
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-RAWProcessing (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-06 02:45 UTC by Thorsten Schnebeck
Modified: 2019-12-24 10:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Schnebeck 2004-11-06 02:45:46 UTC
Version:            (using KDE KDE 3.3.1)
Installed from:    Compiled From Sources

This ist about RAWfile support of digiKam. I *think* this is done by the corresponding kipiplugin(?)

Single RAW file support:
========================

RAW file support in digiKam is nice but not very usable. The interface gives the user control of dcraw parameter and can calculate a visual feedback. But the way to do this basicly right shows the new interface of the rawphoto plugin for GIMP

http://ptj.rozeta.com.pl/Soft/RawPhoto

Parameter and histogram give the better, the necessary  feedback to the users than the simple visual feedback. Please copy this interface for digiKam.

Batch RAW file support:
=======================

RAW files need a per picture setting. So there is normally no reason for batch processing. But as written in
http://bugs.kde.org/show_bug.cgi?id=90875
many RAW file formats (Canon and Nikon for sure) have an embedded Jpeg. This Jpeg is not a simple thumbnail but a full developed and usable image. 

Meanwile we have created an extractor for embedded Jpegs that you can get here:
http://forum.ebv4linux.de/files/rawext.tar.gz
README so far is in German only but here is the short version:
rawext RAWfile.crw JPGFile.jpg
extracts the Jpeg embedded in RAWfile.crw and saves it as JPGFile.jpg. Program is tested for Canon RAW files but should also work with other formats.

So, what is the normal workflow:
- Take the photos in RAW format with Jpeg embedded
- download the photos digiKam. As preview digiKam only needs to show the embedded Jpeg - there is no need to use the time expensive dcraw!
- Than you review your photos upon these Jpegs.
- if Jpegs are fine there is often no need to use the time consuming RAW develop process. So take the Jpegs, drop the RAW
- if Jpegs shows problems (too dark/too light) you don't want the Jpeg but this time the RAW. And then you use the single RAW file converter to optimize this photo.

Ok, I know its a long text. So whats the matter? :-)

- Digikam needs a better single RAW file converter GUI
- Digikam needs to handle with in RAW file embedded Jpegs (#90875)
- Digikams batch RAW-file converter should have an option not to process dcraw with constant parameters but to extract the embedded Jpeg via e.g. rawext.

This is no demand but a whish :-)

Thanks for your patience

  Thorsten
Comment 1 Thorsten Schnebeck 2004-11-08 14:48:13 UTC
Another good or enhanced gimp GUI for dcraw is
http://www.aei.mpg.de/~udif/UFRaw/

Bye

  Thorsten
Comment 2 T. K. 2004-11-23 15:08:16 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Thorsten Schnebeck 2004-11-23 15:18:20 UTC
Hmm, after working a while with bibble (http://www.bibblelabs.com/) there is only one real solution: digikam should support 16bit/channel and handle RAW as a nomal fileformat. Meanwhile UFRaw is a good interim solution ;-)

Bye

  Thorsten

  
Comment 4 caulier.gilles 2006-05-04 15:11:24 UTC
Thorsten,

digiKam image editor 0.9.0 will handle RAW file formats with all dcraw options to decode image and an advanced ICC color profile support to render properly image in editor.

This is not possible to reproduce all internal digiKam features in this plugin (16 bits supports, preview like an editor, ICC, histogram correction etc.) and this is a non-sence to share all digikam core (API) with this plugin.

This plugin is dedicaced to hosts will support 8 bits images only not 16 bits. It will be disabled in digiKam in the future because an advanced batch Raw converter will be created in digiKam core using all digiKam API. This is necessary for pro-photographs RAW files workflow (like bibble program do).
Also, Single Raw converter is a non-sence because digiKam image editor can do it better (:=))...

In Fact, this plugin cannot be used by pro-photograph. Sure, it's can be improved (Exif preservation for example), and i will continue to maintain it in the future.

I close this file now...

Gilles Caulier
Comment 5 caulier.gilles 2006-05-04 15:16:17 UTC
closed