Theodore 136 Posted June 17, 2017 Posted June 17, 2017 When importing new media I create the XML files in MetaBrowser then lock the data for import into Emby. Starting with the latest update to 3.2.20.0 the LockedData field is not being respected and the imported titles are coming in as completely unlocked then Emby's fetcher is overwriting all data I have put in when converting it to the NFO. This is a big problem as the data from Emby's fetcher is often very incomplete and is removing or overwriting data I am specifically making sure is included in the original file. For example, the most recent imports have included data in the "Sort title" field and when Emby imports it that field is now blank. When I create the original XML I make sure to have all cast listed from IMDB, but Emby's fetcher refreshes it, the cast can be cut drastically depending on whether someone has listed everyone or not on whatever site Emby pulls from. When parsing the XML into the NFO, the original data - including field and form locks - need to be respected. Thank you!
Happy2Play 9784 Posted June 17, 2017 Posted June 17, 2017 Do you have the updated XML plugin? You have to disable nfo creation and Emby will now only display what is in your XML file. If you want Emby to display additional information that only Emby gets it will be written to the database and no where else. Legacy Xml Metadata Updates Going forward, if you need support for Media Browser 2 legacy XML, please install the Xml Metadata plugin from the Emby plugin catalog. This includes xml metadata for movies and tv shows, as well as the metadata folder for episodes. https://emby.media/community/index.php?/blog/1/entry-379-emby-server-3220-released/
Theodore 136 Posted June 17, 2017 Author Posted June 17, 2017 I have no problem with the NFO file being default, but since MediaCenter Master and MetaBrowser don't create these and instead output everything as XML Emby still needs to parse this data accurately and correctly. Either that, or you need to make sure that it's fetchers are 100% accurate - such as scraping IMDB directly.
Happy2Play 9784 Posted June 17, 2017 Posted June 17, 2017 Well I know Emby will never scraper any site do to legal issue. And to use there API IMDB wants over $10,000. What information do you deem incorrect. I have seen no difference in TVDB and TMDB compared to IMDB, except for occassionally on some Series. And MCM has a option to Export NFO files( that may resolve your problem), it just requires xml do to it is MCM master metadata. So the question about locked metadata is are the tags correct in the xml (which I don't believe are). What is the lock tag in your xml? @@Luke Does the locked fields carry over from XML when imported into Emby. Either that, or you need to make sure that it's fetchers are 100% accurate This is a dream as both TVDB and TMDB are community driven so you can update both sites if you know the information is incorrect.
Theodore 136 Posted June 17, 2017 Author Posted June 17, 2017 This is from Power Rangers (2017) and This is from Benchwarmers (2006), both have far more actors listed that were in the original XML from IMDB than are found by by Emby. The LockData field is generated from MetaBrowser as "<LockData>True</LockData>". As for carrying over, prior to 3.2.20.0 it absolutely did carry over and it no longer does. As for MCM exporting NFO files, I'd love to know what that option is as I can't find it right now.
Happy2Play 9784 Posted June 17, 2017 Posted June 17, 2017 Since all the XML options moved to the plugin in 3.2.20.0 the tag may have been overlooked. As for MCM go to Application-Settings and Preferences-Metadata, you will see the setting for Kodi metadata. This also activate an additional Kodi tab once activated (Application-Settings and Preferences-Kodi/XMBC. This will add right click "export to other metadata formats" and in Tools "create external metadata for all".
Luke 42085 Posted June 17, 2017 Posted June 17, 2017 I have no problem with the NFO file being default, but since MediaCenter Master and MetaBrowser don't create these and instead output everything as XML Emby still needs to parse this data accurately and correctly. Either that, or you need to make sure that it's fetchers are 100% accurate - such as scraping IMDB directly. Actually metabrowser supports nfo, just configure it to save in Kodi/Xbmc format, and Emby will understand that. Our fetchers are accurate, but Imdb cannot be scraped directly without a very expensive license.
Luke 42085 Posted June 17, 2017 Posted June 17, 2017 In the code for xml metadata I don't see any support for a LockedData xml element, but I do see LockData which can be true/false.
funwithmedia 373 Posted September 2, 2017 Posted September 2, 2017 Perhaps "lockedfields" is what they're meaning? https://emby.media/community/index.php?/topic/43876-emby-server-read-lockedfields-value-when-importing-externally-generated-nfo-files/
Luke 42085 Posted September 2, 2017 Posted September 2, 2017 Well that's nfo, this thread is about the legacy xml format.
funwithmedia 373 Posted September 3, 2017 Posted September 3, 2017 Well that's nfo, this thread is about the legacy xml format. My bad. I know that NFO files are basically XML, so I didn't catch the difference.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now