So the scanner should be using <title>, not <origtitle>.
Hmm, so you're saying currently the scanner evaluates only the named capture <origtitle> to compare the filename with the movies in PVD? To tell the truth I expected the scanner to evaluate
every one of the named captures (<origtitle>, <title>, <year>, <season>, <episode>, <eptitle>) contained in a regular expression. Then in case that their combination in a filename matches an existing record in PVD it would offer to change the path (if different). Only if they don't match it would offer other guesses it made in base of filename, records etc.
It does so at least for the named captures <episode>, <season> and <eptitle>. There it does detect whether <eptitle> already exists in PVD or not and it doesn't concatenate.
From my point of view for the file scanner a filename (movie/episode) which matches exactly a regular expression and matches exactly a movie in PVD (id est all three, filename, regular expression and record, are intentionally managed by the user) should always have the highest priority over the suppositions which makes the software.
But why maintain multiple records for the same movie, when all that's different is the language?
Yes, that would be my ideal world
. Most of my movies are done this way (and a lot of work to synchronize
. Unfortunately this can't be done for all movies ... First there are different versions for both languages like an extended cut and a normal version. (those have different original title) Then we have different versions which seems to be the same movie. But for some reason the distributors for one or the other country decided to cut out different scenes of the movie (I.g The Queen, Angels & Demons and many others). So in the end you have different video tracks (and consequently different audio tracks). Although there would be hardly a saving in diskspace I could put them all in one container (2 video tracks and 2 audio tracks) but unfortunately my streaming box doesn't support choosing between different video tracks in the same container, only between audio tracks and subtitles. So in the end I have to maintain two different movie containers id est files.
This is a real problem where there's a need to intentionally record two or more paths in one record (e.g., a movie and it's trailer). When one is matched, the scanner is unable to add the other.
As I said above for <episode>, <season> and <eptitle> it doesn't. Trailers for episodes are also very common
And it doesn't concatenate. This doesn't seem to be a consistent way to treat the filenames. I think the treatment should be consistent through all kind of filenames. One way or the other.
I didn't consider the fact trailers (because more than one file for the same movie (parts) could be resolved very easily with regular expressions)
I could immagine a solution to this problem would be an option to switch of this concatenation for all kind of filenames (a similar option exists for multiple disc detection). But the best way, IMHO, would be the logic mentioned above.
Thanks