digiKam 1.5.0 released…
Dear all digiKam fans and users!
digiKam team is proud to announce digiKam 1.5.0 release!
digiKam tarball can be downloaded from SourceForge at this url
See the list of new features below and bug-fixes coming with this release since 1.4.0
Enjoy digiKam.
NEW FEATURES:
General : Fix compilation under windows with TDM-GCC and MSVC compilers.
General : Including LensFun library source code as 3rd-party component, especially for windows target where this library is not available.
Image Editor : Improvement of algorithm to convert 8 bits image to 16 and limit histogram holes during conversion.
Batch Queue Manager : Add new tool to remove metadata from images.
Batch Queue Manager : Add new tool to apply Lens corrections using LensFun library.
BUGFIXES FROM KDE BUGZILLA:
001 ==> 247977 : Libpgf relevant : digiKam crash while scrolling the thumbnail view.
002 ==> 249402 : Download window presents file in the opposite order than expected.
003 ==> 249196 : Localization fails after upgrade !
004 ==> 245069 : File name not added for import files.
005 ==> 250003 : Kipi-plugin for xcf is needed.
006 ==> 250081 : Lens-autocorrection does not recognize the lens automaticly for Canon EOS 450D.
007 ==> 207710 : Crash while loading large file (Digikam::DImgScale::dimgScaleAARGB, Digikam::DImg::smoothScaleSection, Digikam::DImgInterface::paintOnDevice).
008 ==> 218256 : digiKam rc1 crashes while generating fingerprints.
009 ==> 237786 : whitebalance doesn’t work properly.
010 ==> 250265 : Black background of short summary display.
011 ==> 248889 : Notification name “save file complete” written in lowercase.
012 ==> 249082 : digiKam crashes on startup leaving message of unknown symbol.
013 ==> 249029 : Changing the parameters of a tool in the batch queue manager changes parameters of all instances of such tool.
014 ==> 230515 : Crash of digikam on closing program.
015 ==> 148721 : Remove serial numbers automatically.
016 ==> 229092 : digiKam Scan for New images closes at 90%.
017 ==> 248943 : Annoying and dangerous number input fields in editor.
018 ==> 216353 : Make it possible to apply lens correction in batch.
019 ==> 251920 : digiKam should match lenses on Exif.CanonCs.LensType, not ExifCanonCs.Lens.
020 ==> 251118 : Sorting order is not remembered.
021 ==> 170170 : High quality 8 to 16-bit conversion (histogram repair).
022 ==> 252295 : “Fit to Window” button while using any tool does not permit panning.
023 ==> 243179 : Wrong Taborder in Settings->Templates->Location|Contact.
024 ==> 210198 : Copyright and Right Usage information in Settings are not saved in template file.
025 ==> 228547 . Videos cannot return to thumbnail view.
026 ==> 251899 : Can’t rename files during import from camera.
027 ==> 169264 : Color Management: Rendering Intents are mixed up.
028 ==> 188335 : Slideshow shows movies as “cannot show picture “xyz.mov”.
029 ==> 252488 : digiKam incorrectly renders SD Card size.
030 ==> 252489 : digiKam incorrectly detects SD Card name.
031 ==> 252521 : README incorrectly claims kdegraphics-4.4 is sufficient.
032 ==> 249248 : Updating fingerprints metadata.
033 ==> 125042 : Batch Rename Image from Album do not select all album images.
034 ==> 237516 : Open in Terminal command doesn’t take KDE systemsettings into account.
035 ==> 225552 : digiKam can’t remember setting.
036 ==> 248087 : Preview not toggling from video mode to image mode.
037 ==> 209382 : Caption not being updated in image file.
038 ==> 253043 : digiKam requires both SQlite and MySql.
039 ==> 252130 : Crash on adding things to batch queue.
040 ==> 237961 : ICC Convert faulty in BQM.
041 ==> 228833 : Rotate image in batch processing doesn’t edit EXIF properly.
042 ==> 213896 : After editing color, etc, i saved the jpg and it just crashed.
043 ==> 232854 : Crashed while adding new tag.
044 ==> 241770 : digiKam crashes.
045 ==> 238045 : Random crashes of digiKam.
046 ==> 188263 : Crash after tinkering with star rating widget in thumbbar.
047 ==> 233549 : Database stuck at saving new image.
048 ==> 221191 : Menu not disabled when decoding raw.
049 ==> 237722 : Crash while applying Vivid color effect.
050 ==> 207893 : Crash after undoing change in Image Editor.
051 ==> 199801 : digiKam geolocation tool crash [exiv2].
052 ==> 223774 : digiKam crashed at liquid rescale preview generation.
053 ==> 233997 : Crash while importing from usb device after exivdates are read.
054 ==> 213576 : Thumbbar not updated after saveas in image editor.
Wrong version at SourceForge
The quick access "Download Now!" button at SourceForge points at the wrong version, it gives you 1.2.0 rater than the latest release.
fixed
Fixed on sourceforge.net
Windows Version
Hi, can you provide Windows binerys? The KDE-Windows Port is still dead...
That would be great!
Marc
windows...
The problem is : how to package digiKam including all shared libraries" ?
If i make a KDE4 installation backup from my computer, it create a tarball of 700 Mb around !
KDE-Windows installer is an optimized way. KDE-windows team just need to enable digiKam and kipi-plugins in package script lists.
digiKam
Digikam on windows
Gilles,
I think when Digikam 2.0 will be out the main features that will be missing for DigiKam are:
- an easy to install .dmg for MacOSX
- an easy to install .exe for windows
Look at vlc, firefox, ... they are very popular because they are easy to install under windows.
I think even if the download is very big, many people would be happy to have an option to install DigiKam easily. Is it possible to distribute digiKam with a private copy of qt/kdelibs/ and other dependencies ?
I guess digiKam relies also on some kde process which need to be lunched along with DigiKam ?
Julien
installers...
>Look at vlc, firefox, ... they are very popular because they are easy to install under windows.
I know... But building an easy installer for Mac and Windows is not a simple task. It take a while to do, to update, and to test.
>I guess digiKam relies also on some kde process which need to be lunched along with DigiKam ?
yes, this is why currently KDE windows installer is the best way...
I repeat: i'm developer, not packager. All contributors are fine to help us in this way.
digiKam
Windows Version Fee
I have been recommending digiKam to people for years now but most people reply "What is Linux?" I understand that there is currently no one who is willing to be responsible for packaging the Windows version. Unfortunately I am not able to help in this way.
Perhaps a small fee could be charged for the Windows version. I suspect KDE will not want to do this but the 'Official' Windows version could be offered in parallel. Users in the 'Windows world' are used to and comfortable with paying for software -- of course they would be paying instead for the services of the packager not the software, technically.
In the mean time I will have to stick to Picasa as my second recommendation -- unfortunately tagging support is nearly completely missing from Picasa to name just one item.
at least it compile...
As you can see, digiKam compile fine under Windows Seven, with GCC and MSVC. I personally manage code for Windows....
Yes, I know. Can you as
Yes, I know. Can you as maintainer enable digikam in the build scripts?
no, this is not my role...
This task is delegate to KDE windows team. I'm developer, not packager. I do a lots of work to digiKam. I don't have more free time to manage windows packages.
THANK YOU SO MUCH!!
I would like to thank You digikam developers SO MUCH for such a great piece of software!! You are doing such a great job with it, this is one if not the best images managing software.
Thank you very much - and what is next
First of all thank you very much to all developers and contributors for this software!!!
I really love it and I would also be interested in an easy installation on windows but I can understand Gilles responses. Maybe the KDE Windows guys will help us soon.
But another question: I saw that the release plan has changed and the 2.0.0. is replaced by a 1.6.0. I don't worry about version numbers but also the comment about included GSoC work has been removed. Is the inclusion of this features rescheduled ??
Thanks again and keep on doing this great work.
Daniel
I missed to scroll down
Sorry, ignore my question about 2.0.0 and GSoC. I just missed to scroll down the page.
I like the improvement of
I like the improvement of algorithm to convert 8 bits image to 16 and limit histogram holes during conversion.
SVN revision
Can you publish the svn revision number of your releases for those of us that compile digikam directly from SVN trunk?
I update my local source by 'svn up -r123456789'; when a new version comes out i sort through the logs to figured out the svn revision number. Perhaps there is a better way do update the digikam sources?
thanks and cheers,
- b
Debian packages
Hello,
For those interested, I have packaged digikam 1.5 and the kipi-plugins 1.5 for debian/unstable i386 (these are not official debian packages, so use at your own risks). You can find the packages at http://xraynaudphotos.free.fr/debian.php
Xavier