English > Support

[SOLVED] movie file path problems

<< < (2/2)

CAD:
Hi Movie.man

regular expression is difficult to understand.
PVD already comes preconfigured for common regular expressions.
For movies it reads the folder name rather than the files. the year helps to identify correct entry when search online databases.

most people adjust their movie naming standard to the regular expression.
I store my movies as ISO's rather than in video_ts folders.

The naming standard I use is the movie name as it appears in IMDB and in brackets the year.
eg. g:\multimedia\movies\Fingers (1978)\finger.pal.iso

or in your case
g:\multimedia\movies\Fingers (1978)\video_ts.
PVD will get the title from the folder name.

I have noticed if I have the same movie in 2 different locations, the scanner seams to flip flop between the two locations.

If you have the same movie as dvd in video_ts folder (or iso) and on avi., you could try storing them in the same folder and see what happens.

eg
J:\MEDIA\Film\DOCUMENTARY\Everest The Death Zone (2009)\PBS.NOVA - Everest - The Death Zone.avi
J:\MEDIA\Film\DOCUMENTARY\Everest The Death Zone (2009)\video_ts

movie.Man:
@CAD - thanks for the help

storing in ISO format certainly makes sense

as for the Everest example, those 2 movies were completely different, thus my not understanding why PVD is considering 2 paths, but, alas, apparently this is where regex comes in, which i do know about - just that i'm terrible at understanding/writing them

still, it seems like such problems would be alleviated if PVD handled this a bit differently.  i guess my question would be; i'm not using regular expressions when i specify a path, so why is the scanner using them to verify a path instead of first considering whether the path i've specified is correct or not?

for new movies i understand this behavior... well, no i don't either, but i'll just accept that it's necessary and/or provides functionality.  however, when verifying a path, it just seems like the scanner should consider the path the user set instead of disregarding it and starting over.  this way one could [accidentally] have multiple copies of the same movie stored with different file names, or in different folders, or different movies with the same name in different folders, and there would be no problems.

rick.ca:

--- Quote ---when verifying a path, it just seems like the scanner should consider the path the user set instead of disregarding it and starting over.
--- End quote ---

Yes, this is a known issue, and nostra has indicated he will fix it. As I mentioned in your Feature Suggestion topic, the scanner can't handle adding a new file to one or more files already recorded in File path. So if I've previously added a trailer and then try to add a movie file for the same title, the scanner will recommend replacing the trailer with the movie. If I let it do so, next time it will do the reverse. As CAD said, it will "flip-flop."

But when you say "those 2 movies were completely different," I'm led to believe this may be contributing to your confusion, but is not the source of your problem. You have to respect the fact the routine is scanning the media on your HDD, using the provided regex to extract titles, and then recommending action based on that information. If you haven't adopted a consistent file-naming convention and configured the scanner with regex that will correctly handle that convention, you're going to have problems. If these two movies were uniquely named Titles in your database and their file pathnames were in a form the regex could correctly extract those unique titles from, then you wouldn't have a problem. The DVD files would be matched to the DVD version of the title, and the AVI would be matched to the AVI version.

movie.Man:
yeah, i realize the problem with those particular files had to do with the regular expressions .  armed with that knowledge, i can make the corrections i need to.  thanks for the help!

Navigation

[0] Message Index

[*] Previous page