Ising itunes for mp4 metadata editor windows code#
First, and foremost, the ffmpeg source code for reference, and moveenc.c in particular.The following references give some more background information on ffmpeg and meta data in. Not available to us users, as it gets automatically set by ffmpeg itself this is set to the libavformat version string. If 1, then this video file is part of a compilation. Optional lyrics for badly sung sing-along… ( String) The season number, in the range of 0 to 255 only. The valid range is limited to 0 to 255 only, so this doesn’t support all those endless telenovas, it seems… ( Int8) It allows numerical sorting of episode names that are strings, but not (necessarily) numbers. This element is for sorting only, but never displayed. If necessary, use the separate, yet optional episode number element for correct sorting.
( String)Įither the episode name or episode number, for display. In contrast to the album elment, grouping happens inside (that is, below) the album level. The name of a group of videos somehow belonging together. ( String)Ī synopsis, a longer description of this video. Same as before, but encoded in a separate element. This will probably a comment set by the audience, not at the time of production. ( String)Ī (short) comment on your video. For a synopsis, please see the separate element instead. ( String)Ī (content) description of this video. This element can also be left out or be the same name as the artist. The name of the album artist: this may be a guest artist or a featured artist. Please don’t use this element for the composer, as there is a dedicated element especially for the composer, see below. Please note that the ffmpeg documentation is totally wrong here, there is no key named year, but only date. 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. 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)
