This is the same case for writing tags too. In the logic of FFmpeg, everything is considered as a stream, some file comes as an input stream, some filters are applied, and then one output is produced. It is trickier to write tags than just reading them. Make sure to get rid of it if your program consumes both stdout and stderr together by default. Note that both ffmpeg and ffprobe prints version number, compile info of the program itself and metadata of the file to stderr. See ffprobe documentations for more options. You can choose whichever format that fits your need better. Omitting this option will result in an output with no useful data.īesides JSON, ffprobe also produce output in CSV, flat key-value pairs, INI, and XML syntax. The option -show_format adds the section "format" to the output, which has the metadata of the file format as long as the tags. "format_long_name": "MP2/3 (MPEG audio layer 2/3)", ffprobe in this case can produce an output in JSON which is more program-friendly.įfprobe -show_format -print_format json music.mp3 To read tags from a music file, we actually need to use ffprobe instead of ffmpeg. The way of doing so might be a little verbose as everything have to fit into the command line interface with other components. Until recently while I was seeking for a solution to read and write tags of (potentially) all music formats 1 I only have MP3, FLAC, AIFF and M4A in my library, so that’s kinda all for me., and I encountered FFmpeg, the Swiss Army Knife of media processing.įFmpeg has always been my go-to solution for processing media programmatically or in batch, and I have recently found the way to write into the tags of music files using it. One of the reason being I am rather particular about having a nicely organised library with all tag data aligned to the same format. In both my previous and recent projects, I have been working with tags (metadata) of music files.
This article is last updated over 3 years ago, the information mentioned may be changed or developed.
0 kommentar(er)
