New to digikam? Needs some help? First, read carefully the digikam documentation. It’s actively maintained and you should find most of what you need there. digiKam is an immensely powerful photo management application, and mastering it requires time Facts about the digiKam Recipes book: Documentation. So I told digiKam where to find my monitor profile and I have a If you have very specific requirements for documenting of editing steps the Versions function .
|Country:||Central African Republic|
|Published (Last):||5 November 2011|
|PDF File Size:||6.57 Mb|
|ePub File Size:||3.90 Mb|
|Price:||Free* [*Free Regsitration Required]|
It makes use of gphoto2 to do camera operations. If your camera is not in the supported list, i would recommend doing some searching around. Please use documentaiton KDE bug tracking system for all bugreports and new feature wishlists. You can checkout the current bugreports and wishlists at these urls. The output looks like: Now we can match the results of these last two steps. If no errors show up, then you have performed all the steps correctly. Set the path to the above path, where the camera is mounted.
On all my albums, digiKam fails to generate thumbnails on some images. The only pattern I can spot is digiksm it docmentation on largish files bigger than 1MB. When the thumnails are generated, the documentxtion that fail appear at first and then are replaced by the broken picture icon. This feature is also supported by gPhoto, which is used as camera driver from digiKam. So it should and is possible to add an hotplug feature into digiKam.
This article tells you what are the requirements and what you have to do. When you documentattion a device into a hotplug bus like USB, the kernel detects it and looks if it has a suitable driver compiled inside. If not, the hotplug module is called and asked what to do. Doing so, the hotplug module will call a gphoto2 library to add a driver and afterthat a customizable script calls the application that should interact with the device.
This implementation uses two scripts.
The first one, usbcam, is called as root and his job is to determine the active user and call the 2nd script digikam-hotplug using the users id. Both scripts could be downloaded here.
The following requirements should be fullfilled to use digiKam with the hotplugging feature. As an additional remark, dofumentation should mention that the digikam-hotplug script documentatjon you could donwload requires KDE not only installed, it has to be the active Window Manager. This section gives the same information like documemtation 4. It simply describes howto setup the kernel hotplugging feature. The only difference are digiKam specific scripts. First you should check whether your kernel comes with the required hotplugging feature.
This program tells the hotplug module, which cameras are supported by the installed version from gPhoto. All you have normally to do is. There are two versions of the scripts.
Digikam documentation in french
Rename your version to usbcam and digikam-hotplug, and copy them to. For security reasons you should also check, that only root has write permissions on each file. After a few moments digiKam should start and connect automaticly to your camera.
If you have problems doing this, you should read the original gphoto documentation and check the syslog for notices from the two scripts.
Most digital cameras store images in jpeg format on the memory card. JPEG is a compressed format, whose compression causes loss of quality. Heavy compression may make the loss of quality visible to the eye.
Every time you open a JPEG image, edit it, save the file and close it, the image is compressed and quality is lost. Lost quality can not be regained.
To avoid this repeated loss of quality you should save your edited files in a lossless format. In digiKam it is advisable to use png.
You have now finished editing your photos and are content with the results. Should you keep the png-files or convert them to the far smaller JPEG files for storage?. If you are very concerned about storage space, you can do the latter. You could, however rather keep the lossless png files and only create JPEG copies in the moment you want to take your images to the print shop, send them by email or post them on the web. But nothing is lost, read on! It does normally not include an ICC profile.
This is fast, but a preview only, no raw data. RAW conversion requires a couple of steps in order to produce djgikam satisfying result, better adapted to your needs than JPEG out-of-the-camera documebtation.
Now, most profiles that come with the camera OEM software are not so suited for linear conversion. It will be more precise than the standard profile and it will include gamma correction – no dark images anymore in bit mode!
What can I do? Sqlite relies on file locking features provided by filesystems check this FAQ entry. But, network file systems often have troubles with locking and this can cause unexpected problems with sqlite. In the future, it will be possible to use another database backend to solve it. Comments in the theme are done by using common XML markers to include comments. The header is the place where you can add some comments, give credit to yourself… Look an existing Documentayion theme file for details.
TextRegularColor is used for regular unselected text and TextSelectedColor is used for selected text. These specifications are documenttion to render the banner at the top of the thumbnail view. There are two color specifications: BannerBorder indicates whether a border should be drawn around the banner, using BannerBorderColor.
These specifications are used for rendering the thumbnails. Regular… is used for unselected thumbnails and Selected… for selected thumbnails. The specifications are similar to that of the banner. These are used for rendering the items on the left treeview.
Color management of your monitor is possible with digiKam from version 0. The better and more fundamental way is to include the display color management in your X server using profiles. Then all other applications will profit as well. The best way to color-manage the display is to establish a custom profile and use that one, a procedure to be repeated every other year or so for aging reasons.
digikam-devel – digiKam API documentation
But if you go the easier way and use the profiles delivered from the manufacturer, it is paramount to do a normalization as described for example on the cambridgeincolour web site.
Also, video support is optional at application compilation time. If yes, you can install the stand alone QtAV media player on your system and check if playing video work as expected. If it do not work, probably a ffmpeg codec is missing on your system. Here you have a list of file types with the list of applications that can open them. The first application listed here will be the default one. Here you can adjust the font size but also choose another font.
Digikam uses Exiv2 shared library to display the file properties. The setting will be remembered by digiKam. If you use Ubuntu, the kcontrol or systemsettings menus will not be available to you, you have do do in the digiKam dialog box as described above. Nowadays, most linux distributions use utf8 by default for the character encoding. It includes the content of files, but also the file names. Digikam will warn you when you change your locale with a new encoding.
Eg, if you switched from iso latin1 iso to utf8, digiKam will send you this warning:. For that purpose, linux distributions propose various solutions and tools, but mainly based on convmv:.
For Mandrivait seems that the same convmv can documeentation applied. Mandriva provide also a script in their Mandriva Errata page. There is also a french page to explain how to convert the filename and the content of the files to utf Converting filenames to UTF-8 encoding. There are also some informations here: The most used tool to do that is convmv written in perl.
Eg try it first in a test directory and backup everything before! If you installed digiKam using your distribution package, language files should be included with it and you can run digiKam in any supported language. If you compiled yourself digiKam using the official tarballs, you can use digiKam in any supported language. The language files are installed with digikam.
If you compiled yourself digiKam from the latest trunk files, you will have to get the digkiam files you need. Check the svn download page for more details eg: First, check that you have development files installed in your linux system.
Usually, linux distributions have -dev packages when you want to compile something against a specific library. Look also at the download page for more informations tarball and svn sections. If you still have problems, check the support page.