Infuse not using year in file name to select correct metadata
7 posts / 0 new / Last post
#1 November 16, 2019 - 6:55pm
I named a file Tracks [2013].mp4 specifically so that Infuse would select the metadata for the 2013 release of that film not the version from the 70s. But Infuse is selecting the 70s one by default instead of the 2013 film even though I specifically put the year of the film in the file name.
Is the year in the file name supposed to do anything or does Infuse ignore it?
I have Infuse 6 Pro
Attachments:
I've seen instances where brackets throw off the metadata fetch so you may want to stick with just "Tracks 2013.mp4" or use parentheses like "Tracks (2013).mp4
Most of the time the year added to movies will help in narrowing down the correct metadata but it is showing in the edit menu and once you select the correct entry it will remember it if needed again.
•Just Another Infuse User• •Not An Employee Of Firecore• •Certified Curmudgeon•
This actually looks like a quirk with the search results provided by TMDb. Even when Infuse sends the year, the top result is the 1976 release, which Infuse uses.
The same thing can be seen when searching on their site.
https://www.themoviedb.org/search?query=tracks...
If you want, you can kind of hack it to avoid having to manually edit the movie by using the Bulgarian title: Пътища [2013].mp4
https://www.themoviedb.org/search?query=Пътища%20y%3A2013&language=en-US
Infuse 6 for iOS and Apple TV is now available!
How do I report this issue to themoviedb?
Their forum may be the best place to share feedback like this.
https://www.themoviedb.org/talk
Infuse 6 for iOS and Apple TV is now available!
This shows up because there was an Italian re-release of the movie in 2013. I've had this same issue with another movie and contacted them about it. They said there is nothing to do except use a different filter for search. Instead of just year, you can use theatrical release or primary year or something. Don't remember exact syntax. But that would need to be something that Infuse would have to change. And who knows what the fallout would be for changing that?? Some testing would have to be done on a lot of movies.
Apple TV 4, Apple TV 3, iPhone Xs, iMac 5k, iPad Pro, Airport Extreme, Airport Express, Synology DS916+
I'm seeing the same issue with the film 'Cold War' which are two films, one from 2017 and one from 2018.
I have submitted a report to themoviedb directly, as suggested by James.
https://www.themoviedb.org/talk/5e0df97312c604...