Git commit 3cc1a04e4e09133690d3327cd7dd73db83a76d05 by Gilles Caulier. Committed on 23/08/2016 at 10:53. Pushed by cgilles into branch 'master'.
split more Using chapter sections M +12 -728 digikam/index.docbook A +288 -0 digikam/using-camera.docbook A +448 -0 digikam/using-setup.docbook http://commits.kde.org/digikam-doc/3cc1a04e4e09133690d3327cd7dd73db83a76d05 diff --git a/digikam/index.docbook b/digikam/index.docbook index 5beee16..d58f301 100644 --- a/digikam/index.docbook +++ b/digikam/index.docbook @@ -5,20 +5,22 @@ <!ENTITY % addindex "IGNORE"> <!ENTITY % English "INCLUDE"><!-- change language only here --> <!ENTITY digikam '<application>digiKam</application>'> -<!-- relative path to snapshots for digikam and showfoto --> - <!ENTITY path ""> -<!-- introduction --> + <!ENTITY path ""><!-- relative path to snapshots for digikam and showfoto --> + +<!-- Introduction Chapter --> <!ENTITY doc-intro-background SYSTEM "intro-background.docbook"> <!ENTITY doc-intro-firstrun SYSTEM "intro-firstrun.docbook"> <!ENTITY doc-intro-fileformats SYSTEM "intro-fileformats.docbook"> <!ENTITY doc-intro-camerasupport SYSTEM "intro-camerasupport.docbook"> <!ENTITY doc-intro-pluginsupport SYSTEM "intro-pluginsupport.docbook"> -<!-- using application --> +<!-- Using Application Chapter --> <!ENTITY doc-using-mainwindow SYSTEM "using-mainwindow.docbook"> <!ENTITY doc-using-sidebar SYSTEM "using-sidebar.docbook"> <!ENTITY doc-using-lighttable SYSTEM "using-lighttable.docbook"> <!ENTITY doc-using-dam SYSTEM "using-dam.docbook"> -<!-- image editor --> + <!ENTITY doc-using-camera SYSTEM "using-camera.docbook"> + <!ENTITY doc-using-setup SYSTEM "using-setup.docbook"> +<!-- Image Editor Chapter --> <!ENTITY doc-photo-editing SYSTEM "photo-editing.docbook"> <!ENTITY doc-editor-color SYSTEM "editor-color.docbook"> <!ENTITY doc-editor-enhance SYSTEM "editor-enhance.docbook"> @@ -26,16 +28,16 @@ <!ENTITY doc-editor-filters SYSTEM "editor-filters.docbook"> <!ENTITY doc-editor-decorate SYSTEM "editor-decorate.docbook"> <!ENTITY doc-color-management SYSTEM "color-management.docbook"> -<!-- batch queue manager --> +<!-- Batch Queue Manager Chapter --> <!ENTITY doc-bqm-mainwindow SYSTEM "bqm-mainwindow.docbook"> <!ENTITY doc-bqm-rawconverter SYSTEM "bqm-rawconverter.docbook"> -<!-- tools --> +<!-- Tools Chapter --> <!ENTITY doc-tool-acquireimages SYSTEM "tool-acquireimages.docbook"> <!ENTITY doc-tool-geolocationeditor SYSTEM "tool-geolocationeditor.docbook"> <!ENTITY doc-tool-presentation SYSTEM "tool-presentation.docbook"> <!ENTITY doc-tool-advrename SYSTEM "tool-advrename.docbook"> <!ENTITY doc-tool-metadataeditor SYSTEM "tool-metadataeditor.docbook"> -<!-- menus --> +<!-- Menus --> <!ENTITY doc-menu-descriptions SYSTEM "menu-descriptions.docbook"> <!ENTITY doc-ie-menu SYSTEM "ie-menu.docbook"> <!ENTITY doc-credits-annexes SYSTEM "credits-annex.docbook"> @@ -118,727 +120,9 @@ &doc-using-dam; - <sect1 id="using-camera"> <title>Using a Digital Camera With &digikam;</title> - <anchor id="camerainterface.anchor"/> - - <sect2> <title>Introduction to Camera Interface</title> - - <para> - The Camera Tool allows you to download your photographs directly from your camera into a &digikam; Album. You can access the Camera Tool by clicking on the Camera menu and selecting from the list of configured cameras. See the <link linkend="setup-camera">Setup Camera Section</link> of the manual for instructions on how to setup &digikam; to work with your camera. If you want to have more information about how &digikam; supports digital cameras, please a take a look at <link linkend="intro-camerasupport">this section</link>. - </para> - - <para> - The Camera Interface is not the only way to get your photographs into &digikam;. See the <link linkend="using-addphototoalbum">Adding a photograph to an Album</link> section for a description of how to add photographs that are already on your hard disk. But Camera Interface provides a lots of advanced settings to import images into your albums database. - </para> - - <para> - To be able to use your digital camera with &digikam;, connect the camera to your computer, switch the camera to the image display mode and turn it on. See you camera's user manual if you need more information. - </para> - - <para> - When you start the Camera Interface, it will try to connect to the Camera. For some cameras this connection phase can take a little while. When connected, a <guilabel>Ready</guilabel> indicator will appear on the bottom and thumbnails of any photographs on the camera will be displayed. Some cameras cannot provide thumbnails of the photographs. If this is the case, you will only see the filenames and a mime-type icon for each item stored by your camera (photograph, movies, sounds, etc). - </para> - - <example> <title>The Camera Client Window</title> - <screenshot><screeninfo>The Camera Client Window</screeninfo> <mediaobject><imageobject><imagedata fileref="&path;cameraclient.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - </sect2> - - <sect2> - <title>Getting information about photographs from the Camera</title> - - <para> - Before downloading photographs to your computer, you may wish to see camera item information. Using the - <menuchoice><guimenuitem>Properties</guimenuitem></menuchoice> and <menuchoice><guimenuitem>Metadata</guimenuitem></menuchoice> side bar tabs from Camera Interface will launch camera item properties and metadata information. - </para> - - <example> <title>The Camera Item Properties Sidebar Tab</title> - <screenshot><screeninfo>The camera item properties sidebar Tab</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientitemproperties.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - <para> - The Properties tab displays file information recorded by the camera and a resume of photographer information to describe how the image has been taken. A flag indicates if the image has not yet been downloaded to the computer. Note, all this information may be unavailable with some digital cameras. - </para> - - <para> - The Metadata tab displays an internal picture's metadata like EXIF, Makernotes, GPS, &etc; This information is the same as <link linkend="using-sidebarmetadata">sidebar Meta-Data</link> from the &digikam; main interface or image editor. Note, all these metadata can be unavailable with some digital cameras. - </para> - - </sect2> - - <sect2> - <title>Downloading photographs to your computer</title> - - <para> - The simplest way to download photographs from your camera to your computer is to click the <guilabel>Download</guilabel> button and then click <guilabel>Download All</guilabel>. This will download all of the photographs on the camera to a single Album in &digikam;. The download process will not remove the photographs from the camera. It is always advisable to check that the photographs have downloaded safely into the Album you were expecting before deleting them from the camera. - </para> - - <para> - If you do not want to download all of the photographs you can select just those that you need using the standard selection methods. Once you have the photographs selected, click <guilabel>Download</guilabel> and then <guilabel>Download Selected</guilabel>. The <guilabel>Download Selected</guilabel> button will be grayed out until you have selected some photographs. - </para> - - <note><para> - If supported by your camera an option <guilabel>Download new</guilabel> is available. Those are images not yet downloaded by &digikam;. In that case the new images are already marked with a star in the thumbnail window. Obviously if you choose this handy option, it will download the new images only. - </para></note> - - </sect2> - - <sect2> - <title>Selecting a Target Album</title> - <anchor id="targetalbumdialog.anchor"/> - - <para> - Using <guilabel>Download All</guilabel> or <guilabel>Download Selected</guilabel> buttons will bring up a dialog, that allows you to select a target Album into which the photographs will be downloaded. The list of existing Albums is displayed, ordered by the Folder method (see the <link linkend="using-myalbumsview">Albums View</link> for details of Album ordering). You can select the target Album from this list and then click OK. - </para> - - <example> <title>The Target Album Selection Dialog</title> - <screenshot><screeninfo>The Target Album Selection Dialog</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameratargetalbumdialog.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - <para> - If you want to create a new Album, into which you could download the photographs, click the <guilabel>New Album</guilabel> button. The new Album will be created as a sub-folder of the Album that is currently selected in the existing Album list. This means that, if you do not want your new Album to be a sub-folder of an existing folder, you must first select the "My Albums" entry from the very top of the existing Albums list before creating a new Album. - </para> - - <para> - When you have selected the target Album, click OK and &digikam; will download the photographs from the camera to that album. - </para> - - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;cameraclientdownload.png" format="PNG" /> </imageobject><textobject><phrase>The Downloading in Progress</phrase></textobject></inlinemediaobject> - </para> - - </sect2> - - <sect2> - <title>Deleting photographs from the camera</title> - - <para> - Once you are happy with the downloaded photographs that you wanted, you are ready to delete photographs from the Camera. You can delete all of the photographs at once by clicking the - <menuchoice> - <guimenu>Delete</guimenu> - <guimenuitem>Delete All</guimenuitem> - </menuchoice> - button. If you just want to delete a selection of the photographs, you have to select those that you want to delete and click - <menuchoice><guimenu>Delete</guimenu> - <guimenuitem>Delete Selected</guimenuitem></menuchoice> - </para> - - <caution><para> - Please note that there is no way to restore a photo that you have deleted from the camera. The photographs are not moved to the internal Trash Can, they are removed completely. It is best to double check that you have successfully downloaded a photograph into a &digikam; Album before you delete it from the camera. Anyway, if you plan to empty the camera card, you better do that from the camera menu because it is much quicker. - </para></caution> - - </sect2> - - <sect2 id="using-cameraclientrenaming"> - <title>Automatic Renaming</title> - - <para> - Cameras often do not use very meaningful filenames for photographs. The filenames are usually reused once the photographs have been deleted from the camera. This can lead to filename clashes if you download photographs from many shootings into the same Album. It can also be useful to include the date and time that an image was taken into the filename. - </para> - - <example> <title>Files Renaming Options</title> - <screenshot><screeninfo>Files Renaming Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting1.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - <para> - &digikam; can automatically rename your photographs using the date and time information included by the camera in the photograph. To use this feature, click the <guilabel>Settings</guilabel> button on the Camera Interface. The Camera Interface window will expand to reveal some extra features. Select <guilabel>Customize</guilabel> and then enter any filename prefix you would like. As an option you can add many information independently or by combination including : date, time, original file name, file extension, directory, owner, group, camera name, a sequence number or any other metadata from the photograph. - </para> - <para> - </para> - <para> - In the next box you find the options for rotating/flipping the image and for date based subalbums. If you check the latter option, folder per day will be automatically generated. - </para> - <para> - The 'On the fly operations' open three more options that act on the photos before storing them on disk. The first two relate to the authors data in <link linkend="author-identity">Default Author Identity</link> settings. If checked, the respective items will be copied into the EXIF tags and IPTC fields. The last option allows a date & time for all downloaded photographs to be set. - </para> - - <tip> - <para> - <itemizedlist> - - <listitem><para>The sequence number may be needed if you have a camera with a very fast multi-shoot mode where it is possible to get two photographs with exactly the same data and time. - </para></listitem> - - <listitem><para>If you want another date format then the default date format, click on <guilabel>Date & Time...</guilabel>, choose <guilabel>Custom</guilabel> in <guilabel>Format</guilabel> drop-down list and fill in for example "dd.MM.yyyy hh:mm:ss". For more information, read <ulink url="http://doc.qt.digia.com/qt/qdatetime.html#toString";>QdateTime</ulink> class reference.</para></listitem> - - <listitem><para>When you select <guilabel>Camera filenames</guilabel>, you have the option to change the filenames to lowercase when downloading. Or use uppercase if you prefer.</para></listitem> - - </itemizedlist> - </para> - </tip> - - <para> - The new filename that &digikam; will use for the photographs when they are downloaded is shown underneath the name provided by the camera in the thumbnail view. The renaming settings will be remembered the next time you use the camera interface. - </para> - - </sect2> - - <sect2> - <title>Camera Information Based Operations</title> - - <sect3> - <title>Automatic Rotation</title> - - <para> - &digikam; can use any information about the orientation of the camera at the moment the photograph was taken for automatic rotation of the photograph when it is downloaded. Not all cameras include this information. See the <link linkend="using-sidebarmetadata">sidebar Meta-Data</link> section for more detail about information that your camera may have embedded in your photographs. - </para> - - <example> <title>On the fly Operations Options</title> - <screenshot><screeninfo>On the fly Operations Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting2.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - <para> - This automatic rotation is switched on by default, and if your camera does not include the information, &digikam; will leave the photograph at its original orientation. If you would like to switch the automatic rotation off, click the <guilabel>Advanced</guilabel> button and deselect the <guilabel>Auto Orient</guilabel> option at the bottom of the window. - </para> - - </sect3> - - <sect3> - <title>Automatic Destination Albums Creation</title> - - <para> - If your camera provides information about the date of the photograph's taking, &digikam; can use this to automatically create subalbums in the destination Album when it is downloaded. Subalbums names will be based on image dates. All images which have the same date will be downloaded into the same subalbum. Not all cameras include this information. - See the <link linkend="using-sidebarmetadata"> - sidebar Meta-Data</link> section for more detail about - information your camera may have embedded in your photographs. - </para> - - <example> <title>Albums Auto-creation Options</title> - <screenshot><screeninfo>Albums Auto-creation Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting3.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - <para> - This option is switched off by default and in this case &digikam; will download the photographs - in the root destination Albums. If you would like to switch on this option click the - <guilabel>Advanced</guilabel> button and select the <guilabel>Download photo in automatically</guilabel> - option at the bottom of the window. - </para> - - </sect3> - - </sect2> - - <sect2> - <title>Uploading Photographs to your camera</title> - - <para> - The simplest way to upload photographs from your computer to your camera is to click the <guilabel>Download</guilabel> button and then click <guilabel>Upload</guilabel>. A standard file selection dialog will appear to select the files from your computer to copying on your camera. You can select more than one file using the standard selection methods. - </para> - - <para> - When images selection is done, &digikam; will ask you where you want to upload the files on your camera. A camera folder selection dialog will appear. Just select one folder and press OK to start uploading. No images will be removed from your computer. - </para> - - <example> <title>The Camera Folder Selection Dialog</title> - <screenshot><screeninfo>The Camera Folder Selection Dialog</screeninfo><mediaobject><imageobject><imagedata fileref="&path;camerafolderselectiondialog.png" format="PNG" /> </imageobject></mediaobject></screenshot> - </example> - - <note><para> - Uploading feature is not supported by all camera drivers. - </para></note> - - </sect2> - - <sect2 id="using-gps"> - <title>How to use a GPS device with &digikam;</title> - <note><para> - <inlinemediaobject> - <imageobject><imagedata fileref="&path;handheld_gps.png" format="PNG"/></imageobject> - </inlinemediaobject>GPS (global positioning system) is used as a generic term throughout this document. It just means a location in latitude and longitude global coordinates that can be displayed on a map. The actual technical implementation that provides the data can be the American GPS, the Russian GLONAS, the European GALILEO or any other system. - </para></note> - - <para> - Not only for professional photographers can it be interesting to link an image to a precise geographical location. Not everybody uses an airplane to overfly and scan a certain area with automatic GPS data recording. Environmental planners, military, police, construction bureaus, real estate agencies, all will have an immediate application. - </para> - <para> - But if, after some time, one has forgotten where the image was taken, if one loves the nice feature to open with a simple click a browser displaying a zoom of the area, if you like to send your image as a postcard to another &digikam; user (who is then able to locate your shot), or if you simply need the documentation aspect of it - having position data stored in a photo is great. - </para> - <para> - Now, how do we get GPS data into the images? <ulink url="http://www.exiv2.org/tags.html";>exiv2</ulink> supports many kinds of the GPS data fields, even bearing, satellite and map references. So the question is really how to get the data into those fields? There are at least three ways to do this: directly with the appropriate hardware, per post-treatment of GPS and image files using the Geolocation Kipi-plugin (<ulink url="help:/kipi-plugins/geolocalization.html">Manual</ulink>) and per 'manual' insertion of known locations. - </para> - <itemizedlist> - - <listitem><para>Direct GPS data insertion into the image files</para> - <para> - To our knowledge there is at the time of writing no camera that integrates a GPS unit. But there are a few that combine with GPS receivers, either as a plug-in card or by data transmission through cable or Bluetooth. - </para> - <para><ulink url="http://www.engadget.com.nyud.net:8090/2004/09/17/diy-black-box-tagging-photos-with-gps-coordinates/";>Selfmade Howto</ulink> - </para> - </listitem> - - <listitem><para>Post-treatment of GPS data and image files</para> - <para> - Using the Geolocation Kipi-plugin (<ulink url="help:/kipi-plugins/geolocalization.html">Manual</ulink> if Kipi-plugins are already installed). - </para> - <para> - This approach is dead easy: while taking your pictures just keep a GPS device running and carry it around with the camera. Once you are done, download the pictures and the GPS tracks, and run the above plugin. It will correlate the data in the time domain; so it is important that the camera be accurate in its clock setting (the GPS device is always accurate through the satellites). The positional accuracy interpolated from the track points can be as good as 20 meters. Of course, this approach only works if your camera can record EXIF data. - </para> - <para>The GPS track download from a device can be managed with the <ulink url="http://gpsman.sourceforge.net/";>gpsman</ulink> or <ulink url="http://www.gpsbabel.org";>gpsbabel</ulink>. It is important that the downloaded tracks are being stored in gpx format, which is the only one compatible with the Geolocation plugin. - </para> - <para> - Several programs exist for &Windows; and MacOS that are able to extract and correlate data from images and GPS data tracks. The following site provides the same functionality for &Linux;: - <ulink url="http://freefoote.dview.net/linux_gpscorr.html";>gpsCorr</ulink> or - <ulink url="http://www.carto.net/projects/photoTools/gpsPhoto/";>gpsPhoto</ulink> - </para> - </listitem> - - <listitem> - <para>'Manual' insertion of known locations</para> - <para>If you happen to know the latitude/longitude or other data you can use the this script which is a GPS wrapper for Phil Harvey's <ulink url="http://www.sno.phy.queensu.ca/~phil/exiftool";>ExifTool</ulink> that uses the signed floating number coordinate notation as produced by maps.google. - </para> - </listitem> - - </itemizedlist> - - <para> - GPS devices: - <ulink url="http://www.letsgodigital.org/en/9323/sony_gps_photography/";>GPS tracker from Sony </ulink> and - <ulink url="http://www.emtac.com/products/bluetooth/index.html#btgps";>EMTAC bluetooth GPS </ulink> - </para> - </sect2> - </sect1> - - <sect1 id="using-setup"> <title>&digikam; Configuration</title> - - <sect2 id="setupdialog"> <title>The Setup Section</title> - - <anchor id="setupdialog.anchor"/> - - <para> - &digikam; tries to give you as much control over how it works as possible. There are many options that change the behavior of &digikam;. To access these settings select - <menuchoice><guimenu>Settings</guimenu> - <guimenuitem>Configure &digikam;</guimenuitem></menuchoice> from the menubar. The configuration dialog is separated into 15 pages. You can change between these pages by clicking on the icons on the left-hand side of the dialog. - </para> - - <itemizedlist> - <listitem><para><link linkend="setup-album">Album Settings</link></para></listitem> - <listitem><para><link linkend="setup-collection">Collection Settings</link></para></listitem> - <listitem><para><link linkend="author-identity">Default Author Identity</link></para></listitem> - <listitem><para><link linkend="setup-embeddedinfo">Metadata (embedded information)</link></para></listitem> - <listitem><para><link linkend="setup-tooltip">Tooltip Settings</link></para></listitem> - <listitem><para><link linkend="setup-mimetype">Mime Type Settings</link></para></listitem> - <listitem><para><link linkend="setup-lighttable">Light Table Settings</link></para></listitem> - <listitem><para><link linkend="setup-editor">Image Editor Settings</link></para></listitem> - <listitem><para><link linkend="setup-saveimages">Save Image Options</link></para></listitem> - <listitem><para><link linkend="setup-raw-decoder">RAW Decoder Settings</link></para></listitem> - <listitem><para><link linkend="setup-iccprofiles">ICC Profiles setup</link></para></listitem> - <listitem><para><link linkend="setup-kipiplugins">Kipi Plugins Settings</link></para></listitem> - <listitem><para><link linkend="setup-slideshow">Slide show settings</link></para></listitem> - <listitem><para><link linkend="setup-camera">Camera Interface Settings</link></para></listitem> - <listitem><para><link linkend="setup-miscellaneous">Miscellaneous Settings</link></para></listitem> - </itemizedlist> - - <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> - </para> - - <para> - The <guilabel>Album Library Path</guilabel> is the location on your hard disk where &digikam; will store all of the Albums. If you change this location without manually moving all of the Albums on the hard disk, &digikam; assumes that there are no existing Albums and will generate a new database at the new location. Your old Albums will not be altered but you will need to change the Album Library Path back to the old location to access them. If you are not sure of what you are doing it is best not to change this location. - </para> - - <para> - The <guilabel>Thumbnails</guilabel> options are described in the <link linkend="using-imageview">Images</link> section. - </para> - - <para> - The <guilabel>Click action</guilabel> can be set to <guilabel>Show embedded preview</guilabel> or <guilabel>Start image editor</guilabel>. You herewith define the default behavior of &digikam; when you click on an image item in the main view. - </para> - - </sect3> - - <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> - </para> - - </sect3> - - <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> - </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> + &doc-using-camera; - <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> - - <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> - </para> - - <para> - These settings allow you to control how &digikam; will deal with this embedded information. - </para> - - <para> - <guilabel>Show images/thumbnails rotated according to orientation tag</guilabel> : this will use any orientation information that your camera has included in the EXIF information to automatically rotate your photographs so that they are the correct way up when displayed. It will not actually rotate the image file, only the display of the image on the screen. If you want to permanently rotate the image on file, you can right-click on the thumbnail and select <guilabel>Auto-rotate/flip according to EXIF orientation</guilabel>. The image will then be rotated on disk and the tag will be reset to "normal". If your camera routinely gets this orientation information wrong you might like to switch this feature off. - </para> - - <para> - <guilabel>Set orientation tag to normal after rotate/flip</guilabel> : the Auto Rotate option automatically corrects the orientation of images taken with digital cameras that have an orientation sensor. The camera adds an orientation tag to the image's EXIF meta-data. &digikam; can read this tag to adjust the image accordingly. If you manually rotate an image, this meta-data will be incorrect. This option will set the orientation tag to "Normal" after an adjustment, assuming that you rotated it to the correct orientation. Switch this off if you don't want &digikam; to make changes to the orientation tag, when you rotate or flip the image. - </para> - - <para> - The <guilabel>IPTC Actions</guilabel> will save the data into the respective IPTC fields, which ensures a permanent metadata storage in the image and not only in &digikam;'s database. Thus, metadata is persistent across applications, and may be exported or imported into &digikam; without loss. - </para> - - <para> - <guilabel>Save image captions as embedded text</guilabel> : this will synchronize the captions that you add to your photographs with those in embedded in the image. This is useful because the captions embedded in the image can be read by other image viewers. Care should be taken if you have images that already have captions embedded in them because these captions will be overwritten by the captions made within &digikam;. - </para> - - </sect3> - - <sect3 id="setup-tooltip"> <title>Tooltip Settings</title> - - <para> - This setup page covers all options of information appearing when the mouse hovers over a file in the main view. According the checked options they will be shown or not. - </para> - - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setuptooltip.png" format="PNG" /> </imageobject></inlinemediaobject> - </para> - - </sect3> - - <sect3 id="setup-mimetype"> <title>Mime Type Settings</title> - - <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> - - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupmimetypes.png" format="PNG" /> </imageobject></inlinemediaobject> - </para> - - </sect3> - - <sect3 id="setup-lighttable"> <title>Light Table Settings</title> - - <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> - </para> - - </sect3> - - <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> - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupimageeditor.png" format="PNG" /> </imageobject></inlinemediaobject> - </para> - - </sect3> - - <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> - </para> - - <para> - With <guilabel>PNG compression</guilabel> option, you can reduce PNG image files size. This operation does not reduce image quality because PNG uses a lossless algorithm. The only effect is that image data needs more time to compress/decompress. If you have a fast computer you can change this value to use a high compression factor (1: low compression / 9: high compression). - </para> - - <para> - With <guilabel>Compress TIFF</guilabel> option, you can toggle to use <emphasis>Deflate</emphasis> compression algorithm with TIFF image files. This will reduce TIFF image files sizes. It has no image quality effect because <emphasis>Deflate</emphasis> is a lossless algorithm. - </para> - - <para> - With the <guilabel>LossLess JPEG 2000 files</guilabel> option allows for lossless storage, or, if the lossy options is selected, even then the quality for comparative files size is much better than normal JPEG. At the time of writing, metadata is not yet supported, but it is in the 'pipeline'. - </para> - - </sect3> - - <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>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>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> - </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> - <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> - - <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> - <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> - 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> - - <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> - </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> - 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> - 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> - </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> - <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> - - <para> - Kipi is an Image Plugin Interface. It is an interface that is supported by a number of image viewer/editor applications. By providing this interface, &digikam; can take advantage of many plugins that are written to work with any application that implements the Kipi interface. - </para> - - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupkipiplugins.png" format="PNG" /> </imageobject></inlinemediaobject> - </para> - - <para> - If your operating system has the Kipi plugins package installed, you will see a list of available plugins. Select those that you want to use and they will be loaded into &digikam;. The plugins will appear as new menu entries in the main menu bar and in the context menu for thumbnails. - </para> - - <para> - Keyboard shortcuts to actions that plugins perform can be set up in the - <menuchoice><guimenu>Setting</guimenu> - <guimenuitem>Configure Shortcuts</guimenuitem></menuchoice> menu. - </para> - - <para> - For more information about Kipi plugins, you can consult the <ulink url="help:/kipi-plugins/index.html">Kipi-plugins manual</ulink>. - </para> - - </sect3> - - <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> - </para> - </sect3> - - <sect3 id="setup-camera"> <title>Camera Interface Settings</title> - - <para> - The camera settings shows on the left of the list of the currently supported cameras. On the right at the top there is an auto-detect button, which tries to identify the camera connected to your computer (make sure that the camera is connected properly to the computer and turned on in the image display mode). Below this are the port settings; the currently supported are Serial, USB, and USB/FireWire Mass Storage. - </para> - - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupcamera.png" format="PNG" /> </imageobject></inlinemediaobject> - </para> - - <anchor id="cameraselection.anchor"/> - - <para> - Clicking on a camera in the list on the left will display the supported ports which you can then select. If there is only one supported port it will be automatically selected. At the bottom on the right there is a box for setting the exact path in case of a serial port. Please note that USB interface does not need any paths to be set. If you cannot find your camera on the list, you can try to use a generic Mass Storage device selecting <guilabel>Mounted Camera</guilabel> item in the list. - </para> - - <para> - At the very bottom is where you set the path for a USB or FireWire (IEEE-1394 or i-link) Mass Storage camera. This box becomes active once you select USB or FireWire Mass Storage camera in the camera list. You need to enter here the path where you mount the camera, usually "/mnt/camera" or "/mnt/removable". - </para> - - <para> - <inlinemediaobject><imageobject><imagedata fileref="&path;setupaddcamera.png" format="PNG" /> </imageobject></inlinemediaobject> - </para> - - <para> - To be able to use your digital camera with &digikam;, connect the camera to your computer, switch the camera to the image display mode and turn it on. - </para> - - <para> - Try and see if &digikam; can auto-detect the camera; if not, you can set the camera model and port manually. Once you have the camera setup, go to the "Cameras" menu in the main interface and you will see the camera listed in the menu. - </para> - - <note><para> - You can choose any title you like for the camera in the setup and this title will be used in the main window <guilabel>Cameras</guilabel> menu. If you have more than one camera, you can add them through this setup interface. - - </para></note> - - </sect3> - - <sect3 id="setup-miscellaneous"> <title>Miscellaneous Settings</title> - - <para> - With the <guilabel>Confirm when moving items to trash</guilabel> setting you can set the verbosity of &digikam; when you delete a photograph or an Album. See <link linkend="using-deleteimage">Deleting a Photograph</link> and <link linkend="using-deletealbum">Deleting an Album</link> sections for more details. - </para> - - <para> - The editorial changes done through the right sidebar can be quietly applied by &digikam; when setting the <guilabel>Apply changes in the right sidebar without confirmation</guilabel> option. Otherwise the changes must be applied by pressing the <guilabel>Apply changes</guilabel> button. - </para> - - <para> - You can also switch off the display of the splash screen when &digikam; loads. This may speed up the start time of &digikam; slightly. - </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> - </para> - - </sect3> - - </sect2> - - <sect2 id="setuptheme"> <title>The Theme Setup</title> - - <para> - Color schemes are supplied like themes to personalize &digikam; main interface for you pleasure. To access these settings select - <menuchoice><guimenu>Settings</guimenu> - <guimenuitem>Themes</guimenuitem></menuchoice> from the menubar and select your preferred theme to use. - </para> - </sect2> - - </sect1> + &doc-using-setup; </chapter> diff --git a/digikam/using-camera.docbook b/digikam/using-camera.docbook new file mode 100644 index 0000000..f0490c0 --- /dev/null +++ b/digikam/using-camera.docbook @@ -0,0 +1,288 @@ +<sect1 id="using-camera"> <title>Using a Digital Camera With &digikam;</title> +<anchor id="camerainterface.anchor"/> + + <sect2> <title>Introduction to Camera Interface</title> + + <para> + The Camera Tool allows you to download your photographs directly from your camera into a &digikam; Album. You can access the Camera Tool by clicking on the Camera menu and selecting from the list of configured cameras. See the <link linkend="setup-camera">Setup Camera Section</link> of the manual for instructions on how to setup &digikam; to work with your camera. If you want to have more information about how &digikam; supports digital cameras, please a take a look at <link linkend="intro-camerasupport">this section</link>. + </para> + + <para> + The Camera Interface is not the only way to get your photographs into &digikam;. See the <link linkend="using-addphototoalbum">Adding a photograph to an Album</link> section for a description of how to add photographs that are already on your hard disk. But Camera Interface provides a lots of advanced settings to import images into your albums database. + </para> + + <para> + To be able to use your digital camera with &digikam;, connect the camera to your computer, switch the camera to the image display mode and turn it on. See you camera's user manual if you need more information. + </para> + + <para> + When you start the Camera Interface, it will try to connect to the Camera. For some cameras this connection phase can take a little while. When connected, a <guilabel>Ready</guilabel> indicator will appear on the bottom and thumbnails of any photographs on the camera will be displayed. Some cameras cannot provide thumbnails of the photographs. If this is the case, you will only see the filenames and a mime-type icon for each item stored by your camera (photograph, movies, sounds, etc). + </para> + + <example> <title>The Camera Client Window</title> + <screenshot><screeninfo>The Camera Client Window</screeninfo> <mediaobject><imageobject><imagedata fileref="&path;cameraclient.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + </sect2> + + <sect2> + <title>Getting information about photographs from the Camera</title> + + <para> + Before downloading photographs to your computer, you may wish to see camera item information. Using the + <menuchoice><guimenuitem>Properties</guimenuitem></menuchoice> and <menuchoice><guimenuitem>Metadata</guimenuitem></menuchoice> side bar tabs from Camera Interface will launch camera item properties and metadata information. + </para> + + <example> <title>The Camera Item Properties Sidebar Tab</title> + <screenshot><screeninfo>The camera item properties sidebar Tab</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientitemproperties.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + <para> + The Properties tab displays file information recorded by the camera and a resume of photographer information to describe how the image has been taken. A flag indicates if the image has not yet been downloaded to the computer. Note, all this information may be unavailable with some digital cameras. + </para> + + <para> + The Metadata tab displays an internal picture's metadata like EXIF, Makernotes, GPS, &etc; This information is the same as <link linkend="using-sidebarmetadata">sidebar Meta-Data</link> from the &digikam; main interface or image editor. Note, all these metadata can be unavailable with some digital cameras. + </para> + + </sect2> + + <sect2> + <title>Downloading photographs to your computer</title> + + <para> + The simplest way to download photographs from your camera to your computer is to click the <guilabel>Download</guilabel> button and then click <guilabel>Download All</guilabel>. This will download all of the photographs on the camera to a single Album in &digikam;. The download process will not remove the photographs from the camera. It is always advisable to check that the photographs have downloaded safely into the Album you were expecting before deleting them from the camera. + </para> + + <para> + If you do not want to download all of the photographs you can select just those that you need using the standard selection methods. Once you have the photographs selected, click <guilabel>Download</guilabel> and then <guilabel>Download Selected</guilabel>. The <guilabel>Download Selected</guilabel> button will be grayed out until you have selected some photographs. + </para> + + <note><para> + If supported by your camera an option <guilabel>Download new</guilabel> is available. Those are images not yet downloaded by &digikam;. In that case the new images are already marked with a star in the thumbnail window. Obviously if you choose this handy option, it will download the new images only. + </para></note> + + </sect2> + + <sect2> + <title>Selecting a Target Album</title> + <anchor id="targetalbumdialog.anchor"/> + + <para> + Using <guilabel>Download All</guilabel> or <guilabel>Download Selected</guilabel> buttons will bring up a dialog, that allows you to select a target Album into which the photographs will be downloaded. The list of existing Albums is displayed, ordered by the Folder method (see the <link linkend="using-myalbumsview">Albums View</link> for details of Album ordering). You can select the target Album from this list and then click OK. + </para> + + <example> <title>The Target Album Selection Dialog</title> + <screenshot><screeninfo>The Target Album Selection Dialog</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameratargetalbumdialog.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + <para> + If you want to create a new Album, into which you could download the photographs, click the <guilabel>New Album</guilabel> button. The new Album will be created as a sub-folder of the Album that is currently selected in the existing Album list. This means that, if you do not want your new Album to be a sub-folder of an existing folder, you must first select the "My Albums" entry from the very top of the existing Albums list before creating a new Album. + </para> + + <para> + When you have selected the target Album, click OK and &digikam; will download the photographs from the camera to that album. + </para> + + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;cameraclientdownload.png" format="PNG" /> </imageobject><textobject><phrase>The Downloading in Progress</phrase></textobject></inlinemediaobject> + </para> + + </sect2> + + <sect2> + <title>Deleting photographs from the camera</title> + + <para> + Once you are happy with the downloaded photographs that you wanted, you are ready to delete photographs from the Camera. You can delete all of the photographs at once by clicking the + <menuchoice> + <guimenu>Delete</guimenu> + <guimenuitem>Delete All</guimenuitem> + </menuchoice> + button. If you just want to delete a selection of the photographs, you have to select those that you want to delete and click + <menuchoice><guimenu>Delete</guimenu> + <guimenuitem>Delete Selected</guimenuitem></menuchoice> + </para> + + <caution><para> + Please note that there is no way to restore a photo that you have deleted from the camera. The photographs are not moved to the internal Trash Can, they are removed completely. It is best to double check that you have successfully downloaded a photograph into a &digikam; Album before you delete it from the camera. Anyway, if you plan to empty the camera card, you better do that from the camera menu because it is much quicker. + </para></caution> + + </sect2> + + <sect2 id="using-cameraclientrenaming"> + <title>Automatic Renaming</title> + + <para> + Cameras often do not use very meaningful filenames for photographs. The filenames are usually reused once the photographs have been deleted from the camera. This can lead to filename clashes if you download photographs from many shootings into the same Album. It can also be useful to include the date and time that an image was taken into the filename. + </para> + + <example> <title>Files Renaming Options</title> + <screenshot><screeninfo>Files Renaming Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting1.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + <para> + &digikam; can automatically rename your photographs using the date and time information included by the camera in the photograph. To use this feature, click the <guilabel>Settings</guilabel> button on the Camera Interface. The Camera Interface window will expand to reveal some extra features. Select <guilabel>Customize</guilabel> and then enter any filename prefix you would like. As an option you can add many information independently or by combination including : date, time, original file name, file extension, directory, owner, group, camera name, a sequence number or any other metadata from the photograph. + </para> + <para> + </para> + <para> + In the next box you find the options for rotating/flipping the image and for date based subalbums. If you check the latter option, folder per day will be automatically generated. + </para> + <para> + The 'On the fly operations' open three more options that act on the photos before storing them on disk. The first two relate to the authors data in <link linkend="author-identity">Default Author Identity</link> settings. If checked, the respective items will be copied into the EXIF tags and IPTC fields. The last option allows a date & time for all downloaded photographs to be set. + </para> + + <tip> + <para> + <itemizedlist> + + <listitem><para>The sequence number may be needed if you have a camera with a very fast multi-shoot mode where it is possible to get two photographs with exactly the same data and time. + </para></listitem> + + <listitem><para>If you want another date format then the default date format, click on <guilabel>Date & Time...</guilabel>, choose <guilabel>Custom</guilabel> in <guilabel>Format</guilabel> drop-down list and fill in for example "dd.MM.yyyy hh:mm:ss". For more information, read <ulink url="http://doc.qt.digia.com/qt/qdatetime.html#toString";>QdateTime</ulink> class reference.</para></listitem> + + <listitem><para>When you select <guilabel>Camera filenames</guilabel>, you have the option to change the filenames to lowercase when downloading. Or use uppercase if you prefer.</para></listitem> + + </itemizedlist> + </para> + </tip> + + <para> + The new filename that &digikam; will use for the photographs when they are downloaded is shown underneath the name provided by the camera in the thumbnail view. The renaming settings will be remembered the next time you use the camera interface. + </para> + + </sect2> + + <sect2> + <title>Camera Information Based Operations</title> + + <sect3> + <title>Automatic Rotation</title> + + <para> + &digikam; can use any information about the orientation of the camera at the moment the photograph was taken for automatic rotation of the photograph when it is downloaded. Not all cameras include this information. See the <link linkend="using-sidebarmetadata">sidebar Meta-Data</link> section for more detail about information that your camera may have embedded in your photographs. + </para> + + <example> <title>On the fly Operations Options</title> + <screenshot><screeninfo>On the fly Operations Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting2.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + <para> + This automatic rotation is switched on by default, and if your camera does not include the information, &digikam; will leave the photograph at its original orientation. If you would like to switch the automatic rotation off, click the <guilabel>Advanced</guilabel> button and deselect the <guilabel>Auto Orient</guilabel> option at the bottom of the window. + </para> + + </sect3> + + <sect3> + <title>Automatic Destination Albums Creation</title> + + <para> + If your camera provides information about the date of the photograph's taking, &digikam; can use this to automatically create subalbums in the destination Album when it is downloaded. Subalbums names will be based on image dates. All images which have the same date will be downloaded into the same subalbum. Not all cameras include this information. + See the <link linkend="using-sidebarmetadata"> + sidebar Meta-Data</link> section for more detail about + information your camera may have embedded in your photographs. + </para> + + <example> <title>Albums Auto-creation Options</title> + <screenshot><screeninfo>Albums Auto-creation Options</screeninfo><mediaobject><imageobject><imagedata fileref="&path;cameraclientsetting3.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + <para> + This option is switched off by default and in this case &digikam; will download the photographs + in the root destination Albums. If you would like to switch on this option click the + <guilabel>Advanced</guilabel> button and select the <guilabel>Download photo in automatically</guilabel> + option at the bottom of the window. + </para> + + </sect3> + + </sect2> + + <sect2> + <title>Uploading Photographs to your camera</title> + + <para> + The simplest way to upload photographs from your computer to your camera is to click the <guilabel>Download</guilabel> button and then click <guilabel>Upload</guilabel>. A standard file selection dialog will appear to select the files from your computer to copying on your camera. You can select more than one file using the standard selection methods. + </para> + + <para> + When images selection is done, &digikam; will ask you where you want to upload the files on your camera. A camera folder selection dialog will appear. Just select one folder and press OK to start uploading. No images will be removed from your computer. + </para> + + <example> <title>The Camera Folder Selection Dialog</title> + <screenshot><screeninfo>The Camera Folder Selection Dialog</screeninfo><mediaobject><imageobject><imagedata fileref="&path;camerafolderselectiondialog.png" format="PNG" /> </imageobject></mediaobject></screenshot> + </example> + + <note><para> + Uploading feature is not supported by all camera drivers. + </para></note> + + </sect2> + + <sect2 id="using-gps"> + <title>How to use a GPS device with &digikam;</title> + <note><para> + <inlinemediaobject> + <imageobject><imagedata fileref="&path;handheld_gps.png" format="PNG"/></imageobject> + </inlinemediaobject>GPS (global positioning system) is used as a generic term throughout this document. It just means a location in latitude and longitude global coordinates that can be displayed on a map. The actual technical implementation that provides the data can be the American GPS, the Russian GLONAS, the European GALILEO or any other system. + </para></note> + + <para> + Not only for professional photographers can it be interesting to link an image to a precise geographical location. Not everybody uses an airplane to overfly and scan a certain area with automatic GPS data recording. Environmental planners, military, police, construction bureaus, real estate agencies, all will have an immediate application. + </para> + <para> + But if, after some time, one has forgotten where the image was taken, if one loves the nice feature to open with a simple click a browser displaying a zoom of the area, if you like to send your image as a postcard to another &digikam; user (who is then able to locate your shot), or if you simply need the documentation aspect of it - having position data stored in a photo is great. + </para> + <para> + Now, how do we get GPS data into the images? <ulink url="http://www.exiv2.org/tags.html";>exiv2</ulink> supports many kinds of the GPS data fields, even bearing, satellite and map references. So the question is really how to get the data into those fields? There are at least three ways to do this: directly with the appropriate hardware, per post-treatment of GPS and image files using the Geolocation Kipi-plugin (<ulink url="help:/kipi-plugins/geolocalization.html">Manual</ulink>) and per 'manual' insertion of known locations. + </para> + <itemizedlist> + + <listitem><para>Direct GPS data insertion into the image files</para> + <para> + To our knowledge there is at the time of writing no camera that integrates a GPS unit. But there are a few that combine with GPS receivers, either as a plug-in card or by data transmission through cable or Bluetooth. + </para> + <para><ulink url="http://www.engadget.com.nyud.net:8090/2004/09/17/diy-black-box-tagging-photos-with-gps-coordinates/";>Selfmade Howto</ulink> + </para> + </listitem> + + <listitem><para>Post-treatment of GPS data and image files</para> + <para> + Using the Geolocation Kipi-plugin (<ulink url="help:/kipi-plugins/geolocalization.html">Manual</ulink> if Kipi-plugins are already installed). + </para> + <para> + This approach is dead easy: while taking your pictures just keep a GPS device running and carry it around with the camera. Once you are done, download the pictures and the GPS tracks, and run the above plugin. It will correlate the data in the time domain; so it is important that the camera be accurate in its clock setting (the GPS device is always accurate through the satellites). The positional accuracy interpolated from the track points can be as good as 20 meters. Of course, this approach only works if your camera can record EXIF data. + </para> + <para>The GPS track download from a device can be managed with the <ulink url="http://gpsman.sourceforge.net/";>gpsman</ulink> or <ulink url="http://www.gpsbabel.org";>gpsbabel</ulink>. It is important that the downloaded tracks are being stored in gpx format, which is the only one compatible with the Geolocation plugin. + </para> + <para> + Several programs exist for &Windows; and MacOS that are able to extract and correlate data from images and GPS data tracks. The following site provides the same functionality for &Linux;: + <ulink url="http://freefoote.dview.net/linux_gpscorr.html";>gpsCorr</ulink> or + <ulink url="http://www.carto.net/projects/photoTools/gpsPhoto/";>gpsPhoto</ulink> + </para> + </listitem> + + <listitem> + <para>'Manual' insertion of known locations</para> + <para>If you happen to know the latitude/longitude or other data you can use the this script which is a GPS wrapper for Phil Harvey's <ulink url="http://www.sno.phy.queensu.ca/~phil/exiftool";>ExifTool</ulink> that uses the signed floating number coordinate notation as produced by maps.google. + </para> + </listitem> + + </itemizedlist> + + <para> + GPS devices: + <ulink url="http://www.letsgodigital.org/en/9323/sony_gps_photography/";>GPS tracker from Sony </ulink> and + <ulink url="http://www.emtac.com/products/bluetooth/index.html#btgps";>EMTAC bluetooth GPS </ulink> + </para> + </sect2> +</sect1> + +<!-- +Local Variables: +mode: sgml +sgml-omittag: nil +sgml-shorttag: t +End: +--> diff --git a/digikam/using-setup.docbook b/digikam/using-setup.docbook new file mode 100644 index 0000000..7cf6689 --- /dev/null +++ b/digikam/using-setup.docbook @@ -0,0 +1,448 @@ +<sect1 id="using-setup"> <title>&digikam; Configuration</title> + + <sect2 id="setupdialog"> <title>The Setup Section</title> + + <anchor id="setupdialog.anchor"/> + + <para> + &digikam; tries to give you as much control over how it works as possible. There are many options that change the behavior of &digikam;. To access these settings select + <menuchoice><guimenu>Settings</guimenu> + <guimenuitem>Configure &digikam;</guimenuitem></menuchoice> from the menubar. The configuration dialog is separated into 15 pages. You can change between these pages by clicking on the icons on the left-hand side of the dialog. + </para> + + <itemizedlist> + <listitem><para><link linkend="setup-album">Album Settings</link></para></listitem> + <listitem><para><link linkend="setup-collection">Collection Settings</link></para></listitem> + <listitem><para><link linkend="author-identity">Default Author Identity</link></para></listitem> + <listitem><para><link linkend="setup-embeddedinfo">Metadata (embedded information)</link></para></listitem> + <listitem><para><link linkend="setup-tooltip">Tooltip Settings</link></para></listitem> + <listitem><para><link linkend="setup-mimetype">Mime Type Settings</link></para></listitem> + <listitem><para><link linkend="setup-lighttable">Light Table Settings</link></para></listitem> + <listitem><para><link linkend="setup-editor">Image Editor Settings</link></para></listitem> + <listitem><para><link linkend="setup-saveimages">Save Image Options</link></para></listitem> + <listitem><para><link linkend="setup-raw-decoder">RAW Decoder Settings</link></para></listitem> + <listitem><para><link linkend="setup-iccprofiles">ICC Profiles setup</link></para></listitem> + <listitem><para><link linkend="setup-kipiplugins">Kipi Plugins Settings</link></para></listitem> + <listitem><para><link linkend="setup-slideshow">Slide show settings</link></para></listitem> + <listitem><para><link linkend="setup-camera">Camera Interface Settings</link></para></listitem> + <listitem><para><link linkend="setup-miscellaneous">Miscellaneous Settings</link></para></listitem> + </itemizedlist> + + <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> + </para> + + <para> + The <guilabel>Album Library Path</guilabel> is the location on your hard disk where &digikam; will store all of the Albums. If you change this location without manually moving all of the Albums on the hard disk, &digikam; assumes that there are no existing Albums and will generate a new database at the new location. Your old Albums will not be altered but you will need to change the Album Library Path back to the old location to access them. If you are not sure of what you are doing it is best not to change this location. + </para> + + <para> + The <guilabel>Thumbnails</guilabel> options are described in the <link linkend="using-imageview">Images</link> section. + </para> + + <para> + The <guilabel>Click action</guilabel> can be set to <guilabel>Show embedded preview</guilabel> or <guilabel>Start image editor</guilabel>. You herewith define the default behavior of &digikam; when you click on an image item in the main view. + </para> + + </sect3> + + <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> + </para> + + </sect3> + + <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> + </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> + + </sect3> + + <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> + </para> + + <para> + These settings allow you to control how &digikam; will deal with this embedded information. + </para> + + <para> + <guilabel>Show images/thumbnails rotated according to orientation tag</guilabel> : this will use any orientation information that your camera has included in the EXIF information to automatically rotate your photographs so that they are the correct way up when displayed. It will not actually rotate the image file, only the display of the image on the screen. If you want to permanently rotate the image on file, you can right-click on the thumbnail and select <guilabel>Auto-rotate/flip according to EXIF orientation</guilabel>. The image will then be rotated on disk and the tag will be reset to "normal". If your camera routinely gets this orientation information wrong you might like to switch this feature off. + </para> + + <para> + <guilabel>Set orientation tag to normal after rotate/flip</guilabel> : the Auto Rotate option automatically corrects the orientation of images taken with digital cameras that have an orientation sensor. The camera adds an orientation tag to the image's EXIF meta-data. &digikam; can read this tag to adjust the image accordingly. If you manually rotate an image, this meta-data will be incorrect. This option will set the orientation tag to "Normal" after an adjustment, assuming that you rotated it to the correct orientation. Switch this off if you don't want &digikam; to make changes to the orientation tag, when you rotate or flip the image. + </para> + + <para> + The <guilabel>IPTC Actions</guilabel> will save the data into the respective IPTC fields, which ensures a permanent metadata storage in the image and not only in &digikam;'s database. Thus, metadata is persistent across applications, and may be exported or imported into &digikam; without loss. + </para> + + <para> + <guilabel>Save image captions as embedded text</guilabel> : this will synchronize the captions that you add to your photographs with those in embedded in the image. This is useful because the captions embedded in the image can be read by other image viewers. Care should be taken if you have images that already have captions embedded in them because these captions will be overwritten by the captions made within &digikam;. + </para> + + </sect3> + + <sect3 id="setup-tooltip"> <title>Tooltip Settings</title> + + <para> + This setup page covers all options of information appearing when the mouse hovers over a file in the main view. According the checked options they will be shown or not. + </para> + + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;setuptooltip.png" format="PNG" /> </imageobject></inlinemediaobject> + </para> + + </sect3> + + <sect3 id="setup-mimetype"> <title>Mime Type Settings</title> + + <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> + + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;setupmimetypes.png" format="PNG" /> </imageobject></inlinemediaobject> + </para> + + </sect3> + + <sect3 id="setup-lighttable"> <title>Light Table Settings</title> + + <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> + </para> + + </sect3> + + <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> + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;setupimageeditor.png" format="PNG" /> </imageobject></inlinemediaobject> + </para> + + </sect3> + + <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> + </para> + + <para> + With <guilabel>PNG compression</guilabel> option, you can reduce PNG image files size. This operation does not reduce image quality because PNG uses a lossless algorithm. The only effect is that image data needs more time to compress/decompress. If you have a fast computer you can change this value to use a high compression factor (1: low compression / 9: high compression). + </para> + + <para> + With <guilabel>Compress TIFF</guilabel> option, you can toggle to use <emphasis>Deflate</emphasis> compression algorithm with TIFF image files. This will reduce TIFF image files sizes. It has no image quality effect because <emphasis>Deflate</emphasis> is a lossless algorithm. + </para> + + <para> + With the <guilabel>LossLess JPEG 2000 files</guilabel> option allows for lossless storage, or, if the lossy options is selected, even then the quality for comparative files size is much better than normal JPEG. At the time of writing, metadata is not yet supported, but it is in the 'pipeline'. + </para> + + </sect3> + + <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>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>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> + </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> + <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> + + <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> + <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> + 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> + + <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> + </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> + 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> + 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> + </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> + <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> + + <para> + Kipi is an Image Plugin Interface. It is an interface that is supported by a number of image viewer/editor applications. By providing this interface, &digikam; can take advantage of many plugins that are written to work with any application that implements the Kipi interface. + </para> + + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;setupkipiplugins.png" format="PNG" /> </imageobject></inlinemediaobject> + </para> + + <para> + If your operating system has the Kipi plugins package installed, you will see a list of available plugins. Select those that you want to use and they will be loaded into &digikam;. The plugins will appear as new menu entries in the main menu bar and in the context menu for thumbnails. + </para> + + <para> + Keyboard shortcuts to actions that plugins perform can be set up in the + <menuchoice><guimenu>Setting</guimenu> + <guimenuitem>Configure Shortcuts</guimenuitem></menuchoice> menu. + </para> + + <para> + For more information about Kipi plugins, you can consult the <ulink url="help:/kipi-plugins/index.html">Kipi-plugins manual</ulink>. + </para> + + </sect3> + + <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> + </para> + </sect3> + + <sect3 id="setup-camera"> <title>Camera Interface Settings</title> + + <para> + The camera settings shows on the left of the list of the currently supported cameras. On the right at the top there is an auto-detect button, which tries to identify the camera connected to your computer (make sure that the camera is connected properly to the computer and turned on in the image display mode). Below this are the port settings; the currently supported are Serial, USB, and USB/FireWire Mass Storage. + </para> + + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;setupcamera.png" format="PNG" /> </imageobject></inlinemediaobject> + </para> + + <anchor id="cameraselection.anchor"/> + + <para> + Clicking on a camera in the list on the left will display the supported ports which you can then select. If there is only one supported port it will be automatically selected. At the bottom on the right there is a box for setting the exact path in case of a serial port. Please note that USB interface does not need any paths to be set. If you cannot find your camera on the list, you can try to use a generic Mass Storage device selecting <guilabel>Mounted Camera</guilabel> item in the list. + </para> + + <para> + At the very bottom is where you set the path for a USB or FireWire (IEEE-1394 or i-link) Mass Storage camera. This box becomes active once you select USB or FireWire Mass Storage camera in the camera list. You need to enter here the path where you mount the camera, usually "/mnt/camera" or "/mnt/removable". + </para> + + <para> + <inlinemediaobject><imageobject><imagedata fileref="&path;setupaddcamera.png" format="PNG" /> </imageobject></inlinemediaobject> + </para> + + <para> + To be able to use your digital camera with &digikam;, connect the camera to your computer, switch the camera to the image display mode and turn it on. + </para> + + <para> + Try and see if &digikam; can auto-detect the camera; if not, you can set the camera model and port manually. Once you have the camera setup, go to the "Cameras" menu in the main interface and you will see the camera listed in the menu. + </para> + + <note><para> + You can choose any title you like for the camera in the setup and this title will be used in the main window <guilabel>Cameras</guilabel> menu. If you have more than one camera, you can add them through this setup interface. + + </para></note> + + </sect3> + + <sect3 id="setup-miscellaneous"> <title>Miscellaneous Settings</title> + + <para> + With the <guilabel>Confirm when moving items to trash</guilabel> setting you can set the verbosity of &digikam; when you delete a photograph or an Album. See <link linkend="using-deleteimage">Deleting a Photograph</link> and <link linkend="using-deletealbum">Deleting an Album</link> sections for more details. + </para> + + <para> + The editorial changes done through the right sidebar can be quietly applied by &digikam; when setting the <guilabel>Apply changes in the right sidebar without confirmation</guilabel> option. Otherwise the changes must be applied by pressing the <guilabel>Apply changes</guilabel> button. + </para> + + <para> + You can also switch off the display of the splash screen when &digikam; loads. This may speed up the start time of &digikam; slightly. + </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> + </para> + + </sect3> + + </sect2> + + <sect2 id="setuptheme"> <title>The Theme Setup</title> + + <para> + Color schemes are supplied like themes to personalize &digikam; main interface for you pleasure. To access these settings select + <menuchoice><guimenu>Settings</guimenu> + <guimenuitem>Themes</guimenuitem></menuchoice> from the menubar and select your preferred theme to use. + </para> + </sect2> + +</sect1> + +<!-- +Local Variables: +mode: sgml +sgml-omittag: nil +sgml-shorttag: t +End: +-->
