Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
What is the purpose of your issue?
The commandline option
--metadata-from-titleallows adding various tags to the metadata of the file, however it appears to ignore the tags actually found by the option if they're not in this list of tags.As an example, see the command below:
Here we have used the regular expression
.*prod[.]? +(?P<composer>[a-z]+).*to select the composer of the music file from the filename, and as seen from[fromtitle] parsed composer: rusherit correctly used this to find the composer.However if we run the command
exiftool nirvana\ \(prod.\ rusher\)-382186547.mp3 | grep Composerwe will find that it produces no output, since the tag was not actually added to the file.We can also see that this is the case from the ffmpeg commandline on the last line of the output, where the composer is absent.
If we add
-metadata composer=rusherto the commandline and run it manually, we will find that it is successfully added to the file:This issue is not present on the known tags. An example using the tag artist is shown below:
The issue must be that the tag
composeris ignored for some reason. I assume this is because somewhere it loops through the aforementioned list of tags and only adds the ones it knows to theffmpegcommandline, or it is otherwise filtered on the way there.My main proposal is that unknown tags in the
--metadata-from-titleoption should be added to theffmpegcommand, since there are surely other tags thancomposerwith this issue, but I suppose that addingcomposerto the list of known tags would also be a solution.