Back to Blog
Digikam face metadata5/29/2023 ![]() ![]() Roadmap and Releases Plan including all GoSC-2012 works ![]() $>git checkout master git pull -rebase git checkout 3.0.0 git pull git merge master To do it, see below as example how to sync digiKam "3.0.0" branch tracking "remotes/origin/development/3.0.0" from KDE git repository: A development branch must be sync with git/master periodically. During GoSC2012 coding time, git/master will still the stable implementation receiving important fixes.To create remote working branches in KDE git repository, please look on this tutorial from KDE TechBase.Repositories Branching and Dates Branches Creation and Maintenance Students and mentors will use digikam-soc-devel at kde dot org mailing-list to coordinate projects. Import/Export tools To Web Services to factorize In order to branch Kipi-plugins to 3.0.0, and to optimize time loading of KIPI host applications at startup, some tools need to be binary factored to the same plugin. Summary : Right now the processing of items in BQM take place in serial fashion, the goal of this project is to allow processing of items from queue in parallel, using multicore CPU.įull size screenshot from Flickr Extra projects relevant of digiKam Software Compilation 3.0.0 Kipi-plugins Factoring Summary.Parallelization of code into Batch Queue manager Working on : Libkipi-2.0.0 Git branch, digiKam 3.0.0 branch and Kipi-plugins 3.0.0 Git branchįull size screenshot from Flickr digiKam Summer of KDE 2012 Projects list Wallpaper pluginįull size screenshot from Flickr Extending Presentation View using Kipi plugins.Working on : A dedicated Svn branch for Exiv2, and digiKam 3.0.0 git branches.įull size screenshot from Flickr Porting Libkipi and KIPI-Plugins to KDE XML-GUI.Working on : libkface 3.0.0 and digiKam 3.0.0 Git branchesįull size screenshot from Flickr Video Metadata Support.Working on : Kipi-plugins 3.0.0 Git branchįull size screenshot from Flickr Camera User Interface Revampįull size screenshot from Flickr Face Recognition.Digikam/GSoC2012/LibKipi_and_KipiPlugin_restructuring_using_KDE_XML_GUI_API.5.2 Roadmap and Releases Plan including all GoSC-2012 worksĭigiKam Google Summer of Code 2012 Projects list.3.1.2 Import/Export tools To Web Services to factorize.3 Extra projects relevant of digiKam Software Compilation 3.0.0.2.4 Parallelization of code into Batch Queue manager.2.3 Extending Presentation View using Kipi plugins.2 digiKam Summer of KDE 2012 Projects list.1.7 Porting Libkipi and KIPI-Plugins to KDE XML-GUI.1 digiKam Google Summer of Code 2012 Projects list.This allows the regions to be resistant to changes in size, as long as no cropping takes place, and rotation, as long as the Orientation of the image is properly updated.įor further info, see the MWG Guidelines for Handling Image Metadata pdf on the subject (pages 51-56). Also, it is assumed that the location is relative to the top left of the image as indicated by the Orientation tag embedded in the image. This means that they will correctly locate the face as long as the image has not been cropped or flipped. The way MWG regions (face tags) work is X/Y coordinates and the height/width of the region are saved as number from 0 to 1 and used as a percent of the images actual height/width. Add -overwrite_original to suppress the creation of backup files. If the names are different, then the commands would have to be altered a bit but it should still be doable. If the filenames are the same, then you could do it in batch with a command like this: exiftool -TagsFromFile /Path/to/Smalls/%F -RegionInfo /Path/to/Larges The basic command to copy would be: exiftool -TagsFromFile SmallFile -RegionInfo LargeImage As long as none of the smaller set of images have been cropped and only are resized, you should be able to do it with Exiftool.įrom my brief search, it looks like digikam saves the faces tags to the MWG XMP tags. ![]()
0 Comments
Read More
Leave a Reply. |