![]() The beta version had the fix in it that was included with the next stable version. Waiting on the next stable version to come out. I used the beta version of Gimp to avoid this problem when I had a Pentax k-r (non Ricoh body). Older versions of Gimp likely won't strip it if it is a Ricoh made Pentax camera. Well, that's the joy of using free software.If you are using a camera prior to a Ricoh Pentax camera, older versions of Gimp can strip the EXIF data. I've copied an exiftool command line copy exif data into a shortcut on my desktop. I use Gimp 2.10.18 and exif data is lost at export. The Ubuntu repository, however, should have the latest version of stable Gimp in it soon though. There is the chance though, that one of the Ubuntu updates, if I don't keep paying attention, will update over top of 2.10.18 with the current stable version in the repositoryĪlso, I could install the lastest stable version of Gimp with flatpak, which is suppose to have the fix. Now that I have a Ricoh/Pentax camera body (the k-s2), probably I could go back to 2.10.18 and everything would work fine - might give that a try. Under the "Edit/preferences" menu, under "import and export", make sure you check all the boxes relevant to retaining exif data.I believe back when I was running 2.10.18, I was experiencing the problem with my old camera, the Pentax k-r, where EXIF data wasn't being retained with "Pentax" camera bodies (not Ricoh made ones), as is similar to this thread: or this thread Note there is a handy NodeJS for Exiv2 as well.I'm running Gimp 2.10.18 on Linux Mint.First, my BREW was messed up because of Yosemite, but I got this unwedged. ![]() So, I went the BREW path, as I believe it has fewer issues (for me) than PORTS. No Exiv2 binary/DMG for OSX, though lots of people put in the time to compile Exiv2 from source. So there is this tool called Exiv2 that can do exactly the issue, namely cross-filetype, multi-faceted metadata editing. Works well, has wildcard and batch processing options, but only deals with PNG. Oddly, it will show two Titles if one is inserted by ImageMagick or ExifTool. Like Inkscape, PNGCommentator actually implements things correctly.Not to mention the university site hosting Exiftool is down. Turns out that Exiftool sucks equally as bad. If the metadata is originally created by Inkscape, it can edit it in a way that preserves.Can read and write all metadata, but does it in a way that OSX Preview will ignore/overwrite.Turn off remove metadata options to preserve metadata.Too bad this doesn't work, that is it cannot edit metadata in JPG files.Unfortunately GIMP won't keep metadata in the XCF native GIMP file.Partha's McGimp variants, the McGimp 2.9.5 64-bit Experimental, or McGimp 2.9.5 64-bit Color Corrected Experimental, are based on 2.9.4 (and are interesting projects in their own right, with HDR extensions and plugins).Note that these are the experimental/unstable releases (stable releases are every few years, so if you want this functionality, have to live on the edge a bit). It is under the menu > Image > Image Metadata. EXIF, XMP metadata editor/viewer added as of Gimp 2.9.4 (possibly 2.9.2).File > Document Metadata provides a nice Dublin Core interface.Don't use this or it will corrupt the file. Somewhat awkward XML editor for SVG metadata.This is because Inkscape puts the info in front of IDAT, but the others do not. 1 However, if the metadata is written by Inkscape in an SVG file and then exported as PNG, it will read it correctly. Will blank overwrite PNG metadata added by ImageMagick or Exiftool.Image Editors and Metadata BehaviorĬurrently, the most convenient tools (aka, the ones I use), and their status on JPG Exif and PNG metadata (XMP): OSX Preview In SVG this is a Dublin Core standard, and in PNG the same is generally available. When looking at a file with a tool, generally a few different bits and bobs are present. For JPG there is EXIF, but for PNG or SVG there are other standards, as in PNG does not have EXIF. Turns out there is more than one way to stuff a keyword. ![]() Generally things start with or result in various formats, including: It would be best if metadata could be added, modified at each stage of editing, and by default would be preserved on copy, export, format changes, compression, etc.
0 Comments
Leave a Reply. |