Image file alterations

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Image file alterations

Chris Savery
Hello,
I'm new to digiKam. I am currently using Lightroom on WinXP under VirtualBox. I would very much like to move to using digiKam so that I can do my photo work under linux.

First thing that comes to mind when trying this out:

-> if I add my image file tree being used under Lightroom into digiKam as albums is digiKam going to write back to the image metadata on those images?

I'd rather that all my Canon CR2 images remained intact and unaltered. I would also very much like if they can co-habitate in both Lightroom and digiKam until I have decided that digiKam offers enough incentive to drop Lightroom. I have looked through the manual but can't find a clear answer on this.

Second thing that I'm not clear on is when adding images from my CF cards using the auto-album mode to create date folders is what those 3 date options really mean. It isn't stated anywhere that I can find, but maybe I'm not looking enough. I want to use the same format I do now - eg. 2009/January/03 for the folder name. Is that "full text" or ISO. It would really help if that selector box there gave examples of what the options mean. I guess that should be added to some wish list.

Lastly, in digiKam it looks like there is no similar concept to the "catalog" of Lightroom. As far as I can tell when images are added to an album it is simply a way of managing a file folder tree. So if that's the case I'm not clear how one works with offline content stored on removable media. If the albums are "out there" (not online) is the data still stored in the database. So is there only ONE really big database for everything ever touched in digiKam or is there some way to select a current database, ie. catalog?

I have many years background programming for Win32 GUI in C/C++. If I am able to really use digiKam for my photography under Linux then I'd be really happy to contribute through programming for digiKam too. There would be a learning curve for me as I have not yet coded for Linux Gui (just console apps so far).

Thanks for any input on my questions above.


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Image file alterations

Gerhard Kulzer-3
On Tuesday 13 January 2009 06:10:09 Chris Savery wrote:

> Hello,
> I'm new to digiKam. I am currently using Lightroom on WinXP under
> VirtualBox. I would very much like to move to using digiKam so that I
> can do my photo work under linux.
>
> First thing that comes to mind when trying this out:
>
> -> if I add my image file tree being used under Lightroom into digiKam
> as albums is digiKam going to write back to the image metadata on those
> images?
digiKam cannot write into RAW files, but can write into DNG files and normal
formats like jpg and png, tif. The latter depends on your settings: you can
leave it at the default where metadata are kept in the database only, or tell
digikam to write into the images (I prefer the latter for security reasons).

> I'd rather that all my Canon CR2 images remained intact and unaltered. I
> would also very much like if they can co-habitate in both Lightroom and
> digiKam until I have decided that digiKam offers enough incentive to
> drop Lightroom. I have looked through the manual but can't find a clear
> answer on this.
see above, CR2 will not be touched.
But digikam can convert them into DNG files and add metadata. (If you read my
article on Digital Asset Management http://www.gerhard.fr/DAM you'll find
arguments against keeping propriatary formats in the long run)

> Second thing that I'm not clear on is when adding images from my CF
> cards using the auto-album mode to create date folders is what those 3
> date options really mean. It isn't stated anywhere that I can find, but
> maybe I'm not looking enough. I want to use the same format I do now -
> eg. 2009/January/03 for the folder name. Is that "full text" or ISO. It
> would really help if that selector box there gave examples of what the
> options mean. I guess that should be added to some wish list.
Use the context help: Shift+F1 (question mark appears), then click onto the
Date format and a detailed example explanation will come up.

> Lastly, in digiKam it looks like there is no similar concept to the
> "catalog" of Lightroom. As far as I can tell when images are added to an
> album it is simply a way of managing a file folder tree. So if that's
> the case I'm not clear how one works with offline content stored on
> removable media. If the albums are "out there" (not online) is the data
> still stored in the database. So is there only ONE really big database
> for everything ever touched in digiKam or is there some way to select a
> current database, ie. catalog?
Currently digiKam can not deal with offline content, but that feature is in the
development pipeline.
> I have many years background programming for Win32 GUI in C/C++. If I am
> able to really use digiKam for my photography under Linux then I'd be
> really happy to contribute through programming for digiKam too. There
> would be a learning curve for me as I have not yet coded for Linux Gui
> (just console apps so far).
You are more than welcome to contribute to digikam. It's best to write or talk
to Gilles Gaulier, our lead developer, directly. He is often on the freenode
#digikam channel.

