Why is Emby scan overriding settings?

[nospotify 184]

Emby seems to be downloading Musicbrainz info and overriding the embedded metadata tags in individual music files, even though literally no metadata downloaders are enabled. Here are the library settings:

 

Here is what is embedded in the files:

But even after completely moving to a differently-named library directory (renamed "Jarrett, Keith" parent directory to "Keith Jarrett" and did full music library scan), and even deleting the .nfo album info file before doing a new library scan, the embedded date (1972) was then overridden by an invisible, unwanted Musicbrainz data download of a 'release group' which created an overriding album date:  

Why is this happening and how can it be stopped, so manually entered metadata is displayed and used and MusicBrainz isn't consulted when nowhere was that requested in any visible Emby library settings? Even manually editng .nfo file gets overridden when a new scan is done. Server log is also attached.

 

embyserver.txt

Edited February 5 by nospotify

[nospotify 184]

@LukeIt seems to be overwriting the album year, but not the year of any individual track. I thought y'all had fixed the problem of external data sources superceding internal metadata, and in this case it's happening even when there are literally no visible external metadata sources selected. The example here is an album recorded in 1972 and released in 2012, and I'd like the year to sort and display as 1972. How can this be fixed? 

Edited February 7 by nospotify

[Luke 42077]

HI, that's odd. Are you sure you didn't uncheck those boxes after the data had already been downlaoded?

[nospotify 184]

51 minutes ago, Luke said:

HI, that's odd. Are you sure you didn't uncheck those boxes after the data had already been downlaoded?

Yes, I'm absolutely certain. I attached the log file above. I have repeated this multiple times. There is a problem with the way Emby server is behaving. And judging from the nfo file which I included a screenshot of, somehow Emby is grabbing this "releasegroup," even though musicbrainz was turned off entirely as a metadata source. Could you investigate?

[nospotify 184]

OK, @Luke here's a clean, simpler demo of the problem. I rotated log and then did this:

- turned off ALL metadata fetchers and downloaders

- confirmed that the album "Sleeper: Tokyo 1979" isn't in the Music Library (see images below with directory listing and sample metadata showing that year and release year are both "1979.")

- moved the directory, which contained only the music files and a cover image, into the correct artist Music Library directory

- did Music Library scan

- opened the newly added album and see that the metadata year is now listed throughout as "2012," and - despite all metadata retrievers being turned off - there are multiple Music Brainz data fields added to the album metadata and the individual music files metadata. See all images below (carefully named so you know what's what), including an image of the new Emby-created nfo file. Emby log also attached. Please figure out why: 

a. MusicBrainz is being contacted and retrieved from, even when all Library settings for metadata retrieval are OFF

b. why that retrieved MusicBrainz data is overriding the embedded metadata for the album (though apparently not for the individual music files)

What's going on and how can it be fixed?

 

embyserver.txt

Edited February 8 by nospotify

[Neminem 1518]

What info is in you mp3 files if you use mp3tag ?

Edited February 8 by Neminem

[nospotify 184]

Here's what is in MP3Tag:

 

[Neminem 1518]

And the extended tag

Right click and select

Edited February 8 by Neminem

[nospotify 184]

What's that? How to view in MP3Tag?

[Neminem 1518]

Right click track and it should be in the list.

[nospotify 184]

Aha! Interesting. So I do see MusicBrainz fields in the extended tags. BUT when I remove them all in every single track (including the ACOUSTID_ID Picard tag - image attached), delete the .nfo file, rescan the album folder and have it update all metadata using the Music Library settings (i.e. no external metadata sources), Emby still is displaying MusiBrainz releaseid info - for the album only. Again, this is after deleting the .nfo and doing a full scan/metadata refresh, with only mp3 files that have had all extneded tags cleansed of all MusicBrainz fields. Any other ideas @Neminemor @Luke?

[nospotify 184]

Additional data: individual tracks seem to all display correct metadata now in Emby, but the Album still displays the spurious-and-deleted-from-every-track MusicBrainz release id and wrong album date. Emby's "date added" is correct for individual tracks (a few minutes ago) but not for the album, too, which shows an earlier time (an hour ago), even though I have done the full Emby dance (move album directory elsewhere, scan, RENAME album directory(!), move back into Music Library folder, rescan Music Library).

Why is Emby still retaining outdated/deleted album-level data (and generating a brand new .nfo file upon import which contains incorrect date and spurious MusicBrainz releaseid), even though it's importing and displaying the individual music files correctly?

[Neminem 1518]

I wonder if this factors in.

[nospotify 184]

So two questions for @Luke:

- is/shouldn't Emby be using the plain embedded "year" field?

- why is Emby not reflecting actual import date/time at the album level?