send me the file paths so i can test with

Having files named The Big Bang Theory or Big Bang Theory shouldn't affect the auto-detection matching process since both are considered valid alias. Forcing the name is easy in the format, but at this point filebot already has decided on an Episode match. Not sure what you're looking for. Is it hav...

Can u send me the output logs for a call that shows this issue? Not sure how to look into this problem right now.

2. Include log output

Pretty Please~

Well, you can test with the CLI as well it'll just take longer. :D Your format doesn't make sense cause the if the file is a subtitles the final name would be "......subs/" (and not end with an actual filename). Once you understand how the format works you'll see that it's not strange at a...

Just build that into your format expression. Play with the GUI format editor to work out your format before you make it work with amc.

FAQ -> Last Q

Just add a unqiue() call:

hahaha, never bothered to actually look it up Wife with Wife - Absolutely Not For Children

This one definitely works: @see http://snag.gy/PLIPX.jpg

Haha, this one is really bad luck! :D There's an anime names:[つまつま 人妻×人妻, WWW, Wife with Wife] which allows WWW to be part of the query, and it gets matched to names:[Christopher Hitchens, www.raydragon.com Presents...] :D Maybe shitty data in the IMDb when that one was scraped. Try one of the lates...

Send me the paths and I can try for myself. If you look at the 2 lines of SxE you'll notice that it just does two renames, once to add lots of extra info like airdate and a second to then rename again with normal SxE order matching by airdate/title. I don't see why it wouldn't execute the second lin...

This will catch it: Give me the whole path and I'll have a look which token is messing with it.

I added DDL to the global blacklist anyway. If you try again next week it should work better.

Have you tried -non-strict?

1. Windows CMD is weird. I've added logging into the Java core by now. Just set something like --log-file amc.log 2. The second gmail error is probably due to some modification you made, or it was broken when you copied it. Either way I can't really be bothered to maintain forks and outdated version...

Of course the answer is "No, it's suppose to work fine with those parameters" . How else would the script know what folder to process? Look at the docs: https://trac.transmissionbt.com/wiki/Scripts#OnTorrentCompletion First you figure out how you access these variables in your shell script...

Yes, that's where these mysterious environment variables are supposed to be coming from: $TR_TORRENT_DIR/$TR_TORRENT_NAME That's the first thing I would be testing. That transmission is in fact passing those variables along. ;) Also it is likely that you can only set one script, unless the docs say ...

Please raise any issues with the synology package with the official maintainers directly.

I only maintain portable and ipkg package which you may be able to use once java is working.

1. Tells you it's a cmdline tool: since filebot/amc is really just a cmdline tool you can probably make it work with any software that can run external programs, or just call it every once in a while with scheduler or cron. 2. Shows you a video how it is just a cmdline tool: http://www.youtube.com/w...

Run with FileBot (console) and paste me the output. Also opening cmd and running this command would be helpful: filebot -script fn:sysinfo Most likely your anti virus is blocking that library. Try copying jnidispatch.dll into the filebot install folder: https://sourceforge.net/p/filebot/code/HEAD/tr...

Pretty much every post in this forums is about this, just not Sabnzbd specific

The amc script does everything:
http://www.filebot.net/forums/viewtopic.php?f=4&t=215

Now you just need to figure out how to integrate that with Sabnzbd.

Why use a format you don't understand instead of just letting it's use it's default that does what you want?

What options are you setting? Are you overriding the format and make it not change the name at all?

Logs would be helpful. Always.

- Fixed file encoding error on several of the groovy config files (were Unicode when ANSI was expected)

The only reason it may expect ANSI is because it's set as default encoding on Windows, it'll probably be UTF-8 on other systems. I recommend forcing UTF-8 whenever reading / writing anything.