Cheers
Gerhard
> Thanks for any input on my questions above.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Image file alterations

Gilles Caulier-4
In reply to this post by Chris Savery


2009/1/13 Chris Savery <[hidden email]>
Hello,
I'm new to digiKam. I am currently using Lightroom on WinXP under VirtualBox. I would very much like to move to using digiKam so that I can do my photo work under linux.

First thing that comes to mind when trying this out:

-> if I add my image file tree being used under Lightroom into digiKam as albums is digiKam going to write back to the image metadata on those images?

By default no. There is a set of options in digiKam Metadata panel to configure this behaviour

http://www.flickr.com/photos/digikam/3037188459/sizes/o/
 


I'd rather that all my Canon CR2 images remained intact and unaltered.

This wil be the case. Not that digiKam use Exiv2 library to play with image metadata (reading and writting)


 
I would also very much like if they can co-habitate in both Lightroom and digiKam until I have decided that digiKam offers enough incentive to drop Lightroom. I have looked through the manual but can't find a clear answer on this.

Second thing that I'm not clear on is when adding images from my CF cards using the auto-album mode to create date folders is what those 3 date options really mean. It isn't stated anywhere that I can find, but maybe I'm not looking enough. I want to use the same format I do now - eg. 2009/January/03 for the folder name. Is that "full text" or ISO. It would really help if that selector box there gave examples of what the options mean. I guess that should be added to some wish list.

I remember something like that in bugzilla. People want to have the best flexibility about file renaming. Look here :

http://bugs.kde.org/show_bug.cgi?id=141240
http://bugs.kde.org/show_bug.cgi?id=144227
http://bugs.kde.org/show_bug.cgi?id=166060
 


Lastly, in digiKam it looks like there is no similar concept to the "catalog" of Lightroom. As far as I can tell when images are added to an album it is simply a way of managing a file folder tree.

not only. digiKam support virtual album (Tags, Search, etc...)
 
So if that's the case I'm not clear how one works with offline content stored on removable media. If the albums are "out there" (not online) is the data still stored in the database.

With KDE4 version, yes.

 
So is there only ONE really big database for everything ever touched in digiKam or is there some way to select a current database, ie. catalog?

There is one big database file for all collections.



I have many years background programming for Win32 GUI in C/C++. If I am able to really use digiKam for my photography under Linux then I'd be really happy to contribute through programming for digiKam too. There would be a learning curve for me as I have not yet coded for Linux Gui (just console apps so far).

You is welcome to join team. digiKam is just ported to Windows, and testers/developers are welcome to hack this version. digiKam is a Linux application originaly, based on Qt4 toolkit. it compile and run under Unix, Win32 and MacosX in native.

The first pointer to start to help is this page :

http://www.digikam.org/contrib
 
Thanks for your help

Gilles Caulier


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Re: Image file alterations

Gilles Caulier-4
In reply to this post by Gerhard Kulzer-3


2009/1/13 Gerhard Kulzer <[hidden email]>
On Tuesday 13 January 2009 06:10:09 Chris Savery wrote:
> Hello,
> I'm new to digiKam. I am currently using Lightroom on WinXP under
> VirtualBox. I would very much like to move to using digiKam so that I
> can do my photo work under linux.
>
> First thing that comes to mind when trying this out:
>
> -> if I add my image file tree being used under Lightroom into digiKam
> as albums is digiKam going to write back to the image metadata on those
> images?
digiKam cannot write into RAW files, but can write into DNG files and normal
formats like jpg and png, tif. The latter depends on your settings: you can
leave it at the default where metadata are kept in the database only, or tell
digikam to write into the images (I prefer the latter for security reasons).

> I'd rather that all my Canon CR2 images remained intact and unaltered. I
> would also very much like if they can co-habitate in both Lightroom and
> digiKam until I have decided that digiKam offers enough incentive to
> drop Lightroom. I have looked through the manual but can't find a clear
> answer on this.
see above, CR2 will not be touched.
But digikam can convert them into DNG files and add metadata. (If you read my
article on Digital Asset Management http://www.gerhard.fr/DAM you'll find
arguments against keeping propriatary formats in the long run)

