Retrieve info from existing .NFO files

[EduardoSantos 40]

Is there something that can be done for Emby to read existing .NFO files?

Their info was already on Emby database but vanished after update to 4.6.

Library is already configured to read and write .NFO files.

 

Edited May 23, 2021 by EduardoSantos

[Luke 42078]

Hi, can you please be more specific? Emby supports nfo files.

[EduardoSantos 40]

There were music albums and .NFO files containing the same information already inside Emby database.

After installing 4.6 Emby database was updated/upgraded and vanished textual information which is still stored on .NFO files.

So while Emby shows no textual info to a given music album, the .NFO file on the path still retains it.

I would like to make Emby to retrieve it from the .NFO file.

[roaku 842]

I found that my TV specials were missing data from their nfo files after the upgrade, specifically the fields related to placing the specials within seasons. More data may have been missing, but this is what I noticed.

Refreshing metadata at the season special level with the fill missing option selected fixed that for me.

Edited May 23, 2021 by roaku

[EduardoSantos 40]

That has already been tried. My music library is not linked to any information service.

Emby ignored the existing .NFO file on the music album path.  

1 minute ago, roaku said:

I found that my TV specials were missing data from their nfo files after the upgrade, specifically the fields related to placing the specials within seasons. More data may have been missing, but this is what I noticed.

Refreshing metadata with the fill missing option selected fixed that for me.

 

[roaku 842]

7 minutes ago, EduardoSantos said:

That has already been tried. My music library is not linked to any information service.

Emby ignored the existing .NFO file on the music album path.  

 

I don't know if my approach will work for your case, but nfos are considered an information service by the system.

[EduardoSantos 40]

Just now, roaku said:

I don't know if my approach will work for your case, but nfos are considered an information service by the system.

Well, I tried to update and there was no update though the .NFO file was there.

[Happy2Play 9780]

Pretty sure here is your answer.

 

[EduardoSantos 40]

1 minute ago, Happy2Play said:

Pretty sure here is your answer.

 

As suggested by that thread, my database already is configured to read and write .NFO files.

Scan does nothing.

[EduardoSantos 40]

Already tried to move the album folder off the library, scan database to delete it and move it back for Emby to read from .NFO.

When it returns to Emby, .NFO is cleaned and textual info is missed.

[Happy2Play 9780]

Just now, EduardoSantos said:

As suggested by that thread, my database already is configured to read and write .NFO files.

Scan does nothing.

 

1 minute ago, EduardoSantos said:

Already tried to move the album folder off the library, scan database to delete it and move it back for Emby to read from .NFO.

When it returns to Emby, .NFO is cleaned and textual info is missed.

Luke says album.nfo are not read at this time (per that post).  

[EduardoSantos 40]

So there's no thing that can be done. Thousands of album textual info are lost.

 

[Carlo 4561]

Album info is now read specifically from the tags in the album tracks. In 4.6 it's now 100% tag driven. Hopefully this does not change in the future as it makes identifying problems very easy.

It probably should have been like this from day 1, but wasn't. It is now, so the answer to almost any music related question is what do your tags show. Emby should now build views based only on your tags and nothing else.

[roaku 842]

I thought I saw a 'use nfo' option when I set up my music library after upgrading to 4.6.

I didn't check it because I have no need for it for music... But still, what does that option do in 4.6?

[Happy2Play 9780]

3 minutes ago, roaku said:

I thought I saw a 'use nfo' option when I set up my music library after upgrading to 4.6.

I didn't check it because I have no need for it for music... But still, what does that option do in 4.6?

There is.  @Lukewhat nfo is being read via Music library nfo reader?

[Luke 42078]

It currently writes only. We can bring back reading album nfo. We just had so many other things to do with 4.6 and ran out of time.

[Happy2Play 9780]

Just now, Luke said:

It currently writes only. We can bring back reading album nfo. We just had so many other things to do with 4.6 and ran out of time.

Was just wonder as the nfo reader is shown on the library.

[BlueMax1916 3]

Hi,

 

what he means is this information in the overview (Übersicht) text field:

 

 

It is empty and will not be filled by any MP3 tags. As album.nfo is not read it will not be filled by that one either.

 

Cheers

Blue Max

 

[Carlo 4561]

2 minutes ago, Luke said:

It currently writes only. We can bring back reading album nfo. We just had so many other things to do with 4.6 and ran out of time.

So what will happen if the NFO has different information than the track tagged info?
If we start reading in NFO files for music won't that cause another round of issues from pre 4.6 days?

[Happy2Play 9780]

1 minute ago, cayars said:

So what will happen if the NFO has different information than the track tagged info?
If we start reading in NFO files for music won't that cause another round of issues from pre 4.6 days?

At the same time user should not be dependent on online providers for Album Overviews.

[Carlo 4561]

I'm not against NFO reading/processing but I think we need to know up front how they would be used and what "tags" info they would read.  If not done correctly I could see this as big mess with conflicting info between tags and nfo elements.

[Happy2Play 9780]

Just now, cayars said:

I'm not against NFO reading/processing but I think we need to know up front how they would be used and what "tags" info they would read.  If not done correctly I could see this as big mess with conflicting info between tags and nfo elements.

True and the UI needs to disable all none editable field, but that will not stop someone from editing the nfo directly.  Users should know that embedded tags will override all customization via nfo files except fields that do not exist in tags.

[BlueMax1916 3]

Hi,

I do not use online sources either. Everything is included in .nfo files locally. For music of course track information and cover art is tagged in the MP and FLAC files I have. But for example background information about an album is not stored in the MP3 tags but in .nfo files.

Example album.nfo:

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<album>
    <musicBrainzReleaseGroupID>d3bc1a64-7561-3787-b680-0003aa50f8f1</musicBrainzReleaseGroupID>
    <musicBrainzAlbumID>64439f14-f4e8-3c88-b455-e921ad26d262</musicBrainzAlbumID>
    <title>Back in Black (2003 Remaster)</title>
    <artist>AC/DC</artist>
    <genre>Hard Rock</genre>
    <review>Back in Black (engl. für „Zurück in Schwarz“) ist das sechste international veröffentlichte Studioalbum der australischen Hard-Rock-Band AC/DC. Es wurde am 25. Juli 1980 veröffentlicht und war das erste Album mit dem Sänger Brian Johnson, der den fünf Monate zuvor verstorbenen Bon Scott ersetzte. Das Album widmete die Band ihrem verstorbenen ehemaligen Leadsänger. Das Album ist mit über 50 Millionen verkauften Tonträgern nach Michael Jacksons Thriller und Pink Floyds The Dark Side of the Moon das drittmeistverkaufte Album der Welt sowie das erfolgreichste Hardrockalbum bislang.</review>
    <label>Epic</label>
    <releasedate>2003-10-14</releasedate>
    <year>1980</year>
    <style>Rock/Pop</style>
    <mood>Energetic</mood>
</album>

 

For me this background information has been deleted also after update to 4.6 from every album entry in Emby. For the time being I can live with that as Luke said he will bring back reading of album.nfo.

 

Cheers

Blue Max

Edited May 23, 2021 by BlueMax1916

[Happy2Play 9780]

Yes do the forced Refresh of all Music to accommodate database changes.  Since nfo reading is currently not happening your information currently does not exist in the database.

[EduardoSantos 40]

So let me see if I got this straight:

By updating to the new 4.6 version every Emby user will lose all album music information no matter what he does.

Is that correct?