And this container type normally gets derived from the container filename suffix (ending): in particular. Ffmpeg supports different meta data elements, based on the type of container.Please note that you must use the ffmpeg meta data keys from the second column in the table below as the metadata keys in Kdenlive’s Project Metadata dialog!.So, variance galore!īut now for the real meat: here come the available meta data elements that ffmpeg supports. Luckily, you don’t need to dive into the source anymore.įinally, please note that other container formats, such as Matroska (.mkv) or * cough* Audio Video Interleave (.avi), support yet other sets of meta data elements.
ITUNES MP4 METADATA EDITOR WINDOWS CODE
At some point, I’ve resorted to reading the source code in order to find out which so-called MP4 atoms actually are supported and through which element names (the magic happens inside mov_write_ilst_tag() in moveenc.c). As Kdenlive uses ffmpeg for encoding, one would think that there’s plenty of information – unfortunately, it’s not, and the scarce information is sometimes plainly wrong. Of course, this may also apply to this Toolbox article, but I’ve taken much effort to cross-check things in real life. Unfortunately, information about what meta data can be used in which situation is rather scarce, sometimes outdated, and sometimes plainly wrong. We will come back to this difference in a second. Then, there is Apple iTunes, and that brings in a lot of meta data, and even changes the allowed set from time to time. The older, standard MP4 set is rather limited in what additional meta data can be used. Unfortunately, there are competing sets of meta data when working with MP4 containers.
0 kommentar(er)
