Thanks for reporting! I've fixed the issue which was introduced yesterday with v3.16c with Mp3tag v3.16d.