osak00006 12 Posted March 27, 2020 Posted March 27, 2020 Is it possible to lock a movie from updating metadata at the movie ID level? Which is to say, if I customize metadata and then replace the video file... say upgrade from DVD to BluRay, or simply a higher quality BluRay 1080p copy, is there a way to prevent Emby from refreshing the Collection and other metadata info? Alternatively, is there any way to have Emby prefer local data, if it exists? That would be another way that I could work around...
Luke 42088 Posted March 27, 2020 Posted March 27, 2020 Alternatively, is there any way to have Emby prefer local data, if it exists? Hi, out of the box with nfo files Emby will always prefer local metadata. Does this answer your question?
osak00006 12 Posted March 27, 2020 Author Posted March 27, 2020 Hi, out of the box with nfo files Emby will always prefer local metadata. Does this answer your question? Yes, thanks! Sorry, I've struggled mightily with custom metadata and I think I finally get the NFO file component
osak00006 12 Posted April 1, 2020 Author Posted April 1, 2020 Thanks for the feedback. Hi Luke, One quick follow question... so this seems to work, as expected, with the exception of custom Collections. Use case: The Avengers.nfo - Deleted TMDB Collection ID from - Manually added <set>The Marvel Cinematic Universe (The Infinity Saga)</set> to local NFO file Emby doesn't scrape in the movie set that I've added. I have to manually right click on the movie and Add to Collection. Am I doing something wrong?
osak00006 12 Posted April 1, 2020 Author Posted April 1, 2020 (edited) Collections aren't stored in NFOs. So they're only stored in the \data\collections\collectionname\collection.xml ? Once the XML contains the movie path... what happens if I temporarily delete and then re-add the same file? Ideally, it would just go back into the Collection, based on the XML, right? For some reason, that doesn't seem to happen on my setup. The movie gets added back to Emby, the path is still in the Collections.xml and matches the file path, but it doesn't show back up in the Collection until I manually re-add it by left click Add to Collection... What am I missing? I'm soooo close Edited April 1, 2020 by osak00006
Luke 42088 Posted April 1, 2020 Posted April 1, 2020 Right we don't use the tag from nfo files, although it's possible for the future. I would suggest using the emby web interface to build your collections.
osak00006 12 Posted April 2, 2020 Author Posted April 2, 2020 (edited) Right we don't use the <set> tag from nfo files, although it's possible for the future. I would suggest using the emby web interface to build your collections. So they're only stored in the \data\collections\collectionname\collection.xml ? Once the XML contains the movie path... what happens if I temporarily delete and then re-add the same file? Ideally, it would just go back into the Collection, based on the XML, right? For some reason, that doesn't seem to happen on my setup. The movie gets added back to Emby, the path is still in the Collections.xml and matches the file path, but it doesn't show back up in the Collection until I manually re-add it by left click Add to Collection... What am I missing? I'm soooo close Also, I just noticed Collections can be locked. What does this accomplish? In testing, it looks like it freezes the collection and movies within the Collection to the point that, even after I delete a media file, it still shows up in the Collection. Is that right? As a potential workaround, that might be close enough to what I'm after... Edited April 2, 2020 by osak00006
Luke 42088 Posted April 2, 2020 Posted April 2, 2020 Ideally you would not touch the collection files and just use the Emby web interface. Why not just do that?
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