Jump to content

Fixing "9999" albums (with nfo files)


mtjj

Recommended Posts

So, recently migrated from a windows setup to a synology NAS, I just copied everything from my previous setup (a bunch of external HDDs) to the NAS and setup a new emby instance pointing at the new folders, as I didn't really care about copying across play history, etc. All media has nfo files saved, so the process went extremely smoothly.

 

But now I want to clean up stuff I never got around to fixing before. One thing I need to fix is a bunch of albums with year = 9999. I know this is a bug that is since fixed, but I don't know how best to fix the albums that were set with the wrong date. Reading back past threads, advice is to "manually edit affected titles", but isn't there an easier way? Unfortunately the bugged version coincided with my doing a mass clean/ import, so I have hundreds of albums with the wrong date. (That's why I've avoided fixing the issue until now...)

 

I don't have any custom metadata, so I thought I could force a refresh, but this didn't work.  I selected a test album and tried "refresh all metadata" with the option set to "replace all metadata", but although I validated that the refresh happened, the album date hasn't changed. I looked in the folder on the NAS and the nfo file is updated /overwritten, but still contains the wrong date (9999-12-31). This is verson 4.0.3.0.

 

I still have the old server instance running (windows, 4.0.3.0) with a parallel library on external HDDs, so I tried the same process there, and it worked. So I don't know if this is a known synology issue, a sign that the bug that was fixed on windows was not fixed here, or something totally different.

 

Can I perhaps delete all nfo files on the NAS music library and force a re-scan? Would that work? I know this will take a long time so I thought I would ask before doing it. Or I suppose I could rescan all the music library on the windows server, correcting the nfo files, then delete from the NAS and re-copy, but that seems like even more of a hassle.

Link to comment
Share on other sites

... a sensible suggestion, thanks. But now I'm even more confused :)

 

I tried deleting an nfo file, and rescanned (from library "scan all libraries"). Waited... until it completed, went and looked at the album folder in explorer, and no nfo file was created. (I also tried this with a movie, and similarly, no nfo file created.)

 

I navigated to the album in emby, tried "refresh metadata" with "replace all metadata selected". This regenerated the nfo file, but again with the date "9999-12-31"

 

Any advice here?

Link to comment
Share on other sites

PenkethBoy

... a sensible suggestion, thanks. But now I'm even more confused :)

 

I tried deleting an nfo file, and rescanned (from library "scan all libraries"). Waited... until it completed, went and looked at the album folder in explorer, and no nfo file was created. (I also tried this with a movie, and similarly, no nfo file created.)

 

I navigated to the album in emby, tried "refresh metadata" with "replace all metadata selected". This regenerated the nfo file, but again with the date "9999-12-31"

 

Any advice here?

Yes a scan will not recreate a nfo for an existing item as it would for a new item 

 

As the refresh with replace all metadata - saved the 9999 date to the nfo - then the 9999 date is in the db and you have a couple of options

 

1) remove the affected albums from emby - do a full scan so the db entries are deleted - re add the album WITHOUT the nfo - and this will get emby to go and download "new" metadata - hopefully with the correct date

 

2) Manually edit albums individually - a PIA if you have more than a few to correct

 

3) This could be corrected in the db directly - but not for the average user to try as potential to get it wrong is high

 

Simplest would be 1.

Link to comment
Share on other sites

Try correcting the date manually.

 

This is exactly what I am trying to avoid - there are a *lot* of albums with the wrong date, so I am looking for any alternative

 

Yes a scan will not recreate a nfo for an existing item as it would for a new item 

 

As the refresh with replace all metadata - saved the 9999 date to the nfo - then the 9999 date is in the db and you have a couple of options

 

1) remove the affected albums from emby - do a full scan so the db entries are deleted - re add the album WITHOUT the nfo - and this will get emby to go and download "new" metadata - hopefully with the correct date

 

2) Manually edit albums individually - a PIA if you have more than a few to correct

 

3) This could be corrected in the db directly - but not for the average user to try as potential to get it wrong is high

 

Simplest would be 1.

 

Yeah, for the music, I think I give up trying to be clever and will just go with 1. I will remove the library, delete all the nfo's, then rescan the entire library. This is slow but at least won't require manual action on my part.

 

But actually I still have one question :-)

 

Previously, (the instance of Emby server running on windows), I would sometimes update media with a newer version (DVD -> bluray, for example). To do this I would navigate to the folder, delete the old media file and the nfo file, and move in the newer version, with the same name. The nfo would be automatically regenerated. This doesn't seem to work any more on the synology. I just tried this with a movie and the new file is sitting there with no nfo. But I know it used to work on the windows instance. Is there any reason why the behaviour should be different on a NAS?

Link to comment
Share on other sites

PenkethBoy

Does the Real time monitor work on your syno - and is it enabled in the Library settings

 

Also did you give emby enough time to see the removal (delete old record in db) before you copied in the new version - by default the RTM has a 60 second delay - so say 75 seconds - before the new file arrives?

 

Another reason could be that a library scan was taking place - as this disables the RTM during the Scan - so if you did the swap at that time the server would not see the change

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...