I've got digikam 1.1.0 (through a kde on windows install) on a
fully-patched win XP machine, and am having significant stability issues when trying to move my pictures around into different folders. Yesterday it probably hung or crashed 10 times over the course of the day, and I can't see any real pattern to it, except that it was usually when moving pictures from one folder to another. However, it doesn't always crash when moving them, only sometimes. The symptoms are usually either that digikam just hangs for a minute or two using 80% cpu, and then just disappears with no notice, but sometimes gives me a vc library error (something about requesting an unusual way of shutting down), and sometimes I get a Dr Watson error. And the function to delete pictures simply doesn't work. The pictures don't disappear from either the album, nor from the HD. Are these file-management issues likely to have been fixed in a later release that hasn't been ported windows yet? D _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hello everybody!
Just a short question on my workflow, since I guess that there is a nicer and faster way than I am doing it. Here it comes: I always take a RAW and a JPG copy of each picture with my camera because I want to have a RAW copy of my good picures. Then I download the pictures in digiKam and delete all the crap I took. During this process I don't want to scrall through every picture twice (and have to delete twice) so I only look at the JPGS (by activating the filter at the bottom of the DK window). After this process is done I still have all the crap RAW files of which I deleted the jpgs. Then I go manually through the folder and delete every RAW file of which I do not have the corresponded JPG because, of course I don't want to keep a RAW copy of the crap photos I took. Then I copy the RAW files of the good fotos into another folder and store them away because at the moment I just want to backup my phots as RAW files but don't need them for now. But this process sometimes takes quite a long time and there is also the danger of deleting the wrong RAW files just by accident when doing it fast and annoyed by this boring work. So now I guess there must be a way of automating this within DK. But this it not all. The ideal solution is a little more complex: Since I even don't want to keep the RAW files of ALL photos of which I keep the JPGs I am even looking for the possibility to for example to delete all RAW files of which I do not have a corresponding JPEG rated lower than 4 or with or without a certain tag. Sometimes you want to keep bad picutres just for memorizing moments but which do not justify occupying the momeory with big RAW files. Anybody can help me with that? It would also be helpful to hear (or read) how other people deal with this problem. I guess I am not the only one wanting RAW-Files of only a selection of the photos they took. thanks a lot in andvance micha ___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Am 22.08.2010 23:12, schrieb Micha Neubauer: > Hello everybody! > > Just a short question on my workflow, since I guess that there is a nicer and faster way > than I am doing it. Here it comes: > > I always take a RAW and a JPG copy of each picture with my camera because I want to have a > RAW copy of my good picures. Then I download the pictures in digiKam and delete all the > crap I took. > During this process I don't want to scrall through every picture twice (and have to delete > twice) so I only look at the JPGS (by activating the filter at the bottom of the DK > window). > After this process is done I still have all the crap RAW files of which I deleted the > jpgs. Then I go manually through the folder and delete every RAW file of which I do not > have the corresponded JPG because, of course I don't want to keep a RAW copy of the crap > photos I took. Then I copy the RAW files of the good fotos into another folder and store > them away because at the moment I just want to backup my phots as RAW files but don't need > them for now. > But this process sometimes takes quite a long time and there is also the danger of > deleting the wrong RAW files just by accident when doing it fast and annoyed by this boring > work. So now I guess there must be a way of automating this within DK. > - "delete to trash" the unwanted jpegs - write a small script that searches through the trash folder for jpegs and deletes the raw files with the same basename; then delete the jpeg in the trash (or move both to another, private trash) like this (bash script): cd $DIGIKAM_TRASH files=$(/bin/ls -1 *.jpg ) cd $DIGIKAM_ROOT for i in $files do DNG=`basename $i .jpg`.dng JPG=`basename $i` find -L $PROOT -name $DNG -exec mv -fv {} $TRASH \; find -L $PROOT -name $JPG -exec mv -fv {} $TRASH \; # doublettes rm -f $DIGIKAM_TRASH/$i done > But this it not all. The ideal solution is a little more complex: > Since I even don't want to keep the RAW files of ALL photos of which I keep the JPGs I am > even looking for the possibility to for example to delete all RAW files of which I do not > have a corresponding JPEG rated lower than 4 or with or without a certain tag. Sometimes > you want to keep bad picutres just for memorizing moments but which do not justify > occupying the momeory with big RAW files. > > Anybody can help me with that? It would also be helpful to hear (or read) how other people > deal with this problem. I guess I am not the only one wanting RAW-Files of only a > selection of the photos they took. > thanks a lot in andvance > > micha > > cd whereyourjpegsare files=$(find -maxdepth 1 -name "*.jpg") for i in $files do rating=`exiftool -f -rating $i | awk '{print $3}'` if [ $rating == "-" ] then rating=0 fi if [ $rating -lt $min_rating ] then DNG=`basename $i .jpg`.dng find -L $DIGIKAM_ROOT -name $DNG -exec mv -fv {} $TRASH \; fi done use at your own risk ;-) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hello Ruediger!
Wow, thaks a lot for sharing these scripts. Looks like they do what I want... have not tested them yet due to lack of time. Anyway it seems like there is no "internal" fuction in DK, since nobody else replied. Thanks a lot again lg micha On Monday 23 August 2010, 23:50:49 ruediger wrote: > Am 22.08.2010 23:12, schrieb Micha Neubauer: > > Hello everybody! > > > > Just a short question on my workflow, since I guess that there is a nicer > > and faster way than I am doing it. Here it comes: > > > > I always take a RAW and a JPG copy of each picture with my camera because > > I want to have a RAW copy of my good picures. Then I download the > > pictures in digiKam and delete all the crap I took. > > During this process I don't want to scrall through every picture twice > > (and have to delete twice) so I only look at the JPGS (by activating the > > filter at the bottom of the DK window). > > After this process is done I still have all the crap RAW files of which I > > deleted the jpgs. Then I go manually through the folder and delete every > > RAW file of which I do not have the corresponded JPG because, of course > > I don't want to keep a RAW copy of the crap photos I took. Then I copy > > the RAW files of the good fotos into another folder and store them away > > because at the moment I just want to backup my phots as RAW files but > > don't need them for now. > > But this process sometimes takes quite a long time and there is also the > > danger of deleting the wrong RAW files just by accident when doing it > > fast and annoyed by this boring work. So now I guess there must be a way > > of automating this within DK. > > how I do it: > - "delete to trash" the unwanted jpegs > - write a small script that searches through the trash folder for jpegs > and deletes the raw files with the same basename; then delete the jpeg > in the trash (or move both to another, private trash) > like this (bash script): > cd $DIGIKAM_TRASH > files=$(/bin/ls -1 *.jpg ) > cd $DIGIKAM_ROOT > for i in $files > do > DNG=`basename $i .jpg`.dng > JPG=`basename $i` > find -L $PROOT -name $DNG -exec mv -fv {} $TRASH \; > find -L $PROOT -name $JPG -exec mv -fv {} $TRASH \; # doublettes > rm -f $DIGIKAM_TRASH/$i > done > > > But this it not all. The ideal solution is a little more complex: > > Since I even don't want to keep the RAW files of ALL photos of which I > > keep the JPGs I am even looking for the possibility to for example to > > delete all RAW files of which I do not have a corresponding JPEG rated > > lower than 4 or with or without a certain tag. Sometimes you want to > > keep bad picutres just for memorizing moments but which do not justify > > occupying the momeory with big RAW files. > > > > Anybody can help me with that? It would also be helpful to hear (or read) > > how other people deal with this problem. I guess I am not the only one > > wanting RAW-Files of only a selection of the photos they took. > > thanks a lot in andvance > > > > micha > > like this: > cd whereyourjpegsare > files=$(find -maxdepth 1 -name "*.jpg") > for i in $files > do > rating=`exiftool -f -rating $i | awk '{print $3}'` > if [ $rating == "-" ] > then > rating=0 > fi > if [ $rating -lt $min_rating ] > then > DNG=`basename $i .jpg`.dng > find -L $DIGIKAM_ROOT -name $DNG -exec mv -fv {} $TRASH \; > fi > done > > > use at your own risk ;-) > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Micha Neubauer wrote:
> Hello Ruediger! > > Wow, thaks a lot for sharing these scripts. Looks like they do what I want... have not > tested them yet due to lack of time. > Anyway it seems like there is no "internal" fuction in DK, since nobody else replied. > > Just to chime in a me too ;-) I have a similar workflow (just don't get too much time for the deleting bit (not even sorting out the bad/good shots, so I have accumulated over 170GB of images now, quite a few of them need sorting out) Some things that come up in my mind here: - this kind of workflow could be better supported in digikam, perhaps we need to collectively formulate a wish on bugs.kde.org? - I use gqview, now called geeqie. The newer versions support RAW+JPG and deleting an image will delete both together. - dealing with multiple renderings of the original RAW file is not so easy (sometimes the camera jpeg is good enough, but on some images, you need multiple attempts to get what you want from the RAW file. I suppose the built-in editor works ok for this, but when editing in an external tool like gimp+ufraw makes it hard to keep track) some features that would be useful: - upon importing, provide option to use a flowing light-table like quick selection (like the apple dashboard when you move your mouse over it, the icons grow, only bigger ;-) to filter out bad shots (out of focus, cut-off subjects, over/underexposed). That would need to have a film-like ribbon with enlarged versions of about 3 shots on the screen (with easy option to go fullscreen and zoom in). - this would also be useful on a selection (multiple albums) from the normal digikam UI for when you don't have time to do this at import time. - better tracking of tags/ratings for images derived from the same RAW data. (defining a group identity? storing this in the DB, scanning should be able to use exif data to automatically form such groups) Cheers Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Micha Neubauer
I would have used Ztree to delete them, not sure if there's an equivalent file manager in Linux.
I would tag all the jpg files in the affected folder, then use the control+Batch command to use the base of their filenames to create a batch file to rename their matching raw files to, say, *.rawsave. Then I'd delete all remaining raw files and rename the rawsave files back to raw. I assume digiKam can then work out which thumbnails to get rid of. This procedure could also work for multiple directories. You could do it the same way by manipulating directory listings into scripts by hand if you find Ruediger's scripts daunting. It sounds like digiKam needs a way for raw/jpg pairs to be able to be treated as one unit, like Lightroom's stacks. Doing it with scripts is bound to lead to tears sooner or later. Peter Shute -------------------------- Sent using BlackBerry ----- Original Message ----- From: Micha Neubauer <[hidden email]> To: [hidden email] <[hidden email]> Sent: Thu Aug 26 22:12:16 2010 Subject: Re: [Digikam-users] workflow for deleting not wanted RAW-Files Hello Ruediger! Wow, thaks a lot for sharing these scripts. Looks like they do what I want... have not tested them yet due to lack of time. Anyway it seems like there is no "internal" fuction in DK, since nobody else replied. Thanks a lot again lg micha On Monday 23 August 2010, 23:50:49 ruediger wrote: > Am 22.08.2010 23:12, schrieb Micha Neubauer: > > Hello everybody! > > > > Just a short question on my workflow, since I guess that there is a nicer > > and faster way than I am doing it. Here it comes: > > > > I always take a RAW and a JPG copy of each picture with my camera because > > I want to have a RAW copy of my good picures. Then I download the > > pictures in digiKam and delete all the crap I took. > > During this process I don't want to scrall through every picture twice > > (and have to delete twice) so I only look at the JPGS (by activating the > > filter at the bottom of the DK window). > > After this process is done I still have all the crap RAW files of which I > > deleted the jpgs. Then I go manually through the folder and delete every > > RAW file of which I do not have the corresponded JPG because, of course > > I don't want to keep a RAW copy of the crap photos I took. Then I copy > > the RAW files of the good fotos into another folder and store them away > > because at the moment I just want to backup my phots as RAW files but > > don't need them for now. > > But this process sometimes takes quite a long time and there is also the > > danger of deleting the wrong RAW files just by accident when doing it > > fast and annoyed by this boring work. So now I guess there must be a way > > of automating this within DK. > > how I do it: > - "delete to trash" the unwanted jpegs > - write a small script that searches through the trash folder for jpegs > and deletes the raw files with the same basename; then delete the jpeg > in the trash (or move both to another, private trash) > like this (bash script): > cd $DIGIKAM_TRASH > files=$(/bin/ls -1 *.jpg ) > cd $DIGIKAM_ROOT > for i in $files > do > DNG=`basename $i .jpg`.dng > JPG=`basename $i` > find -L $PROOT -name $DNG -exec mv -fv {} $TRASH \; > find -L $PROOT -name $JPG -exec mv -fv {} $TRASH \; # doublettes > rm -f $DIGIKAM_TRASH/$i > done > > > But this it not all. The ideal solution is a little more complex: > > Since I even don't want to keep the RAW files of ALL photos of which I > > keep the JPGs I am even looking for the possibility to for example to > > delete all RAW files of which I do not have a corresponding JPEG rated > > lower than 4 or with or without a certain tag. Sometimes you want to > > keep bad picutres just for memorizing moments but which do not justify > > occupying the momeory with big RAW files. > > > > Anybody can help me with that? It would also be helpful to hear (or read) > > how other people deal with this problem. I guess I am not the only one > > wanting RAW-Files of only a selection of the photos they took. > > thanks a lot in andvance > > > > micha > > like this: > cd whereyourjpegsare > files=$(find -maxdepth 1 -name "*.jpg") > for i in $files > do > rating=`exiftool -f -rating $i | awk '{print $3}'` > if [ $rating == "-" ] > then > rating=0 > fi > if [ $rating -lt $min_rating ] > then > DNG=`basename $i .jpg`.dng > find -L $DIGIKAM_ROOT -name $DNG -exec mv -fv {} $TRASH \; > fi > done > > > use at your own risk ;-) > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de _______________________________________________ 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 |
One hint about the command "mv":
if you are moving a file from one filesystem (partition) to a different filesystem the time the command needs to do it is different. Espacially for large files. Reason: If you move a file in the same filesystem the OS(operating system) will only write the inode number of the file into the dataset of the new directory. The data itself will stay at the same physical place in the file system. A move to a different filesystem will cause two actions done by the OS: first copy (for one moment you the double amount of space) to different filesystem. second delte the file in the old place. Only move into TRASH what you will keep for later times. But TRASH means: Idont't want it. So remove it and you will save space. Next hint with scripts and find command: find -L $PROOT -name $JPG -exec mv -fv {} $TRASH \; do first find -L $PROOT -name $JPG -exec ls {} $TRASH \; You will see what would be removed. If thaat is correct, change ls to mv or rm Am Freitag, 27. August 2010 schrieb Peter Shute: > I would have used Ztree to delete them, not sure if there's an > equivalent file manager in Linux. > > I would tag all the jpg files in the affected folder, then use the > control+Batch command to use the base of their filenames to create > a batch file to rename their matching raw files to, say, > *.rawsave. Then I'd delete all remaining raw files and rename the > rawsave files back to raw. I assume digiKam can then work out > which thumbnails to get rid of. > > This procedure could also work for multiple directories. You could > do it the same way by manipulating directory listings into scripts > by hand if you find Ruediger's scripts daunting. > > It sounds like digiKam needs a way for raw/jpg pairs to be able to > be treated as one unit, like Lightroom's stacks. Doing it with > scripts is bound to lead to tears sooner or later. > > Peter Shute > > > -------------------------- > Sent using BlackBerry > > ----- Original Message ----- > From: Micha Neubauer <[hidden email]> > To: [hidden email] <[hidden email]> > Sent: Thu Aug 26 22:12:16 2010 > Subject: Re: [Digikam-users] workflow for deleting not wanted > RAW-Files > > Hello Ruediger! > > Wow, thaks a lot for sharing these scripts. Looks like they do what > I want... have not tested them yet due to lack of time. > Anyway it seems like there is no "internal" fuction in DK, since > nobody else replied. > > Thanks a lot again > lg > micha > > On Monday 23 August 2010, 23:50:49 ruediger wrote: > > Am 22.08.2010 23:12, schrieb Micha Neubauer: > > > Hello everybody! > > > > > > Just a short question on my workflow, since I guess that there > > > is a nicer and faster way than I am doing it. Here it comes: > > > > > > I always take a RAW and a JPG copy of each picture with my > > > camera because I want to have a RAW copy of my good picures. > > > Then I download the pictures in digiKam and delete all the crap > > > I took. > > > During this process I don't want to scrall through every > > > picture twice (and have to delete twice) so I only look at the > > > JPGS (by activating the filter at the bottom of the DK window). > > > After this process is done I still have all the crap RAW files > > > of which I deleted the jpgs. Then I go manually through the > > > folder and delete every RAW file of which I do not have the > > > corresponded JPG because, of course I don't want to keep a RAW > > > copy of the crap photos I took. Then I copy the RAW files of > > > the good fotos into another folder and store them away because > > > at the moment I just want to backup my phots as RAW files but > > > don't need them for now. > > > But this process sometimes takes quite a long time and there is > > > also the danger of deleting the wrong RAW files just by > > > accident when doing it fast and annoyed by this boring work. So > > > now I guess there must be a way of automating this within DK. > > > > how I do it: > > - "delete to trash" the unwanted jpegs > > - write a small script that searches through the trash folder for > > jpegs and deletes the raw files with the same basename; then > > delete the jpeg in the trash (or move both to another, private > > trash) > > like this (bash script): > > cd $DIGIKAM_TRASH > > files=$(/bin/ls -1 *.jpg ) > > cd $DIGIKAM_ROOT > > for i in $files > > do > > DNG=`basename $i .jpg`.dng > > JPG=`basename $i` > > find -L $PROOT -name $DNG -exec mv -fv {} $TRASH \; > > find -L $PROOT -name $JPG -exec mv -fv {} $TRASH \; # > > doublettes rm -f $DIGIKAM_TRASH/$i > > done > > > > > But this it not all. The ideal solution is a little more > > > complex: Since I even don't want to keep the RAW files of ALL > > > photos of which I keep the JPGs I am even looking for the > > > possibility to for example to delete all RAW files of which I > > > do not have a corresponding JPEG rated lower than 4 or with or > > > without a certain tag. Sometimes you want to keep bad picutres > > > just for memorizing moments but which do not justify occupying > > > the momeory with big RAW files. > > > > > > Anybody can help me with that? It would also be helpful to hear > > > (or read) how other people deal with this problem. I guess I am > > > not the only one wanting RAW-Files of only a selection of the > > > photos they took. thanks a lot in andvance > > > > > > micha > > > > like this: > > cd whereyourjpegsare > > files=$(find -maxdepth 1 -name "*.jpg") > > for i in $files > > do > > rating=`exiftool -f -rating $i | awk '{print $3}'` > > if [ $rating == "-" ] > > then > > rating=0 > > fi > > if [ $rating -lt $min_rating ] > > then > > DNG=`basename $i .jpg`.dng > > find -L $DIGIKAM_ROOT -name $DNG -exec mv -fv {} $TRASH \; > > fi > > done > > > > > > use at your own risk ;-) > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > ___________________________________________________________ > Telefonate ohne weitere Kosten vom PC zum PC: > http://messenger.yahoo.de > _______________________________________________ > 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 > -- Andreas Tono _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by pshute
In data venerdì 27 agosto 2010 00:24:40, Peter Shute ha scritto:
> It sounds like digiKam needs a way for raw/jpg pairs to be able to be > treated as one unit, like Lightroom's stacks. Doing it with scripts is > bound to lead to tears sooner or later. How does Lightroom do this kind of thing? I suppose that grouping RAW shots with their associated JPGs/PNGs could be done storing something unique in each derived image metadata. This way one can move or rename files, without the risk of breaking the reference to the original RAW image. Moreover, since most of the external editors like Gimp leave most of the Exif metadata untouched, this reference could easily survive when you edit the image in an external program (actually, when you save a JPEG image in Gimp you can choose also to preserve Exif and XMP metadata[1]). This unique metadata entry could be something like an hash of the original RAW image (don' we already use something similar to find duplicate images?). One could associate some JPGs to a RAW manually, selecting them and then choosing some option somewhere in the menus, or during camera import, since often a RAW and a JPG from camera share the same base name, with just a different extension. What do you think about these arguments? regards gerlos [1]: But at the moment Gimp removes IPTC metadata from JPG images. It seems to be an old, known problem (see http://www.flickr.com/photos/ricardo_ferreira/2435354902/), but for some reason no one filed this bug before on bugzilla. Now it's here: https://bugzilla.gnome.org/show_bug.cgi?id=629044 -- "Life is pretty simple: You do some stuff. Most fails. Some works. You do more of what works. If it works big, others quickly copy it. Then you do something else. The trick is the doing something else." < http://gerlos.altervista.org > gerlos +- - - > gnu/linux registred user #311588 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Micha Neubauer
Lightroom allows you to create a "stack". This is a group of images, represented on screen as a thumbnail of the first image only (or any other image you nominate). You can identify it as a stack because it has the number of images in that stack superimposed over one corner of it.
You can automatically stack all images taken within, say, 1 second of each other, thus stacking all continuous bursts of shots, and I assume it would also match up all raw/ jpg pairs because their time is the same. You can manually stack any images you like, they don't have to be truly related in any way (other than being in the same folder, I think). The idea is to reduce clutter. It appears there's no way to delete a whole stack at once. If you try, it just deletes the first image in the stack. So if this approach was to be the solution for this problem in digiKam then the digiKam implementation would have to allow that. As for how people handle this situation in Lightroom, apparently the pairs can be treated separately like in digiKam, or with the jpg acting as a sidecar for the raw, in which case it's inaccessible. In the former case, there doesn't appear to be any magic way of getting rid of those files that have had their matching pair deleted. In the current version of digiKam, I think that given the pain involved in deleting the unwanted jpgs and then trying to locate their matching pair to also delete, I would just review and delete in pairs. One suggestion I read was to adjust the thumbnail size until there are two columns, so that the jpg/raw pairs are side by side, making the reviewing operation simpler. Peter Shute -------------------------- Sent using BlackBerry ----- Original Message ----- From: gerlos <[hidden email]> To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Sent: Wed Sep 08 21:34:24 2010 Subject: Re: [Digikam-users] workflow for deleting not wanted RAW-Files In data venerdì 27 agosto 2010 00:24:40, Peter Shute ha scritto: > It sounds like digiKam needs a way for raw/jpg pairs to be able to be > treated as one unit, like Lightroom's stacks. Doing it with scripts is > bound to lead to tears sooner or later. How does Lightroom do this kind of thing? I suppose that grouping RAW shots with their associated JPGs/PNGs could be done storing something unique in each derived image metadata. This way one can move or rename files, without the risk of breaking the reference to the original RAW image. Moreover, since most of the external editors like Gimp leave most of the Exif metadata untouched, this reference could easily survive when you edit the image in an external program (actually, when you save a JPEG image in Gimp you can choose also to preserve Exif and XMP metadata[1]). This unique metadata entry could be something like an hash of the original RAW image (don' we already use something similar to find duplicate images?). One could associate some JPGs to a RAW manually, selecting them and then choosing some option somewhere in the menus, or during camera import, since often a RAW and a JPG from camera share the same base name, with just a different extension. What do you think about these arguments? regards gerlos [1]: But at the moment Gimp removes IPTC metadata from JPG images. It seems to be an old, known problem (see http://www.flickr.com/photos/ricardo_ferreira/2435354902/), but for some reason no one filed this bug before on bugzilla. Now it's here: https://bugzilla.gnome.org/show_bug.cgi?id=629044 -- "Life is pretty simple: You do some stuff. Most fails. Some works. You do more of what works. If it works big, others quickly copy it. Then you do something else. The trick is the doing something else." < http://gerlos.altervista.org > gerlos +- - - > gnu/linux registred user #311588 _______________________________________________ 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 |
Free forum by Nabble | Edit this page |