Why are DVD extras limited to a single directory?

[Koleckai Silvestri 1151]

NFO files, in this case, are simply XML text files with the Item's Metadata held within them. They won't break Kodi because they are supposed to follow Kodi's Standards. Though, even if they have extra fields Kodi should just ignore those fields.

 

http://kodi.wiki/view/NFO_files

[PenkethBoy 2066]

@@Luke has commented on other threads that they have to be careful changing nfo(xml) file formats as it can break things in other apps

 

maybe its not Kodi just the others we would need to account for etc

[Luke 40009]

We can add fields to nfo, it's not a problem.

[PenkethBoy 2066]

good - thanks for confirming

[TroyBennett 9]

I personally don't mind the extras being in one folder.  The problem I see all the time is the naming of the extras because there isn't any corresponding nfo or xml file

 

So if I get a bluray with lots of extras i have to resort to a naming scheme sush as:

Deleted 1. Play all

Deleted 2. <deleted scene here>

...

Deleted 13. <deleted scene here>

1. Making of <movie name here>

2. some other extra

Actor Interview 1. <actor name here>

Actor interview 2. <actor name here>

etc.

 

I have to name them like this to keep the files together or in a particular order

 

If we had access to use an nfo or xml file for this I think it would be much better. we could just name files extra1.mkv, extra1.nfo

and the nfo would contain all the information we want about the extra, and we wouldn't have to resort to long file names to keep the extra in a particular order.

[funwithmedia 369]

Well we do support embedded metadata within videos. We could also do an nfo file for these.

I'd be interested in NFO support for Extras (both support for writing to NFO, but also for reading an pre-existing NFO on import, like is done for regular items). As part of my transitioning from my old setup to Emby I've been generating NFO files for everything in my old (non-Emby) library and was surprised and a little bummed that the Extras weren't having their NFO files (which I'd generated outside of Emby) picked up by Emby (as some of my extras do have associated IMDB details). However, given that the way extras are currently presented (ie, such that you don't really see/view much of their details), I can understand why there currently is not much support for additional details (and thus no NFO file support).

[funwithmedia 369]

For those that are interested, a bit ago I created a Feature Request regarding NFO support for Extras:

https://emby.media/community/index.php?/topic/43845-emby-server-emby-theater-support-nfo-files-and-automatic-metadata-lookup-for-extras/

 

And regarding the ideas and questions about sub-folders for Extras: What if Emby added basic support for sub-folders within the Extras folder, where the sub-folder name would be used as a grouping title when displaying those extras within Emby apps? This would give maximum flexibility to users, as they could name the folder whatever they want. For example, if I was adding a 6-part documentary, I might create a folder (eg, "Documentary Title") just for that within Extras. Then, within Emby apps Emby could display "Extras" (for items in the root Extras folder), and below that "Extras - Documentary Title".

 

I do think that something like the above of simple sub-folder support for Extras in conjunction with then grouping those Extras by the folder name within the Emby interface would be a useful, and relatively easy method, of organizing one's Extras. It would allow a lot of flexibility (because folks could name folders however they want), while keeping the programming overhead relatively low (ie, Emby just would need to parse the folder name and contents, and then output those groupings, perhaps just in alphabetical order of folder names).

 

Thoughts?