I need help with patterns for filenames

[kraleksandr]

By default, XBMC can recognize next filenames patterns:

Code:

foo_[sAA]_[eBB]
foo.AxBB
foo.sAAeBB
foo.Pt.I

But some of my TVshows have different name. Now I use hardlinks with names like s07e04.mkv, but I spend too much time to create it.
Can someone create regexp row (for advancedsettings.xml) for this templates:?

• Morskie.d'javoly.Smerch.(13).2012.SATRip.mkv
• 05. Путь к безумию (Method to the Madness).mkv
  

Both rows dont contain season number (05 for first, 08 for second). Series number for first row is inside round brackets. Series number for second row is first two digits.

[bacobart]

Where is the season information coming from? Are you using absolute ordering? You should read this: http://wiki.xbmc.org/index.php?title=TV_Shows_(Video_Library)

In any case if the file names lack logic or information (season information), it will be impossible to write a piece of logic (regex) to parse it. XBMC expects the first regexp match to be the season, and the second to return the episode. If the season information isn't in the file or directory name, a regex cannot match it and thus not return it.

[kraleksandr]

Ok, then is there a way to create description file (like tvshow.nfo) with something like
'filename1'='s07e01'
'filename2'='s07e02'?

[bacobart]

I'm not sure.

Have you looked at tools like Ember ( http://ember.purplepig.net/projects/embermm/wiki ) to manage your video library?

Read http://www.howtogeek.com/61976/how-to-use-ember-media-manager-to-whip-your-media-collection-into-shape/ on why you would want to use it

[kraleksandr]

What does it do? It renames wrong filenames to correct templates? It is not my way bcoz files from these folders is seeding by transmission.
Looks like hardlinks is my solution...

[mk01]

(16th Feb, 2013 11:22 PM)kraleksandr Wrote:  What does it do? It renames wrong filenames to correct templates? It is not my way bcoz files from these folders is seeding by transmission.
Looks like hardlinks is my solution...

there is always a solution. but provide more information about structure of the directories - and, wheter you can put file into dir (.nfo), or is read only etc.

btw: hardlink are limited to one filesystem. if it's shared / cross filesystem, hardlinks won't be created.

btw2: some prefer putting description file into dir (your idea of describing files), some prefer changing general settings and changing patterns. if you have very very large library, adding more and more unique masks could lead to longer library updates and even probably conflicts).