File system improvement

[taconaut]

Ahhh now I get what you mean. Don't think I'm going to go this way, as most of the work has already been done. I've attached the DB schema I'm using. Some fields are still wrong (e.g. Orientation has nothing to do in the video table).
Usually I also code c#

[loraderon]

I see.

The most important part is to actually support a Media Library. Keep on the great work, it's highly appreciated!

You said that your are not to happy about the method for populating the db, maybe this is a great place to introduce another type of plugin/scraper?
Then you could ship a default plugin/scraper that can easily be updated/replaced.

This is just a suggestion.

Otherwise I'll probably just create a custom utility for importing XBMC library data into your newly developed media library (writing to the db directly).

[taconaut]

You said that your are not to happy about the method for populating the db, maybe this is a great place to introduce another type of plugin/scraper?
Then you could ship a default plugin/scraper that can easily be updated/replaced..

That's what's planned, but for now no interface is defined and no reflection is used to load such a plugin dynamically. We''ll see if it will make it into the first beta; there are so many things I'd like to see in there

[rakosnicek]

I rather dislike the idea of needing to use IMDB to gather the required information. For instance, I may have saved the movie in a file that is named according to my own method or in my own language and neither of which cause the right information to be returned from an IMDB query.

For audio, what about using MP3 tag information contained in the file(s) to build the information store in the database rather than using an online database?

And along those lines, what are the chances of seeing this feature first delivered as a "beta" for audio whilst a method to implement the same for video is decided upon?

[taconaut]

You aren't forced to use anything (e.g. imdb). The plugin system to import data can import data from anywhere; currently only online sources (imdb and tmdb) exist. Plugins can be developed, which receive a name (which is being deduced from the file name) and the absolute path of the file with which it can import the data. It could use the file itself to import metadata from mkvs or id3 tags from mp3s; I haven't thought of a use case which wouldn't be covered by the plugin system.

[rakosnicek]

You aren't forced to use anything (e.g. imdb). The plugin system to import data can import data from anywhere; currently only online sources (imdb and tmdb) exist. Plugins can be developed, which receive a name (which is being deduced from the file name) and the absolute path of the file with which it can import the data. It could use the file itself to import metadata from mkvs or id3 tags from mp3s; I haven't thought of a use case which wouldn't be covered by the plugin system.

I think the reading existing files for information should take first priority.

I don't really want to tell Amazon (they own IMDB) every time this plugin runs and needs new data.

[taconaut]

That's up to you it's fully configurable

[rakosnicek]

Ok, just let us know when there are plugins available for using the information in the files rather than from the internet, ok?

[chocolateboy]

I don't really want to tell Amazon (they own IMDB) every time this plugin runs and needs new data.

The IMDb API plugin does not contact IMDb.

[taconaut]

I don't really want to tell Amazon (they own IMDB) every time this plugin runs and needs new data.

The IMDb API plugin does not contact IMDb.

Good point