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 use place holder files like "X-Men 2 (2003).bluray.disc" or "Daredevil (2003).dvd.disc" to get my existing DVD's and Bluray's displayed at the XBMC database. When using XWMM I would expect to get a DVD or Bluray icon displayed where usually at mp4 files the icons for AAC,SD/720,16:9 are displayed but it shows not any icon.
The text was updated successfully, but these errors were encountered:
Seemingly initiating a library scan form the web interface and refreshing (F5) after other Mediaflags display. But I still cant get any Bluray/HDDVD etc that you add to filenames.... So I can confirm this bug.
Having tested this across TVshows/Movies as well displaying these mediaflags seems to be an issue generally and flags you add to filename _never_ get displayed which makes this a definitive issue.
Media flags rely on the video/audio codec metadata which Kodi only populates when a file is played.
DVD/BluRay labels are a skin feature in Kodi. If the file name doesn't contain a media source Kodi falls back to the video codec information to select the correct media flag.
I'm going to relabel this as an improvement/feature request as it's not currently broken it just doesn't support parsing file names for media information.
The standard confluence skin is able to do it and when I check an nfo file export of the movie I am not able to detect there the Bluray media information. So your analysis should be correct. Thank you for checking and adding the request.
I use place holder files like "X-Men 2 (2003).bluray.disc" or "Daredevil (2003).dvd.disc" to get my existing DVD's and Bluray's displayed at the XBMC database. When using XWMM I would expect to get a DVD or Bluray icon displayed where usually at mp4 files the icons for AAC,SD/720,16:9 are displayed but it shows not any icon.
The text was updated successfully, but these errors were encountered: