English > Support

TV-series filename structure

<< < (3/6) > >>

rick.ca:

--- Quote ---Because of sake of other users who might found it useful, I think it was a good idea not to open new topic but to activate old one you started, both of them upon same issue.
--- End quote ---

I thought it seemed familiar... ;)

Thanks. Topics merged.


--- Quote ---Considering this, I suggest to pin a topic with proven regexps for different syntax of file names.
--- End quote ---

Hmmm... If one were deciding what filename structures to use that would work in PVD, there are a variety of answers easily determined by examining the regex. The problem is, most users already have files and would rather not have to change them to suit the regex provided. Users in that circumstance have to accept the choice they face: Either modify the regex to suit their filenames, or change their filenames to suit the regex. Then there are those who not only use patterns not recognized by the regex provided, they use a variety of different patterns. That, of course, makes everything more complicated. Generally, each pattern will require it's own regex, and more care will be necessary to ensure the regex don't conflict with one another and are processed in the correct order.

My point is, we would never be able to pin down a finite number of filename pattern sets in use. And it would mean listing a complete set of regex (in the correct order) for each. It would be much easier—and probably more useful—to document the intended purpose of each of the regex provided, together with examples of filename patterns that are correctly interpreted by each one. From that, it might be easier for a user to find a filename pattern close to what they are using, and then determine what modification is necessary so it would work for them.

This is the format I'm imagining...

Type/Regex/ExampleCommentsType:1. Series (title in filename)folder ignoredRegex:(?i)^.*\\(?P<title>.*)(s|\b)(?P<season>[0-9]{1,3})e(?P<episode>[0-9]{1,3})   case insensitiveExample:Series title s01e01 remainder ignored.ext1-3 digit series/episode numbersVariation:Series title S01 E01.extadd a space before the "e"Type:2. Series (hyphen-delimited with episode title)folder ignoredRegex:(?i)^.*\\(?P<title>.*).?-.?(?P<season>[0-9]{1,3})x(?P<episode>[0-9]{1,3}).?-.?(?P<eptitle>\w*\b)does "\w*\b" match a oneExample:Series title - 1x001 episodetitle.extword episode title only?Variation:Series title - 1x001 episode title.ext...change to "\..{3,4}"
I could post the skeleton of such a thing, and then others could help flesh it out by posting suggestions and examples to the topic (e.g., "here's another example for type 1..."). I would then add those to the top post. Users could also post their personal modifications in the same format (e.g., "type 2 did not work for my series filenames, so I replaced it with this...").

Would such a topic be helpful, or too mind-numbing to be of any use? :-\

patch:

--- Quote from: buah on April 30, 2010, 09:37:12 pm ---Considering this, I suggest to pin a topic with proven regexps for different syntax of file names. In such a topic, comments wouldn't be allowed ... only filename -> contributed proven regexp.
...
Any thoughts?

--- End quote ---
Why not put it in the PVD wiki

Lordfinarfin:
(sory for my english xD) I did that at work xD, so i dont have all the structures that I tried.  My expression exclude all the words that appear after a dot. Problem? you cant put a dot in the middle of an episode tittle. This formula is to remove the file the file extension.

buah:

--- Quote ---My point is, we would never be able to pin down a finite number of filename pattern sets in use
--- End quote ---

We don't have to, need to or tend to. My idea was to constantly pin down in a separate pinned topic only those filename patterns discussed here and for which regexs were resolved (confirmed, proven). According to this, and taking place of an average user who's almost for sure inexperienced with regex, probably it would be appropriate to format your idea as

Type/Example (discussed in this forum)/Regex (resolved, you need to type in PVD's Preferences)

... or in PVD Wiki, why not.

rick.ca:

--- Quote ---We don't have to, need to or tend to...
--- End quote ---

It seems you're missing my point. Let's say someone has one specific filename pattern that's not being properly recognized by the default regex. They ask for help here, and someone suggests an expression. This expression is tested and proven to work for the given filename pattern. You're suggesting we create a list of these patterns with proven regex—in a locked topic. I'm saying this will be of limited use, if not misleading. Consider...

Another new user, using exactly the same filename pattern, finds it's entry in this list. They add the "proven" regex to their configuration, and it still doesn't work. Oops. We forgot to consider all the regex in the configuration continue to function. So a similar one in the default set still matches and occurs first. So should the list indicate which expressions should be removed when the "proven" one is added? No, we can't do that. It may still be applicable to another filename pattern. The list fails to recognize the proper solution could be to (1) replace an existing expression with the recommended one, (2) have two expressions, but put them in an order that doesn't result in conflicts, or (3) revise the existing expression so it will recognize both filename patterns. The last is obviously the best solution, and will rarely be found by anyone relying on such a list—especially if unfamiliar with regex.

My suggestion, as awkward as it may seem, provides a way of directing the user to the default expression that most closely fits their filename pattern. They may then effectively consider what changes might be necessary to their configuration (e.g., consider the three choices mentioned). If they need help they can ask. When the problem is solved—assuming there is a discussion about it—the list can be updated with another example, comment or variation. If that's not possible—because the solution is to add a completely different expression to the set—this new expression can still be documented in the same manner. I could provide a second list (in the message following the first) for such "custom" expressions. We could periodically consider which of these should be added to the default configuration.


--- Quote ---...or in PVD Wiki, why not.
--- End quote ---

Because it doesn't provide for a one-stop place for reference, discussion and help. Anyone is welcome to copy any material in this forum and add it to the wiki—where it may serve as a more permanent and static reference.

Navigation

[0] Message Index

[#] Next page

[*] Previous page