English > Support

[FAQ] What is the best action to take when the file scanner gets it wrong?

<< < (4/6) > >>

deazo:

 Here is the result, not good.

 I guess we should wait for Nostra and Rick to help me out hey, unless you have another suggestion?
 I wonder if it's not a Windows setting rather than a PVD one that is preventing these regex's to be used...?

 

[attachment deleted by admin]

buah:
Well, I think you should wait for them.

Till then, here's my example how it works for me. Maybe you should try to reproduce this case (naming folders and files, locations, etc).
If you don't get the same result as I do, ready your brain for exploding :P

[attachment deleted by admin]

rick.ca:
Sorry, I'm not sure what the problem is. As far as the regex goes, (?i)^.*\\(?P<title>.*)\..* seems appropriate. It means...

(?i) - using case insensitive mode...
^.*\\ - from the beginning of the string, match any number of any character until a "\"...
(?P<title>.*)\. - then match any number of any character until a "." and save this as <title>...
.* - then match any number of any character.

This won't handle periods in titles or resolve ambiguities using <year>, but otherwise should work as expected. That is, save the string between the last "\" and the following "." as <title>.

Maybe the problem is in what the program does with the <title> returned by the regex. From your examples, it seems it's matching what it finds to titles which end in the same string (e.g., or to American Splendor). Are these all new movies you're trying to add via the scanner? Maybe the result would be different if such titles existed in the database—so there could be an exact match.

So the answer to your original question might be to simply create the movie record, then scan. That might be the best you can do when the filenames do not include <year> to resolve ambiguities.

The scanning routine could use some improvement. In particular, the results window should provide the means to fix this sort of thing (e.g., "no, not American Splendor, add a new movie with the title Or").

deazo:

 
 "Or" is actually a record in my database (http://www.imdb.com/title/tt0388311/) so I am not trying to add a new movie.
 American splendor is also a record.
 So creating the record before hand cannot solve this.

 Another thing is that the results are the same with or without the Regex's. If I empty them in preferences and run a scan, it will give me the same suggestion.
 So I suspect the program is not even using the Regex's!
 It must then use the default settings, but what are they?
 I'm lost here, maybe I should try scanning with a different computer what do you think, could it be a setting on my computer?
 This is a fresh install of pvd by the way.



rick.ca:

--- Quote ---Another thing is that the results are the same with or without the Regex's. If I empty them in preferences and run a scan, it will give me the same suggestion. So I suspect the program is not even using the Regex's!
--- End quote ---

I never thought of trying that. But it doesn't follow the program is not using the regex. It's more likely that the program logic uses the same thing (the string between the last "\" and ".") in the event there are no regex matches. Maybe it's just taking the first (partial) match found, based on the assumption there are unlikely to be duplicates. This seems to be a bad assumption given your filename structure, but it works reasonably well if there's a year that can be matched as well. I imagine the requirement that the filename match the title exactly would be too restrictive for most users.

I don't know how the scanning time would be affected, but maybe the scanner should present all matches—so the user can select the correct one in the results window.

Meanwhile, the only thing I can suggest is that you enter the file path "manually" in such cases. Unfortunately, that means adding the incorrect items the ignore list, and noting the titles so they can be looked up after the scan routine is otherwise complete.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version