Never mind. Simple typo. Was missing the 't' in 'minLenghMS=0'. Sorry for taking up your time.

Hey all, The issue is this: I have a number of videos that filebot skips claiming they are too short when they do not appear to be so. The videos do fall below the default minimum length and filesize for filebot to include it in processing, but setting minimum filesize and length to 0 ought to fix ...

Thank you for an excellent tool, by the way.

I ran my first 20 executions or so manually, watching the log, not trusting it to do the right thing.
I was proven wrong. Filebot really just works! (so far )

Yes. I was just stupid and assumed during testing in an interactive console, that the ANSI codes would be in the log if filebot were to be called non-interactively. d'oh!

Thanks for the comprehensive answer :) For some odd reason I assumed that piping and redirecting would also include the ANSI codes. Good design that they don't [thumbs up] Here's what I end up doing, should anybody want to know: $ filebot -script 'fn:amc' [...a lot of options here...] --log all ...

Would it be possible to include an option to force plain text output of the logfile specified with the option?
It would be desirable, as it would result in more readable logs in less capable terminals and obviate any need for later removal ansicodes if so desired.