https://blog.lazy-evaluation.net/deContents © 2025 <a href="mailto:dzu@member.fsf.org">Detlev Zundel</a> Sat, 08 Mar 2025 11:07:56 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://blog.lazy-evaluation.net/de/posts/linux/gthumb-tags.html?pk_campaign=feedDetlev Zundel<div><div style="text-align:center" class="imageblock" id="org4b3e01f"> <div id="org9f88832" class="figure"> <p><img src="https://blog.lazy-evaluation.net/de/images/exif-info-camera-image-playback.thumbnail.jpg" alt="exif-info-camera-image-playback.thumbnail.jpg" title="Virtual Machine Manager Logo" align="middle" width="250"> </p> </div> </div> <p> I guess most people have their own way of organizing lots of digital images efficiently. Most of them probably use databases for organization even though there are standardized ways to put metadata into the image files themselves. This blog post will detail my approach based on manipulating only the image files themselves rather than putting a database "on top", or other abstractions external to the files themselves. </p> <p> The <a href="https://wiki.gnome.org/Apps/Gthumb">GThumb</a> application from the GNOME Project is my preferred tool to organize digital images. Up until I wanted to work only on subsets of the original images, the standard functionality was good enough for my very amateurish needs. In the previous years we used to manually copy individual files into separate directories for different further processing. Such a procedure leaves a lot of duplicate files behind and does not record the selection process in the original files themselves. After cleaning up the left behinds from those previous years I set out to establish a better procedure this time. The aim was to enable an easy process to select pictures relevant for different groups of persons all the while recording the process in the original image files. The tagged files are then collected with a short script into individual directories for further processing, e.g. for creating a picture book out of them. </p> <p><a href="https://blog.lazy-evaluation.net/de/posts/linux/gthumb-tags.html?pk_campaign=feed">Weiterlesen…</a> (9 min verbleiben zum Lesen)</p></div>https://blog.lazy-evaluation.net/de/posts/linux/gthumb-tags.htmlThu, 23 Nov 2023 22:54:56 GMThttps://blog.lazy-evaluation.net/de/posts/metadata-ffmpeg.html?pk_campaign=feedDetlev Zundel<div><div style="text-align:center" class="imageblock" id="org7047db6"> <div id="org45b1055" class="figure"> <p><img src="https://blog.lazy-evaluation.net/de/images/ffmpeg-logo.png" alt="ffmpeg-logo.png" title="Big lock" align="middle" width="150"> </p> </div> </div> <p> The <a href="https://www.ffmpeg.org/">FFmpeg</a> suite of multimedia tools is a very powerful toolkit, but sometimes its default behavior just plain surprises me. While I am totally impressed by its capability to stabilize videos taken by my mobile phone, it took me some time to realize that this processing step lost all the metadata. Of course, I did not expect this, and it is trivial to fix the script, but first you need to be aware that the problem even exists. </p> <p><a href="https://blog.lazy-evaluation.net/de/posts/metadata-ffmpeg.html?pk_campaign=feed">Weiterlesen…</a> (5 min verbleiben zum Lesen)</p></div>https://blog.lazy-evaluation.net/de/posts/metadata-ffmpeg.htmlSat, 11 Nov 2023 14:54:58 GMT