2020-12-22, 04:33
Recently I noticed tmm fails to update video bitrate information for some matroska files when running "update media files" command.
It turned out that a lot of matroska files simply don't contain such metadata depending how they were encoded.
For instance, see this:
https://gitlab.com/mbunkus/mkvtoolnix/-/...trate-lost
The bug with tmm is that when a new file lacks such metadata, it retains the info from previous file in the database even though the updated mediainfo.xml file no longer contains the information.
For missing audio bitrate, it properly leaves it empty both for the db and the xml file.
The only solution to update I found is to remove and re-import the movie, then it shows "overall bitrate" of the new matroska file as video bitrate (of course it's inaccurate since it's a combined bitrate of all audio + video tracks, but it's still better than showing the previous file's. Probably the user needs to remux such files with latest mkv encoding tools to add accurate bitrate per track metadata).
It turned out that a lot of matroska files simply don't contain such metadata depending how they were encoded.
For instance, see this:
https://gitlab.com/mbunkus/mkvtoolnix/-/...trate-lost
The bug with tmm is that when a new file lacks such metadata, it retains the info from previous file in the database even though the updated mediainfo.xml file no longer contains the information.
For missing audio bitrate, it properly leaves it empty both for the db and the xml file.
The only solution to update I found is to remove and re-import the movie, then it shows "overall bitrate" of the new matroska file as video bitrate (of course it's inaccurate since it's a combined bitrate of all audio + video tracks, but it's still better than showing the previous file's. Probably the user needs to remux such files with latest mkv encoding tools to add accurate bitrate per track metadata).