Git commit 39c4968f037e86f82b8fc1e14c43c7ba50415f97 by Gilles Caulier. Committed on 24/08/2016 at 09:28. Pushed by cgilles into branch 'master'.
reveiw Setup section D +- -- digikam/setupimageplugins.png R +- -- digikam/using-setup-addcamera.png [from: digikam/setupaddcamera.png - 100% similarity] R +- -- digikam/using-setup-album.png [from: digikam/setupalbum.png - 100% similarity] R +- -- digikam/using-setup-camera.png [from: digikam/setupcamera.png - 100% similarity] R +- -- digikam/using-setup-collections.png [from: digikam/setupcollections.png - 100% similarity] R +- -- digikam/using-setup-embeddedinfo.png [from: digikam/setupembeddedinfo.png - 100% similarity] R +- -- digikam/using-setup-iccprofiles.png [from: digikam/setupiccprofiles.png - 100% similarity] R +- -- digikam/using-setup-imageeditor.png [from: digikam/setupimageeditor.png - 100% similarity] R +- -- digikam/using-setup-kipiplugins.png [from: digikam/setupkipiplugins.png - 100% similarity] R +- -- digikam/using-setup-lighttable.png [from: digikam/setuplighttable.png - 100% similarity] R +- -- digikam/using-setup-mimetypes.png [from: digikam/setupmimetypes.png - 100% similarity] R +- -- digikam/using-setup-misc.png [from: digikam/setupmisc.png - 100% similarity] R +- -- digikam/using-setup-rawfiledecoding.png [from: digikam/setuprawfiledecoding.png - 100% similarity] R +- -- digikam/using-setup-saveimages.png [from: digikam/setupsaveimages.png - 100% similarity] R +- -- digikam/using-setup-slideshow.png [from: digikam/setupslideshow.png - 100% similarity] R +- -- digikam/using-setup-tooltip.png [from: digikam/setuptooltip.png - 100% similarity] M +132 -82 digikam/using-setup.docbook http://commits.kde.org/digikam-doc/39c4968f037e86f82b8fc1e14c43c7ba50415f97 diff --git a/digikam/setupimageplugins.png b/digikam/setupimageplugins.png deleted file mode 100644 index 1baf7b4..0000000 Binary files a/digikam/setupimageplugins.png and /dev/null differ diff --git a/digikam/setupaddcamera.png b/digikam/using-setup-addcamera.png similarity index 100% rename from digikam/setupaddcamera.png rename to digikam/using-setup-addcamera.png diff --git a/digikam/setupalbum.png b/digikam/using-setup-album.png similarity index 100% rename from digikam/setupalbum.png rename to digikam/using-setup-album.png diff --git a/digikam/setupcamera.png b/digikam/using-setup-camera.png similarity index 100% rename from digikam/setupcamera.png rename to digikam/using-setup-camera.png diff --git a/digikam/setupcollections.png b/digikam/using-setup-collections.png similarity index 100% rename from digikam/setupcollections.png rename to digikam/using-setup-collections.png diff --git a/digikam/setupembeddedinfo.png b/digikam/using-setup-embeddedinfo.png similarity index 100% rename from digikam/setupembeddedinfo.png rename to digikam/using-setup-embeddedinfo.png diff --git a/digikam/setupiccprofiles.png b/digikam/using-setup-iccprofiles.png similarity index 100% rename from digikam/setupiccprofiles.png rename to digikam/using-setup-iccprofiles.png diff --git a/digikam/setupimageeditor.png b/digikam/using-setup-imageeditor.png similarity index 100% rename from digikam/setupimageeditor.png rename to digikam/using-setup-imageeditor.png diff --git a/digikam/setupkipiplugins.png b/digikam/using-setup-kipiplugins.png similarity index 100% rename from digikam/setupkipiplugins.png rename to digikam/using-setup-kipiplugins.png diff --git a/digikam/setuplighttable.png b/digikam/using-setup-lighttable.png similarity index 100% rename from digikam/setuplighttable.png rename to digikam/using-setup-lighttable.png diff --git a/digikam/setupmimetypes.png b/digikam/using-setup-mimetypes.png similarity index 100% rename from digikam/setupmimetypes.png rename to digikam/using-setup-mimetypes.png diff --git a/digikam/setupmisc.png b/digikam/using-setup-misc.png similarity index 100% rename from digikam/setupmisc.png rename to digikam/using-setup-misc.png diff --git a/digikam/setuprawfiledecoding.png b/digikam/using-setup-rawfiledecoding.png similarity index 100% rename from digikam/setuprawfiledecoding.png rename to digikam/using-setup-rawfiledecoding.png diff --git a/digikam/setupsaveimages.png b/digikam/using-setup-saveimages.png similarity index 100% rename from digikam/setupsaveimages.png rename to digikam/using-setup-saveimages.png diff --git a/digikam/setupslideshow.png b/digikam/using-setup-slideshow.png similarity index 100% rename from digikam/setupslideshow.png rename to digikam/using-setup-slideshow.png diff --git a/digikam/setuptooltip.png b/digikam/using-setup-tooltip.png similarity index 100% rename from digikam/setuptooltip.png rename to digikam/using-setup-tooltip.png diff --git a/digikam/using-setup.docbook b/digikam/using-setup.docbook index 7cf6689..5a746c8 100644 --- a/digikam/using-setup.docbook +++ b/digikam/using-setup.docbook @@ -28,14 +28,14 @@ <listitem><para><link linkend="setup-miscellaneous">Miscellaneous Settings</link></para></listitem> </itemizedlist> - <sect3 id="setup-album"> <title>Album Settings</title> + <sect3 id="setup-album"> <title>Album Settings</title> <para> The Album settings control how the main application will behave. </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupalbum.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-album.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para> @@ -52,61 +52,64 @@ </sect3> - <sect3 id="setup-collection"> <title>Collection Settings</title> + <sect3 id="setup-collection"> <title>Collection Settings</title> <para> This dialog manages your Collection types. Album Collections are described in detail in the <link linkend="using-myalbumsview">Albums</link> section. </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupcollections.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-collections.png" format="PNG" /> </imageobject></inlinemediaobject> </para> </sect3> - <sect3 id="author-identity"> <title>Default Author Identity for IPTC</title> + <sect3 id="author-identity"> <title>Default Author Identity for IPTC</title> <para> This page contains the default identity and copyright data as shown on the printscreen below. The data will be automatically written into the respective IPTC data fields if so selected during the download from the <link linkend="using-cameraclientrenaming">camera interface</link>. Also, if you call for database synchronisation, this data will be written into the IPTC fields. </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;cameraclientidentity.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-camera-identity.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para>This is an extract of the IPTC specifications:</para> -<itemizedlist> - <listitem><para> - <emphasis>Author</emphasis> (is synonymous to <emphasis>Creator</emphasis> and <emphasis>By-line</emphasis>): This field should contain your name, or the name of the person who created the photograph. If it is not appropriate to add the name of the photographer (for example, if the identity of the photographer needs to be protected) the name of a company or organization can also be used. Once saved, this field should not be changed by anyone. This field does not support the use of commas or semi-colons as separator. - </para></listitem> - - <listitem><para> - <emphasis>Author title</emphasis> (synonymous with <emphasis>By-line title</emphasis>): This field should contain the job title of the photographer. Examples might include titles such as: Staff Photographer, Freelance Photographer, or Independent Commercial Photographer. Since this is a qualifier for the Author field, the Author field must also be filled out. - </para></listitem> - - <listitem><para> - <emphasis>Credit</emphasis> (synonymous with Provider): Use the credit field to identify who is providing the photograph. This does not necessarily have to be the author. If a photographer is working for a news agency such as Reuters or the Associated Press, these organizations could be listed here as they are "providing" the image for use by others. If the image is a stock photograph, then the group (agency) involved in supplying the image should be listed here. - </para></listitem> - - <listitem><para> - <emphasis>Source</emphasis>: The Source field should be used to identify the original owner or copyright holder of the photograph. The value of this field should never be changed after the information is entered following the image's creation. While not yet enforced by the custom panels, you should consider this to be a "write-once" field. The source could be an individual, an agency, or a member of an agency. To aid in later searches, it is suggested to separate any slashes "/" with a blank space. Use the form "photographer / agency" rather than "photographer/agency." Source may also be different from Creator and from the names listed in the Copyright Notice. - </para></listitem> - - <listitem><para> - <emphasis>Copyright Notice</emphasis>: The Copyright Notice should contain any necessary copyright notice for claiming the intellectual property, and should identify the current owner(s) of the copyright for the photograph. Usually, this would be the photographer, but if the image was done by an employee or as work-for-hire, then the agency or company should be listed. Use the form appropriate to your country. For the United States you would typically follow the form of © {date of first publication} name of copyright owner, as in "©2005 John Doe." Note, the word "copyright" or the abbreviation "copr" may be used in place of the © symbol. In some foreign countries only the copyright symbol is recognized and the abbreviation does not work. Furthermore the copyright symbol must be a full circle with a "c" inside; using something like (c) where the parentheses form a partial circle is not sufficient. For additional protection worldwide, use of the phrase, "all rights reserved" following the notice above is encouraged. In Europe you would use: Copyright {Year} {Copyright owner}, all rights reserved. In Japan, for maximum protection, the following three items should appear in the copyright field of the IPTC Core: (a) the word, Copyright; (b) year of the first publication; and (c) name of the author. You may also wish to include the phrase "all rights reserved." - </para></listitem> -</itemizedlist> + + <itemizedlist> + + <listitem><para> + <emphasis>Author</emphasis> (is synonymous to <emphasis>Creator</emphasis> and <emphasis>By-line</emphasis>): This field should contain your name, or the name of the person who created the photograph. If it is not appropriate to add the name of the photographer (for example, if the identity of the photographer needs to be protected) the name of a company or organization can also be used. Once saved, this field should not be changed by anyone. This field does not support the use of commas or semi-colons as separator. + </para></listitem> + + <listitem><para> + <emphasis>Author title</emphasis> (synonymous with <emphasis>By-line title</emphasis>): This field should contain the job title of the photographer. Examples might include titles such as: Staff Photographer, Freelance Photographer, or Independent Commercial Photographer. Since this is a qualifier for the Author field, the Author field must also be filled out. + </para></listitem> + + <listitem><para> + <emphasis>Credit</emphasis> (synonymous with Provider): Use the credit field to identify who is providing the photograph. This does not necessarily have to be the author. If a photographer is working for a news agency such as Reuters or the Associated Press, these organizations could be listed here as they are "providing" the image for use by others. If the image is a stock photograph, then the group (agency) involved in supplying the image should be listed here. + </para></listitem> + + <listitem><para> + <emphasis>Source</emphasis>: The Source field should be used to identify the original owner or copyright holder of the photograph. The value of this field should never be changed after the information is entered following the image's creation. While not yet enforced by the custom panels, you should consider this to be a "write-once" field. The source could be an individual, an agency, or a member of an agency. To aid in later searches, it is suggested to separate any slashes "/" with a blank space. Use the form "photographer / agency" rather than "photographer/agency." Source may also be different from Creator and from the names listed in the Copyright Notice. + </para></listitem> + + <listitem><para> + <emphasis>Copyright Notice</emphasis>: The Copyright Notice should contain any necessary copyright notice for claiming the intellectual property, and should identify the current owner(s) of the copyright for the photograph. Usually, this would be the photographer, but if the image was done by an employee or as work-for-hire, then the agency or company should be listed. Use the form appropriate to your country. For the United States you would typically follow the form of © {date of first publication} name of copyright owner, as in "©2005 John Doe." Note, the word "copyright" or the abbreviation "copr" may be used in place of the © symbol. In some foreign countries only the copyright symbol is recognized and the abbreviation does not work. Furthermore the copyright symbol must be a full circle with a "c" inside; using something like (c) where the parentheses form a partial circle is not sufficient. For additional protection worldwide, use of the phrase, "all rights reserved" following the notice above is encouraged. In Europe you would use: Copyright {Year} {Copyright owner}, all rights reserved. In Japan, for maximum protection, the following three items should appear in the copyright field of the IPTC Core: (a) the word, Copyright; (b) year of the first publication; and (c) name of the author. You may also wish to include the phrase "all rights reserved." + </para></listitem> + + </itemizedlist> </sect3> - <sect3 id="setup-embeddedinfo"> <title>Metadata (embedded information settings)</title> + <sect3 id="setup-embeddedinfo"> <title>Metadata (embedded information settings)</title> <para> Image files can have some meta-data embedded into the image file format. This meta-data can be stored in a number of standard formats. &digikam; can read meta-data in the EXIF format if it is present in the file. &digikam; can also write captions into the <ulink url="http://www.exif.org";>EXIF information</ulink>. Writing captions to the EXIF section is limited to JPEG images for now (the exiv2 library is in development and will be extended to PNG and TIFF format metadata embedding in the near future). </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupembeddedinfo.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-embeddedinfo.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para> @@ -138,7 +141,7 @@ </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setuptooltip.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-tooltip.png" format="PNG" /> </imageobject></inlinemediaobject> </para> </sect3> @@ -148,10 +151,13 @@ <para> &digikam; can understand lots of different image file types as well as some video and audio formats. To control which types of files &digikam; will try to display you can add or remove file extensions from these lists. Any files that are in the &digikam; Album folders that do not match these extensions will be ignored by &digikam;. </para> - <note><para>The default settings can be easily restored by clicking on the update buttons to the right of each category.</para></note> + + <note> + <para>The default settings can be easily restored by clicking on the update buttons to the right of each category.</para> + </note> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupmimetypes.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-mimetypes.png" format="PNG" /> </imageobject></inlinemediaobject> </para> </sect3> @@ -161,34 +167,41 @@ <para> The setting of the &digikam; Light Table can be set to default values on this page so that every time you open the Light Table, these settings are activated (if possible, because for images having different sizes the synchronous mode does not work). The "Load full image size" is only recommended for fast maschines, but if you have one, enable this option for better viewing results. </para> + <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setuplighttable.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-lighttable.png" format="PNG" /> </imageobject></inlinemediaobject> </para> </sect3> - <sect3 id="setup-editor"> <title>Image Editor Settings</title> + <sect3 id="setup-editor"> <title>Image Editor Settings</title> + <para> By default the Image Editor will use a black background behind photographs when they are displayed. If you prefer a different background color you can choose one here. You can also turn off the ToolBar when the Image Editor is in full screen mode. </para> + <para> - Over and underexposed areas of an image can be indicated by dark and light marker colors that can be defined here. In the editor this viewing mode can be switched on and off with F10 and F11 respectively.</para> + Over and underexposed areas of an image can be indicated by dark and light marker colors that can be defined here. In the editor this viewing mode can be switched on and off with F10 and F11 respectively. + </para> + <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupimageeditor.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-imageeditor.png" format="PNG" /> </imageobject></inlinemediaobject> </para> </sect3> - <sect3 id="setup-saveimages"> <title>Save Image Options</title> + <sect3 id="setup-saveimages"> <title>Save Image Options</title> <para> When changes are made to JPEG files and they are saved back to the hard disk the JPEG file must be re-encoded. Each time a JPEG file is encoded a decision must be made on the level of quality that is to be applied. Unfortunately the level of quality applied is not recorded in the image file. This means that the Image Editor cannot use the same quality ratio when saving an altered image as was used for the original image. You can change the default level of quality that the Image Editor will apply when it saves altered images by moving the <guilabel>JPEG quality</guilabel> slider (1: low quality / 100: high quality and no compression). </para> + <para> Chroma subsampling is the practice of encoding images by implementing more resolution for luminance information than for color information. Please read <ulink url="http://en.wikipedia.org/wiki/Chroma_subsampling";>this</ulink> Wikipedia article for a full explanation. </para> + <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupsaveimages.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-saveimages.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para> @@ -205,128 +218,161 @@ </sect3> - <sect3 id="setup-raw-decoder"> <title>RAW Decoder Settings</title> + <sect3 id="setup-raw-decoder"> <title>RAW Decoder Settings</title> <para> In the early versions of &digikam; the Image Editor was just a viewer for photographs, but it is rapidly developing into a very useful photo manipulation tool. This dialog allows you to control how the Image Editor will behave. </para> - <para><guilabel>16-bit color depth</guilabel></para> + <para> + <guilabel>16-bit color depth</guilabel> + </para> + <para>If enabled, all RAW files will be decoded to 16-bit color depth using a linear gamma curve. To prevent dark image rendering in the editor, it is recommended to use Color Management in this mode. If disabled, all RAW files will be decoded to 8-bit color depth with a BT.709 gamma curve and a 99th-percentile white point. This mode is faster than 16-bit decoding. In 8-bit mode only will the <guilabel>brightness</guilabel> setting be taken into account (dcraw limitation). </para> - <para><guilabel>Interpolate RGB as four colors</guilabel></para> + <para> + <guilabel>Interpolate RGB as four colors</guilabel> + </para> + <para>The default is to assume that all green pixels are the same. If even-row green pixels of the CCD sensor are more sensitive to ultraviolet light than odd-row this difference causes a mesh pattern in the output; using this option solves this problem with minimal loss of detail. To resume, this option blurs the image a little, but it eliminates false 2x2 mesh patterns with VNG quality method or mazes with AHD quality method.</para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setuprawfiledecoding.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-rawfiledecoding.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para><guilabel>Use camera white balance</guilabel></para> <para>Use the camera's custom white-balance settings if set. Otherwise apply <guilabel>Automatic color balance</guilabel> if this option is set.</para> <para><guilabel>Automatic color balance</guilabel></para> + <para>Only used if camera white balance is not set. The default is to use a fixed color balance based on a white card photographed in sunlight.</para> <para><guilabel>Use Super CCD secondary sensors</guilabel></para> + <para>For Fuji Super CCD SLR cameras only. Use the secondary sensors, in effect underexposing the image by four stops to reveal detail in the highlights. For all other camera types this option is being ignored.</para> <para><guilabel>Highlights</guilabel></para> + <para>This is the story of the three highlight options, courtesy of Nicolas Vilars:</para> + <para>Default is here to consider highlights (read: part of your images that are burned due to the inability of your camera to capture the highlights) as plain / solid white (<guilabel>solid white</guilabel> option). You can get some fancy results with the <guilabel>unclip</guilabel> option which will paint the highlights in various pinks. At last you can try to consider recovering some parts of the missing information from the highlights (<guilabel>reconstruct</guilabel> option).</para> + <para> - This is possible because the blue pixels tends to saturate less quickly than the greens and the reds. &digikam;/dcraw will try to reconstruct the missing green and red colors from the remaining none saturated blue pixels. Of course here everything is a question of tradeoff between how much color or white you want.</para> + This is possible because the blue pixels tends to saturate less quickly than the greens and the reds. &digikam;/dcraw will try to reconstruct the missing green and red colors from the remaining none saturated blue pixels. Of course here everything is a question of tradeoff between how much color or white you want. + </para> + <para>If you select <guilabel>reconstruct</guilabel> as the option, you will be given the choice to set a level. A value of 3 is a compromise and can/should be adapted on a per image basis.</para> + <note><para> - A small warning here, for the few curious that have read the man pages of Dcraw, the author says that 5 is the compromise, 0 is solid white and 1 unclip. This is because in &digikam; 0 and 1 are the "solid white" and "unclip" options in the drop down menu (if you select these, the level slider will be grayed out). Therefore, the slider in &digikam; with the "reconstruct" option will let you choose between 0 to 7 (instead of 0 to 9 in Dcraw command line) where 3 is the compromise instead of 5 in "native" Dcraw command line tool.</para></note> + A small warning here, for the few curious that have read the man pages of Dcraw, the author says that 5 is the compromise, 0 is solid white and 1 unclip. This is because in &digikam; 0 and 1 are the "solid white" and "unclip" options in the drop down menu (if you select these, the level slider will be grayed out). Therefore, the slider in &digikam; with the "reconstruct" option will let you choose between 0 to 7 (instead of 0 to 9 in Dcraw command line) where 3 is the compromise instead of 5 in "native" Dcraw command line tool. + </para></note> <para><guilabel>Brightness</guilabel> (works in 8 bit mode only)</para> + <para> Set the luminosity to your taste, you probably need to go a little higher than the default = 1. But this can be adjusted later with the image options in the &digikam; image editor. Given the cost in time for demosaicing, stay conservative. </para> <para><guilabel>Quality</guilabel></para> + <para> - A <ulink url="http://en.wikipedia.org/wiki/Demosaicing";>demosaicing</ulink> algorithm is a digital image process used to interpolate a complete image from the partial raw data received from the color-filtered image sensor internal to many digital cameras in form of a matrix of colored pixels. Also known as CFA interpolation or color reconstruction.</para> + A <ulink url="http://en.wikipedia.org/wiki/Demosaicing";>demosaicing</ulink> algorithm is a digital image process used to interpolate a complete image from the partial raw data received from the color-filtered image sensor internal to many digital cameras in form of a matrix of colored pixels. Also known as CFA interpolation or color reconstruction. + </para> + <para> - &digikam; and Dcraw offer us three alternatives: bi-linear, VNG interpolation, AHD interpolation. It seems that <emphasis>AHD interpolation</emphasis> (for Adaptive Homogeneity-Directed) is the best choice for quality according to some test that I have performed and the paper of the person that implemented it. <emphasis>VNG interpolation</emphasis> (Variable Number of Gradients) was the first algorithm used by Dcraw but suffers from color artifacts on the edge. <emphasis>Bilinear</emphasis> is interesting if you are looking for speed with a acceptable result.</para> + &digikam; and Dcraw offer us three alternatives: bi-linear, VNG interpolation, AHD interpolation. It seems that <emphasis>AHD interpolation</emphasis> (for Adaptive Homogeneity-Directed) is the best choice for quality according to some test that I have performed and the paper of the person that implemented it. <emphasis>VNG interpolation</emphasis> (Variable Number of Gradients) was the first algorithm used by Dcraw but suffers from color artifacts on the edge. <emphasis>Bilinear</emphasis> is interesting if you are looking for speed with a acceptable result. + </para> - <para><guilabel>Enable Noise Reduction</guilabel></para> - <para> + <para><guilabel>Enable Noise Reduction</guilabel></para> + + <para> While demosaicing your image you can additionally ask for noise reduction (at a slight speed penalty). This option applies a noise reduction algorithm while the image still is in CIE Lab color space. Because the noise is only applied to the Luminosity layer (the "L" of the Lab), it should not blur your image as traditional noise reduction algorithms do in RGB mode. So, if you converted an image from RAW and it appears noisy, rather than applying a denoiser, go back and re-convert with this option enabled. The defaults are: <emphasis>Threshold</emphasis> = 100. Higher values will increase the smoothing, lower will decrease smoothing. </para> <anchor id="CA.anchor"/> + <para><guilabel>Enable chromatic aberration (CA) correction</guilabel></para> + <para> If you know the CA of your lenses you can set the red and blue correction values here. This is certainly the optimal method for CA correction as it is done during RAW conversion. </para> </sect3> - <sect3 id="setup-iccprofiles"> <title>ICC Profiles setup</title> + <sect3 id="setup-iccprofiles"> <title>ICC Profiles setup</title> <para> &digikam; is color-management enabled. RAW files - as they come - are not color managed at all. Your camera provides the data it has captured in a raw format and will let you manage all the processing. Every camera has its specifics as to how it captures color information, therefore you will need to apply a specific profile to the images you want to process. Please refer to the section <link linkend="using-iccprofile">ICC color profile management</link> for more details an explanations. </para> + <para> Basically, a profile "maps" the color information and gives information on how one should render them. It gives also information to LCMS and &digikam; on how to translate the color information from one color space to an other in order to keep the colors as accurate as possible across all rendring media. </para> + <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupiccprofiles.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-iccprofiles.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para> <guilabel>Behavior</guilabel> Ask when opening an image in image editor / Launch Color Management tool with RAW files </para> + <para><guilabel>Color Profiles Directory</guilabel> Set this to the folder where you store all your profiles ⪚ "/usr/share/color/icc" or "/home/user/.color/icc". &digikam; will scan this folder when starting up.</para> + <para><guilabel>ICC Profiles Settings</guilabel> Here you are given the ability to provide "default" choices for your profiles. Everything is adaptable later-on at the opening of a RAW file.</para> + <itemizedlist> - <listitem><para>The <guilabel>Use color managed view</guilabel> is an alternative to using Xcalib or Argyll. Only your image will be color managed, not your entire screen! </para></listitem> + <listitem><para>The <guilabel>Use color managed view</guilabel> is an alternative to using Xcalib or Argyll. Only your image will be color managed, not your entire screen! </para></listitem> - <listitem><para> - You have to provide a workspace profile (linear profiles such as sRGB, ECI-RGB, LStar-RGB, Adobe-RGB or CIE-RGB). If you want to print your images, you may want to opt for Adobe RGB, if it is only for web publishing, sRGB is better (Adobe RGB will be displayed slightly dull in non color managed enabled software such as browsers). However you may change this later of course (by attributing another profile), therefore Adobe RGB can be a good choice for storing and image handling as you can always change it to sRGB before releasing an image for your blog.</para><para>Do not use non-linear profiles as they will change the color-balance</para> - </listitem> + <listitem><para> + You have to provide a workspace profile (linear profiles such as sRGB, ECI-RGB, LStar-RGB, Adobe-RGB or CIE-RGB). If you want to print your images, you may want to opt for Adobe RGB, if it is only for web publishing, sRGB is better (Adobe RGB will be displayed slightly dull in non color managed enabled software such as browsers). However you may change this later of course (by attributing another profile), therefore Adobe RGB can be a good choice for storing and image handling as you can always change it to sRGB before releasing an image for your blog.</para><para>Do not use non-linear profiles as they will change the color-balance</para> + </listitem> - <listitem><para> - The input profile should match the camera maker and model you are using. 'Not all profiles are created equal', there are some that have no tone mapping/gamma correction included (Canon). As of now, dcraw does not correct gamma for 16 bit depth conversion, which means that you have to do the tone mapping yourself.</para></listitem> + <listitem><para> + The input profile should match the camera maker and model you are using. 'Not all profiles are created equal', there are some that have no tone mapping/gamma correction included (Canon). As of now, dcraw does not correct gamma for 16 bit depth conversion, which means that you have to do the tone mapping yourself.</para></listitem> - <listitem><para> - There are some other options such as the soft proof profile which enables you to emulate, granted that you have a profile for it, how your image will render for a particular device. It is useful before printing for instance because your printer has a smaller gamut than your camera and some colors might look saturated. You may want to fix this manually instead of relying on the "blind" algorithm of your printer.</para></listitem> + <listitem><para> + There are some other options such as the soft proof profile which enables you to emulate, granted that you have a profile for it, how your image will render for a particular device. It is useful before printing for instance because your printer has a smaller gamut than your camera and some colors might look saturated. You may want to fix this manually instead of relying on the "blind" algorithm of your printer.</para></listitem> </itemizedlist> <para> For most cameras it is pretty obvious what color profile they propose for the type at hand, not so for the Canon's. Here is a table of camera/profiles matches, it is non-authoritative of course: </para> + <informaltable><tgroup cols="2"> - <thead><row> - <entry>Camera</entry> - <entry>Profile series</entry> + + <thead><row> + <entry>Camera</entry> + <entry>Profile series</entry> </row></thead> + <tbody> - <row> <entry>Canon 1D mark II</entry> <entry>6051</entry> </row> - <row> <entry>Canon 1D mark II</entry> <entry>6111</entry> </row> - <row> <entry>Canon 1Ds</entry> <entry>6021</entry> </row> - <row> <entry>Canon 1Ds mark II</entry> <entry>6081</entry> </row> - <row> <entry>Canon 5D</entry> <entry>6091</entry> </row> - <row> <entry>Canon 10D</entry> <entry>6031</entry> </row> - <row> <entry>Canon 20D</entry> <entry>6061</entry> </row> - <row> <entry>Canon 30D</entry> <entry>6112</entry> </row> - <row> <entry>Canon 40D</entry> <entry>6101</entry> </row> - <row> <entry>Canon 300D</entry> <entry>6031</entry> </row> - <row> <entry>Canon 350D</entry> <entry>6111 or 6071</entry> </row> - <row> <entry>Canon 400D</entry> <entry>6131</entry> </row> - </tbody> - </tgroup> - </informaltable> + <row> <entry>Canon 1D mark II</entry> <entry>6051</entry> </row> + <row> <entry>Canon 1D mark II</entry> <entry>6111</entry> </row> + <row> <entry>Canon 1Ds</entry> <entry>6021</entry> </row> + <row> <entry>Canon 1Ds mark II</entry> <entry>6081</entry> </row> + <row> <entry>Canon 5D</entry> <entry>6091</entry> </row> + <row> <entry>Canon 10D</entry> <entry>6031</entry> </row> + <row> <entry>Canon 20D</entry> <entry>6061</entry> </row> + <row> <entry>Canon 30D</entry> <entry>6112</entry> </row> + <row> <entry>Canon 40D</entry> <entry>6101</entry> </row> + <row> <entry>Canon 300D</entry> <entry>6031</entry> </row> + <row> <entry>Canon 350D</entry> <entry>6111 or 6071</entry> </row> + <row> <entry>Canon 400D</entry> <entry>6131</entry> </row> + </tbody> + + </tgroup></informaltable> + <para>The Canon profile extension betray the target style: F for Faithful Style, L for Landscape Style, N for Neutral Style, P for Portrait Style, S for Standard Style. </para> <para>Here you find a typical <link linkend="raw-workflow">RAW workflow</link> scenario.</para> + </sect3> <sect3 id="setup-kipiplugins"> <title>Kipi Plugins Settings</title> @@ -336,7 +382,7 @@ </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupkipiplugins.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-kipiplugins.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para> @@ -355,11 +401,13 @@ </sect3> - <sect3 id="setup-slideshow"> <title>Slide show setup</title> + <sect3 id="setup-slideshow"> <title>Slide show setup</title> <para>The slide show setup should be easy to understand. The upper slider adjusts the time between image transitions; usually a time of 4-5 seconds is good. The other check boxes enable/disable the metadata to be shown on the bottom of the slide show images during display.</para> + <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupslideshow.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-slideshow.png" format="PNG" /> </imageobject></inlinemediaobject> </para> + </sect3> <sect3 id="setup-camera"> <title>Camera Interface Settings</title> @@ -369,7 +417,7 @@ </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupcamera.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-camera.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <anchor id="cameraselection.anchor"/> @@ -383,7 +431,7 @@ </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupaddcamera.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-addcamera.png" format="PNG" /> </imageobject></inlinemediaobject> </para> <para> @@ -416,12 +464,13 @@ </para> <anchor id="rescan-items" /> + <para> <guilabel>Scan for new items at startup</guilabel> option will force &digikam; to scan the album library tree for new items added or removed between &digikam; sessions. This may slow down the start time of &digikam;. If any items have been removed from album library, &digikam; will ask you confirmation before to remove definitely item references in database. </para> <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupmisc.png" format="PNG" /> </imageobject></inlinemediaobject> + <inlinemediaobject><imageobject><imagedata fileref="&path;using-setup-misc.png" format="PNG" /> </imageobject></inlinemediaobject> </para> </sect3> @@ -435,6 +484,7 @@ <menuchoice><guimenu>Settings</guimenu> <guimenuitem>Themes</guimenuitem></menuchoice> from the menubar and select your preferred theme to use. </para> + </sect2> </sect1>
