You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a MKV file with an attachment named "kodi-override-metadata". The attachment is a UTF-8 encoded file containing the URL to the correct TMDB page for that movie: https://www.themoviedb.org/movie/484641-anna
Kodi does not read the attached NFO and therefore does not directly scrape the metadata from the provided URL to the movie page on TMDB.
Expected Behavior
I expect Kodi to read the attachment and scrape the movie directly from the provided URL in the attachment as this wiki entry describes: https://kodi.wiki/view/Video_file_tagging#MKV_tag_options
Actual Behavior
Upon library update Kodi seems to ignore the attachment and scrapes the wrong movie: https://www.themoviedb.org/movie/596258-anna
My MKV file is named "Anna (2019).mkv". TMDB has three movies titled "Anna" that were released in 2019.
Additional context or screenshots (if appropriate)
Besides "Description" MKVToolnix GUI also shows a field labeled "File name". If I put "kodi-override-metadata" in the "File name" field, the library update failes when Kodi tries to scrape that movie file. A popup message titled "Couldn't download information" is shown with the text:
"Unable to connect to remote server. Would you like to continue scanning?" -> "Yes" | "No"
If I click "No" the file will be scanned again during the next library update. If I click Yes, the movie file is not added to the library and will also not be scanned at the next update. I have to change the "kodi-override-metadata" text in the "File name" field to something else, to have it scanned again.
I am unsure whether this is related to the bug #16150
Your Environment
I can reproduce this bug on the following operating systems:
Windows 7 x64
LibreElec 9.2 on Raspberry Pi 3B+
The Kodi version is always: 18.5
The text was updated successfully, but these errors were encountered:
Using Windows 10 and Kodi v18.5, I was able to confirm this issue.
I enabled/disabled the setting Use Video File Tags, also enabled and disabled "Movies are in separate folders that match the movie title" and neither setting had any effect.
Bug report
Describe the bug
I have a MKV file with an attachment named "kodi-override-metadata". The attachment is a UTF-8 encoded file containing the URL to the correct TMDB page for that movie:
https://www.themoviedb.org/movie/484641-anna
Kodi does not read the attached NFO and therefore does not directly scrape the metadata from the provided URL to the movie page on TMDB.
Expected Behavior
I expect Kodi to read the attachment and scrape the movie directly from the provided URL in the attachment as this wiki entry describes:
https://kodi.wiki/view/Video_file_tagging#MKV_tag_options
Actual Behavior
Upon library update Kodi seems to ignore the attachment and scrapes the wrong movie:
https://www.themoviedb.org/movie/596258-anna
My MKV file is named "Anna (2019).mkv". TMDB has three movies titled "Anna" that were released in 2019.
To Reproduce
Steps to reproduce the behavior:
Debuglog
The debuglog can be found here: https://paste.kodi.tv/isowajagus.kodi
Additional context or screenshots (if appropriate)
Besides "Description" MKVToolnix GUI also shows a field labeled "File name". If I put "kodi-override-metadata" in the "File name" field, the library update failes when Kodi tries to scrape that movie file. A popup message titled "Couldn't download information" is shown with the text:
"Unable to connect to remote server. Would you like to continue scanning?" -> "Yes" | "No"
If I click "No" the file will be scanned again during the next library update. If I click Yes, the movie file is not added to the library and will also not be scanned at the next update. I have to change the "kodi-override-metadata" text in the "File name" field to something else, to have it scanned again.
I am unsure whether this is related to the bug #16150
Your Environment
I can reproduce this bug on the following operating systems:
The Kodi version is always: 18.5
The text was updated successfully, but these errors were encountered: