Thanks for the reply. I typically do not store MBID tags in files as I do not use Picard for tagging purposes. I like Picard for this because I can open my file(s)/folder and load up the MB release (for example) by its ID and see them side by side. Then I can match up my files to the MB listing on the right and submit. Because this is a GUI, I like to see what is selected and done, because a GUI like Acoustid Fingerprinter is ambiguous to me… what is it exactly doing, what files is it (or not) submitting, what release did it see, etc. It is just a pick a group and send it, errors (if there) and all. In Picard, I can see how my recordings match up, make sure durations are a match, etc before submitting.
BTW- I use Ubuntu, currently Ubuntu 17.10 MATE. I am sure our tools are close enough, but I wanted to make the difference known.
EDIT: To clarify, I do not physically tag files with Picard, but aside from submitting with it, I do use it (and the MB web UI) to lookup releases, recordings, etc. It is extremely useful, as well as the current scan button in Picard to help identify unknown files of recordings. I can get quite particular on tags as of late… to the point of often manual cleaning with tools like AtomicParsley as most GUI tag editors cannot see ALL tags, just those it can recognize… like Picard where it only shows the tags it is set to and the rest are invisible from within the GUI.