Open ghjimmy opened 1 year ago
Thanks for filing an issue! Please note that this project is only passively maintained, so your best bet for getting an issue resolved is through a pull request that is easy to verify! Please read this for more information.
This is a known incompatibility. As an alternative, you can use AtomicParsley to added custom tags using --rDNSatom
. However, you'll need to build AP with the fix in PR #63, which fixes a problem in parsing .--rDNSatom
values. The PR is a bit messy because the submitter didn't squash commits, but the end result appears to to work.
The issue is a 3rd party program (Topaz Video AI) adding these tags via ffmpeg, and then making the file incompatible for AtomicParsley. Currently, I make a "best guess" at what the tags are from parsing ffprobe and re-add the compatible ones with "AtomicParsley --metaEnema --artwork REMOVE_ALL" but I was hoping there was a workaround in AtomicParsley to parse them correct. I'll look at the PR you mentioned to preserve the extra tags when I write them in a more compatible format. Currently, I just write them as extended attributes to the file itself, just so I can preserve them.
The use of -movflags use_metadata_tags
triggers ffmpeg to write the tags in a form that is unreadable for Windows Explorer, Mp3Tag, Kid3, AtomicParsley and other applications, so no shortcut that I could see. Also, there are some differences in how applications handle reverse DNS tags with multiple values, so some care is required if you're writing tags in different applications.
Looks like if a non standard tag is added by, for example, ffmpeg, AtomicParsley reports on all of the tokes, but called them the empty string. If the example below I've removed the extraneous ffprobe output:
Now add an extra tag to the file and re-run AtomicParsley and ffprobe again