Note : with Exiv2 0.18, a generic tiff writter have been implemented, and Exiv2 start to tupport writting mode in some RAW file format based on TIFF/EP, as DNG of course, but also, PEF, and NEF. I know that Andreas Huggel (Exiv2 coordinator) work on CR2 support.

As Gerhard said previously, DNG can be a solution. This depand of your workflow.

DNG is not perfect. I recommend to test my RAW to DNG converter tool for Linux avaialble in digiKam as plugin:

http://www.digikam.org/drupal/node/373

Personally, i don't use yet DNG. My raw workflow is :

RAW (mrw-minolta) [Camera, backup]

PNG (16 bits) [Editing, cataloging, storage, backup, versioning]

JPEG [publishing and printing only - i never store in local JPEG image]

Gilles Caulier

Best

Gilles Caulier
 


> Second thing that I'm not clear on is when adding images from my CF
> cards using the auto-album mode to create date folders is what those 3
> date options really mean. It isn't stated anywhere that I can find, but
> maybe I'm not looking enough. I want to use the same format I do now -
> eg. 2009/January/03 for the folder name. Is that "full text" or ISO. It
> would really help if that selector box there gave examples of what the
> options mean. I guess that should be added to some wish list.
Use the context help: Shift+F1 (question mark appears), then click onto the
Date format and a detailed example explanation will come up.

> Lastly, in digiKam it looks like there is no similar concept to the
> "catalog" of Lightroom. As far as I can tell when images are added to an
> album it is simply a way of managing a file folder tree. So if that's
> the case I'm not clear how one works with offline content stored on
> removable media. If the albums are "out there" (not online) is the data
> still stored in the database. So is there only ONE really big database
> for everything ever touched in digiKam or is there some way to select a
> current database, ie. catalog?
Currently digiKam can not deal with offline content, but that feature is in the
development pipeline.
> I have many years background programming for Win32 GUI in C/C++. If I am
> able to really use digiKam for my photography under Linux then I'd be
> really happy to contribute through programming for digiKam too. There
> would be a learning curve for me as I have not yet coded for Linux Gui
> (just console apps so far).
You are more than welcome to contribute to digikam. It's best to write or talk
to Gilles Gaulier, our lead developer, directly. He is often on the freenode
#digikam channel.

Cheers
Gerhard
> Thanks for any input on my questions above.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Reply | Threaded
Open this post in threaded view
|

Digikam settings dialog crashes

Sveinn í Felli
In reply to this post by Gerhard Kulzer-3
Hi,

I had a HDD failure some days ago, it was one of my data
disks (not the OS), which contained my photos on a FAT32
partition (sharing with win2k). No harm done, I have rsync
mirroring a backup onto another disk (external), so I was
quickly up and running with new disks and a new partition
layout.
Since I changed a bit the mounts, I first made a dummy of my
old mount, eg. /mnt/oldphotos where I copied digikam3.db
along with some photos for testing.
Then I ran digikam, no problems, it asked whether to remove
the missing photos from the DB, yes, and opened normally.
Digikam seemed to behave very well, until I wanted to run
"Settings/Configure Digikam" to switch album root to
/mnt/newphotos, Digikam crashed with signal 11 (SIGSEGV).
Tried this several times, then I edited
/home/sveinki/.kde/share/config/digikamrc and changed the
album root directly. Booted digikam, all normal and new
albumroot showing, but still this crash when clicking on
"Settings/Configure Digikam".

I'm not even sure it has anything to do with my hard disk
failure, I have not touched the Digikam settings for a
while, it just worked, and I've had all kinds of other minor
issues due to the system being a 64bit one. And I know I can
downgrade to 0.9.3 which is totally stable.

Any idea ?
Thanks,
Sveinn í Felli

System: Intel(R) 64bit Core(TM)2 Quad CPU Q9400 @ 2.66GHz
OS: OpenSuse 11.0 and KDE 3.5.10 r33.1
Digikam: v0.9.4-52.1-x86_64 from OpenSuse repo KDE:Backports
Here's the debugging info:

