Bug 298158 - when working in digikam, metadata erased whereas GIMP preserves metadata
Summary: when working in digikam, metadata erased whereas GIMP preserves metadata
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Interroperability (show other bugs)
Version: 2.5.0
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-15 02:05 UTC by Axel Krebs
Modified: 2017-08-13 15:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Krebs 2012-04-15 02:05:32 UTC
User-Agent:       
Build Identifier: 

When I exportet a pic to gimp an re-opende in digikam, all metadata from exposure were kept.

When working on reimported pic batch: 
- change size 
- minimize noise
- sharpen
- use watermark (text)

all metadate were loosen

Reproducible: Always

Steps to Reproduce:
1. as described above
2.
3.


Expected Results:  
digikam should keep metadata in any case- but in cases, where one wants to erase these explicitely

as metadata are crucial informations, I take this as a "major severity"
Comment 1 caulier.gilles 2012-04-15 08:35:18 UTC
Not reproducible here. Which file format you use ?

Gilles Caulier
Comment 2 Axel Krebs 2012-04-15 08:46:10 UTC
last years NIKON: jpg + NIKON NEF


Axel

Am 15.04.2012 10:35, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=298158
> 
> Gilles Caulier <caulier.gilles@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles@gmail.com
> 
> --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> ---
> Not reproducible here. Which file format you use ?
> 
> Gilles Caulier
>
Comment 3 caulier.gilles 2012-06-22 08:49:49 UTC
Official digiKam 2.6.0 release is out since few days now :

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

Please, check if this entry still valid, or update report accordingly.

Thanks in advance.

Gilles Caulier
Comment 4 ronny-kdebug 2012-07-01 11:56:01 UTC
Hey Gilles,
at least for Exposure Blending its still valid in 2.6.0. At least most of the EXIF info is overwritten.
Editing doesn't delete them. At least here.

greets
Comment 5 Marcel Wiesweg 2012-07-21 13:03:24 UTC
Ronny: Exposure blending is a kipi plugin. I didn't try, it should probably copy a sbuset of the metadata from one of the images. If it does not, please file a bug against that.

Axel: Is this about batch editing or image editor? You give four steps. Does any pick of these delete metadata, or only a specific tool?
Comment 6 Axel Krebs 2012-07-21 19:16:21 UTC
Marcel,

please give me a little time


Axel
Am 21.07.2012 15:03, schrieb Marcel Wiesweg:
> https://bugs.kde.org/show_bug.cgi?id=298158
> 
> --- Comment #5 from Marcel Wiesweg <marcel.wiesweg@gmx.de> ---
> Ronny: Exposure blending is a kipi plugin. I didn't try, it should probably
> copy a sbuset of the metadata from one of the images. If it does not, please
> file a bug against that.
> 
> Axel: Is this about batch editing or image editor? You give four steps. Does
> any pick of these delete metadata, or only a specific tool?
>
Comment 7 caulier.gilles 2013-11-22 17:50:53 UTC
Axel, Ronny,

Outside the fact that it can be a problem with ExpoBlending tool as you mention in comment #4, what's the status of this entry when you use the original workflow explained in top entry of this file ?

Note : ExpoBlending mix more than one image to a target and use Enfuse command line tool from Hugin project. It's probably a bug in this program tool, and this must be reported to this project. After all ExpoBlending is just a front end to setup pool of image to mix and to config parameters.

Gilles Caulier
Comment 8 caulier.gilles 2014-08-28 13:33:12 UTC
Can you refresh the status of this file using last digiKam 4.2.0 ?

Gilles Caulier
Comment 9 ronny-kdebug 2014-08-28 15:12:06 UTC
I think you can close it as resolved...

Thanks.