You mentioned that the utorrent script already does plenty of logging. What is the path to the logs or even just the file name so I can search for it? Im on a headless ubuntu system.

How is the name of the movie determined? So far its gotten 2 out of 3 movies wrong when I am using it with the uttorrent script. Is it even looking at the NFO file or the folder name or is it mainly looking at the video file name?

Nice work. That fixed it! Thanks for your great app!

I already admitted to the typo so thats why the command was not completing as the folder was empty (aka, it didnt exist because the path was wrong). My point is that your update didnt get rid of the x11 warnings.

Nvm, i had a typo. So while things do work, the new jar doesnt seem to make a difference with the X11 warnings. I replaced my /usr/share/filebot/FileBot.jar file with the new one. I left the change you mentioned in my /usr/bin/filebot startup file as well.

hmm, doesnt the utorrent script do extracting though? The folder is full of rar files and an nfo

I dont see an r1444 in that list. Am I blind? Also, you were right that it it was working despide those warnings, but now when I have my fully completed command, it doesnt appear to finish. It says it does, but I cant find that anything has been done. Is there a debug option? macscr@server:/media ...

didnt seem to make a difference. =(

Apologies for my ignorance, but which startup file?

Is X11 required when using Filebot through the CLI? Im currently trying it from an ssh session and i get the following warnings: macscr@server:~/autoprocesstv/delugeScripts$ filebot -script fn:utorrent-postprocess -non-strict --def ut_kind=multi --def 'ut_dir=/media/Storage/torrents/incomplete ...