YAMJ / yamj-v2

Yet Another Movie Jukebox (YAMJ) v2
GNU General Public License v3.0
28 stars 11 forks source link

Overwrite some switches of moviejukebox.properties on movie-level (inside one librairie) #584

Open Omertron opened 9 years ago

Omertron commented 9 years ago

Original issue 585 created by Omertron on 2009-03-04T17:44:42.000Z:

This is not an issue, but rather an enhancement. It has probably been asked already, but couldn't find it anywhere in the issues, so here it goes.

The enhancement would be to be able to have a ".properties" file per movie (inside one librairy of course since YAMJ already handles .properties file per librairy). The options on movie level would "overwrite" the options on librairy level, but not all options can be overwritten.

Exp: librairy contains some french movies inside a collection of hollywood movies; librairy .properties file has the following switch...

mjb.internet.plugin=com.moviejukebox.plugin.ImdbPlugin

...which works great for hollywood movies, but not always so great for french movies. AllocinePlugin is great for french movies, but not always so great for other movies.

What's the "wanted" behavior. By default, use IMDB plugin, but for some movies use the AllocinePlugin (or any other).

Same thing for TV series. By default, use theTVDB plugin, but "overwritte on serie level" for some series (exp: that don't exist on TheTVDB) by using IMDB plugin.

Another example of option that would be usefull on movie level: the opensubtitle plugin. I noticed recently that the plugin had overwritten all my correct subtitles with new incorrect ones - apprently it overwrittes the files everytime you run the jukebox. Having this switch on movie/serie level would be great (eg: once you have the correct subtitles, no need to overwritte them !)

Omertron commented 9 years ago

Comment #1 originally posted by Omertron on 2009-03-05T00:29:49.000Z:

This is almost related to Issue 507 but it refers to overring the skin setting via command line or library setting.

That issue and this one could be resolved by allowing the skin and scanner to be specified in the library.xml on a per library basis. This way one library.xml file can contain multiple library entries to create one large jukebox, while allowing for different skin for movies and TV shows, and different scanner per directory basis like for FRENCH, GERMAN or ASIAN films.

The only thing the user would need to make sure is to keep the foreign films in their own parent folder to specify in the library setting (for different scanner).

Omertron commented 9 years ago

Comment #2 originally posted by Omertron on 2009-03-05T01:47:52.000Z:

Why not allow all the configuration to be specified there? Throw in a section that looks like the one spammed to all the movie XMLs.

Omertron commented 9 years ago

Comment #3 originally posted by Omertron on 2010-02-15T04:55:35.000Z:

Stuart, Has this ever been implemented in some other way since this issue was created?

The only thing I can think of is allowing language in the nfo file, but this is not which scanner to use.

Ideally my point above: << That issue and this one could be resolved by allowing the skin and scanner to be specified in the library.xml on a per library basis.

still seems appropriate.

Otherwise, I can only think of 1 way that might be a workaround:

Omertron commented 9 years ago

Comment #4 originally posted by Omertron on 2010-02-15T09:40:26.000Z:

Vincent is doing some re-work around plugins, so we can be more flexible about the priorities of each, so you can scan different movies, or groups of movies, using different plugins.

This will allow those multi-language people to scan French movies with Allocine, Italian with FilmUpIt, etc.

Also useful for other plugins such as some IMDb for TV series

This is a while away yet though.