call filebot -script fn:amc "C:\completed downloads" --output "C:\New series and movies" --conflict override -non-strict
filebot -script fn:cleaner "C:\completed downloads"
The script works fine for all my downloads, but somehow new family guy downloads get excluded. See log below. The show has been downloaded twice and both are excluded, but this is normally no problem for Filebot.
--def excludeList=amc-input.txt Keep a list of previously processed files to be ignored in future runs (if you run this script on the same files repeatedly you must enable this option)
Also thanks for the heads up on the exclude list, i put that in as well. Should I use the exclude list as well when periodically fetching missing subtitles? That kind of defeats the purpose of it.
1.
In the amc script --def excludeList makes sure no files are processed twice, so that files that cannot be processed aren't processed (and fail to be) on each single call.
2.
The main issues is similar to your periodical fetching of subtitles. You shouldn't. Suppose a proper subtitle is never added? It'll still check every day and fail every day and this is what gets you banned. You can either try to figure out some logic, like once after 1 day, then after 1 week, and then 1 month, and then give up. If you wanna "abuse" OpenSubtitles everyday you can probably still do so, though I recommend donating lots of money to them, just to be polite.
The def excludeList script works properly now as far as i can see so files downloaded to this folder are only processed once. Subs are turned off for now (no biggie for me). Thanks for the digital-asshole prevention
Quick question, I actually was wondering about this from the start, but in the tutorial you are using --action copy, witch will indeed run over the same files over and over again.
I am however using --action move, and my script will only process new files, and is run once everyday.
should I add the excludelist parameter to my script:
What happens if for some reason some file can't be processed and thus isn't moved?
There's no downside to using --def excludeList just in case something unexpected happens. Alternatively, you could have additional scripts take care of getting rid of files that are still there after processing in some way, but on Windows, any kind of extra scripting tends to be extra painful.