FileBot

I'm curious if this is a mistake or just the way it is meant to be:

$filebot -non-strict -rename --db thetvdb --format "/home/belgarth/Downloads/TV-Shows/{n}/{n} - {s}x{e} - {t}" /home/belgarth/Downloads/TV-Shows/Unsorted/lost.girl.s02e18.720p.hdtv.x264-2hd.mkv
Rename episodes using [TheTVDB]
Auto-detected query: [lost girl, Lost]
Fetching episode data for [Lost]
Fetching episode data for [Lost Girl]
Renamed [/home/belgarth/Downloads/TV-Shows/Unsorted/lost.girl.s02e18.720p.hdtv.x264-2hd.mkv] to [/home/belgarth/Downloads/TV-Shows/Lost/Lost - 6x2 - LA X (2).mkv]

filebot appears to be thinking that the x264-2hd is the season/episode string and is somehow turning it into 6x2. I understand why it could get confused by such a string in the filename, so I just want to confirm if this is the expected behavior.

No, SxxExx pattern definitely takes precedence. Are you sure Lost Girl 2x18 exists in your chosen database? I suspect the episode doesn't exist and thus FileBot fuzzy logic converges on the next best match. I'll check into it though, maybe there is an odd bug somewhere. If you use normal strict mode these matching problems can't happen.

Yep, did run some tests and the fuzzy logic failed this one. In my case it always matched Lost 2x18 though. I'll fix that for next release.

EDIT:
Try the latest revision: http://sourceforge.net/projects/filebot ... ebot/HEAD/

In this case strict mode fails due to confusion between Lost and Lost Girl.

I'm running filebot on ubuntu installed via the deb package. Are there instructions somewhere on how I can use the latest JAR to take over the currently installed filebot structure (ie the new latest jar will be the one run when /usr/bin/filebot is executed) without messing up future installs of the release deb?

Just replace the jar in the installation folder with the latest revision and you're good to go. There'll be no side effects from updating the core like this.

should "filebot -version" reflect the new version after using this method?

belgarth@media-server:~$ sudo cp filebot-2.5-r935-matchfix.jar /usr/share/filebot/FileBot.jar
belgarth@media-server:~$ filebot -version
FileBot 2.5 (r905) / OpenJDK Runtime Environment 1.6.0_23 (headless)

Nope. It's hard coded like version now because update kept breaking on some system. You can check FileBot.jar/Meta-Inf/manifest, that tell you the actual build revision.