jExifToolGUI VS FFmpeg

Here is a GUI tool to manipulate Exif data, which is the most common form of metadata.

Does anyone have any recommendations for software that can create metadata, especially keywords? I also need recommendations for software that is able to search through all the metadata and present files based on keywords or any other rules that make it easy to locate files. Currently looking at jEXIFToolGUI, I prefer the GUI because many different files (especially images) require me to be able to see a preview and using a command line tool would take a massive amount of time to create the metadata

commandline exiftool if it is ok for you, probably fastes way how to transfer Cretated to Original date for lot of files, or jExifToolGUI if you need gui app - https://hvdwolf.github.io/jExifToolGUI/

To just browse and tag, Adobe Bridge is free and will to correctly add metadata following the IPTC Photo Metadata Standard. Also free and uses exiftool on the backend is jExifToolGUI.

There may be GUIs for it, the search words would be exiftool and gui. Here is jExifToolGui. It seems to be as pretty as its name; I have no experience with it.

mat is not the only option. Most of the time I use exiftool, but on images I also use Imagemagick. I recently found an interesting GUI front-end for exiftool called jExifToolGUI - it is available as an AppImage, so you do not have to worry about dependencies and removing it is as simple as deleting the file. https://github.com/hvdwolf/jExifToolGUI/releases

You will have to add/alter the metadata of the image. One rather complicated way is through exiftool (GUI https://github.com/hvdwolf/jExifToolGUI/releases), changing values for InitialViewHeadingDegrees IitialViewPitchDegrees InitialViewRollDegrees in GPano tab

There's only one exiftool program, located at exiftool.org, though there are some programs that use exiftool on the backend, such as hvdwolf's jExifToolGUI.

FFmpeg (https://ffmpeg.org/)

GPL2

Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?

IANAL, apologies if I miss understand license requirements.

https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file

This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...

The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.

If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.

I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".

You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.

There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.

To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.