Jump to content

Movie Metadata Gone, Will Not Fetch Metadata


Recommended Posts

Posted

I don't know if this is the correct sub-forum to post in, I'm running on Unraid.  Since the update, all of my movie metadata has gone (which I've come to see should have been expected), but it will not fetch new metadata to replace what was lost.  It will take forever to scan every time I try to scan for it, but it just doesn't find/pull anything down?  Please help, this is very irritating.

 

Thanks

tymanthius
Posted

I'm also seeing similar. I'm now allowing my server to finish a scan (moving super slow on the last 5% - .01 in 3 hours).  

 

But if anyone has any insight, I'd love to hear it.

Posted

I've not only finished my scan, I've run it multiple times.  I've also tried a fresh install and scanned that, and it still won't find the metadata.

Posted

@@DarkZim

I am also facing the issue of the whole movie library being pruned on first library scan after 3.x -> 4.x migration.

Where was it mentioned that this is expected behavior? Or do you just mean that you already heard about the problem?

 

For testing purposes I did the migration from 3.x to 4.x about 5 or 6 times now, trying various settings/constellations. Removing all addons, disabling all scheduled tasks and disabling the download of subtitles prior to updating helps to speed up the first initial 4.x library scan by a lot.

That's no solution to losing all manually edited metadata and having to re-identify all manually identified movies due to the db pruning, though.

 

Still hoping this migration path is a bug rather than expected behavior and I won't have to put in a lot of busy work to get the benefits of 4.x..

Posted

I have seen in the forums that having everything deleted is the expected behavior of the update.  I don't have a problem with that, all my my data was automatic through the scraper.  The issue is that now it won't download new metadata to replace what was removed by the update.

Posted

It's not expected behavior. Only in certain situations depending on your settings and libraries.

 

I apologize for the disruption. Can you please provide an emby server log from the library scan following the upgrade? Thanks.

  • Like 1
Posted (edited)

Oh i  would like the answer.

My help to unistall all plugins?

Im in a real mess.

Days of worked ar fucked up. At leat i got a full backup of 3.5.3.0.

I need an solutions too or i must quit emby

 

Edit: I did everything back to 3.5.3.0. Works like charm. Deleted all plugins. Restart. Stii fine.

Installed emb-server4.0.0.2 amd64 (debian) . After migration, it still looked finde, I did a full media search. everything fucked up again! I may try it again an bevor media scan in 4.0.0.2 i delete the preinstalled plugins.

 

There musst be a sulutions. Else, aks für a liftetimepremier key. I wont need it anymore.

Edited by ottoii
Posted (edited)

I dont know which plugins makes the terror, but anyway nothgin helps. 24h roasted \o/

 

Sorry for my bad temper. I will wait for a nice solutionas as always. Thank you

Edited by ottoii
Posted

@@Luke

Here you go

 

@@DarkZim If you use the identify feature on one of the titles that did not get metadata, does that fill it in?

Posted

@@Luke

Yes, I can manually search and add metadata just fine, but the scan will not pull in anything.

Posted

We'll be getting an update out to resolve this. I apologize for the disruption.

Posted

Thank you very much for your time.

Will this update work from 3.5.3.0?

Posted

What I'm fixing is the regression in parsing the movie title and year from the file name. That will get the matching back to where it was before.

Posted

Still the same. My movies were locked? May thats the problem? How can i post log file withouth spoiling personal information? Or what can i do, to help you guys solve the problem?

Posted

Yes that could be the problem. Can you please give an example? Thanks.

Posted (edited)

-

Edited by ottoii
Posted (edited)

.

Edited by ottoii
Posted

I don't think there is a way to retain manually changed metadata that only resides in Emby's database (as in: not as .nfo with the files itself) when upgrading to 4.x.

At least with the current codebase.

See here.

 

Still hoping the devs have mercy on us manual metadata folk and implement a fix :)

  • Like 1
Posted

I unlocked the diffrent media librarys at 3.5.3.0 and did the update. I recoginezed, that you cant lock a whole library anymore at 4.0.1.0.

But all the movies in the library itself are locked. I did this to prevent chainging. I had wired behavior in the past with metadata from movies i had to manualy identify. So i lock all new movies after the media scan.

Why cant i have those locked for the update? I dont want the metainfos changed! That was quite some work to edit the metadate to my preferences. I dont want to loose it.

 

Edit: I deinstalled the plugin statistics. May this was the problem. I couldnt update statistics.

 

 

Method not found: 'System.Collections.Generic.IEnumerable`1 MediaBrowser.Controller.Library.IUserManager.get_Users()'.

at Statistics.ScheduledTasks.CalculateStatsTask.MediaBrowser.Model.Tasks.IScheduledTask.Execute(CancellationToken cancellationToken, IProgress`1 progress)

at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)

at Statistics.ScheduledTasks.CalculateStatsTask.MediaBrowser.Model.Tasks.IScheduledTask.Execute(CancellationToken cancellationToken, IProgress`1 progress)

at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.ExecuteInternal(TaskOptions options)

 

 

I will try now without the plugin. Will need some time for backup etc.

Thanks for forther help.

 

This is related to your statistics plugin. Either update or remove that.

Posted

I don't think there is a way to retain manually changed metadata that only resides in Emby's database (as in: not as .nfo with the files itself) when upgrading to 4.x.

At least with the current codebase.

See here.

 

Still hoping the devs have mercy on us manual metadata folk and implement a fix :)

 

I apologize for the disruption. We have at least resolved the fetching problem.

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...