[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9ab3f0d700 (LWP 5486)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f9ab11f412c in ?? () from /lib64/libc.so.6
#6  0x00007f9ab11f6111 in malloc () from /lib64/libc.so.6
#7  0x00007f9ab159bafd in operator new () from
/usr/lib64/libstdc++.so.6
#8  0x00007f9ab385690f in QMapPrivate<QString,
QString>::insert ()
   from /opt/kde3/lib64/libdigikam.so.0
#9  0x00007f9ab3856d5d in QMap<QString, QString>::insert ()
   from /opt/kde3/lib64/libdigikam.so.0
#10 0x00007f9ab3a2e2a0 in
Digikam::SetupICC::parseProfilesfromDir ()
   from /opt/kde3/lib64/libdigikam.so.0
#11 0x00007f9ab3a2e9be in Digikam::SetupICC::fillCombos ()
   from /opt/kde3/lib64/libdigikam.so.0
#12 0x00007f9ab3a2f060 in Digikam::SetupICC::readSettings ()
   from /opt/kde3/lib64/libdigikam.so.0
#13 0x00007f9ab3a2f2a5 in
Digikam::SetupICC::slotToggledWidgets ()
   from /opt/kde3/lib64/libdigikam.so.0
#14 0x00007f9ab3a2f38c in Digikam::SetupICC::qt_invoke ()
   from /opt/kde3/lib64/libdigikam.so.0
#15 0x00007f9ab1dd6f5f in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00007f9ab1dd9045 in QObject::activate_signal_bool ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00007f9ab1e66311 in QButton::setState ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00007f9ab3a2f1ce in Digikam::SetupICC::readSettings ()
   from /opt/kde3/lib64/libdigikam.so.0
#19 0x00007f9ab3a31216 in Digikam::SetupICC::SetupICC ()
   from /opt/kde3/lib64/libdigikam.so.0
#20 0x00007f9ab3a25ca3 in Digikam::Setup::Setup ()
   from /opt/kde3/lib64/libdigikam.so.0
#21 0x00007f9ab37ab35c in Digikam::DigikamApp::setup ()
   from /opt/kde3/lib64/libdigikam.so.0
#22 0x00007f9ab37b0148 in Digikam::DigikamApp::qt_invoke ()
   from /opt/kde3/lib64/libdigikam.so.0
#23 0x00007f9ab1dd6f5f in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00007f9ab1dd92d2 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00007f9ab2c3a8c0 in KAction::slotPopupActivated ()
   from /opt/kde3/lib64/libkdeui.so.4
#26 0x00007f9ab2c3abc8 in KAction::qt_invoke ()
   from /opt/kde3/lib64/libkdeui.so.4
#27 0x00007f9ab1dd6f5f in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#28 0x00007f9ab20f120d in QSignal::signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#29 0x00007f9ab1df0c44 in QSignal::activate ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#30 0x00007f9ab1ed3ebd in QPopupMenu::mouseReleaseEvent ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#31 0x00007f9ab1e0c246 in QWidget::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#32 0x00007f9ab1d785d5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#33 0x00007f9ab1d795d2 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#34 0x00007f9ab26d2952 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#35 0x00007f9ab1d16f8e in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#36 0x00007f9ab1d15a7e in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#37 0x00007f9ab1d2880a in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#38 0x00007f9ab1d8f109 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#39 0x00007f9ab1d8ef92 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#40 0x000000000040337b in ?? ()
#41 0x00007f9ab119a436 in __libc_start_main () from
/lib64/libc.so.6
#42 0x0000000000402029 in ?? ()
#43 0x00007fffbbf51f38 in ?? ()
#44 0x000000000000001c in ?? ()
#45 0x0000000000000005 in ?? ()
#46 0x00007fffbbf5239c in ?? ()
#47 0x00007fffbbf523a4 in ?? ()
#48 0x00007fffbbf523ad in ?? ()
#49 0x00007fffbbf523b5 in ?? ()
#50 0x00007fffbbf523bb in ?? ()
#51 0x0000000000000000 in ?? ()

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users