IMDB matching wierdness

[Luke 42078]

1 hour ago, davepusey said:

But the point is my workflow has already identified the correct movie/series to match it with, and I've given a unique indentifier for it. If Emby is unable to match with just that then either I've given an incorrect ID or something is wrong. I do not want Emby trying to figure out the movie/series matching by itself, I want it to match explicitly on the identifier I am providing ONLY.

The only way to accomplish that is to ensure all your file names have the ids based on your highest priority fetcher. There’s no way to prevent it from searching by name, so you just have to ensure it never gets there.

[davepusey 1]

Which is what I am now doing, and it does seem to be working.

My original design was based on an incorrect understanding that by providing an IMDB ID, that it would be directly queried against the IMDB website/APIs.

Edited February 6, 2025 by davepusey

[Fch11 3]

Will switching from imdb to tmdbid force a rescan for video preview and cached metadata rescan?

[Luke 42078]

34 minutes ago, Fch11 said:

Will switching from imdb to tmdbid force a rescan for video preview and cached metadata rescan?

Hi, switching what, where exactly?

[Fch11 3]

53 minutes ago, Luke said:

Hi, switching what, where exactly?

My movie folders and titles are marked 

310 to Yuma (2007) {imdb-tt0381849}

If i change that to tmdbid instead will it force a new scan?

[Luke 42078]

1 hour ago, Fch11 said:

My movie folders and titles are marked 

310 to Yuma (2007) {imdb-tt0381849}

If i change that to tmdbid instead will it force a new scan?

Yes when you rename files and folders then it becomes a brand new item in your server library. If you have nfo files that can help preserve existing metadata.

[davepusey 1]

When I renamed mine earlier today it did retain all the Watched tickmarks on the episodes, so it did seem to recognise these were the same item.

[Luke 42078]

7 hours ago, davepusey said:

When I renamed mine earlier today it did retain all the Watched tickmarks on the episodes, so it did seem to recognise these were the same item.

That's user data, which is stored based on external id's so that's why you're seeing that.