I created a cmd file to call FB for post-processing. The script runs fine and completes the rename and file movement but the status in the sabnzb history still says failed.
My FB script moves the file to my Google Drive which is mounted as a local drive using Netdrive 2
As you can see it says done in green...but followed by some weird characters...
FileBot is working fine, and seems to have finished it's task succesfully. Your console encoding is off though. Also, the GUI launcher doesn't have a console so the fact that you get output at all is strange.
This is clearly about how to integrate 3rd party tools with sabnzb, so you should ask the sabnzb developers for some docs on that.
1.
This log message will only be printed when you pass in --log ALL (default) so you could just define your own log level that is higher, for example FINE or INFO.
2.
If sbanzbd can't deal with ヾ(@⌒ー⌒@)ノ printed to console, then you may will have similar issues when FileBot logs unicode filenames to the console.
Looks like FileBot is using UTF-8 encoding and Windows CMD is interpreting the bytes with Windows-1252 encoding.
I'm not sure that CMD can display Unicode characters at all actually. If you pipe the output to a text file and then look at it with good Editor you'll probably see that it looks just fine.
rednoah wrote:Looks like FileBot is using UTF-8 encoding and Windows CMD is interpreting the bytes with Windows-1252 encoding.
I'm not sure that CMD can display Unicode characters at all actually. If you pipe the output to a text file and then look at it with good Editor you'll probably see that it looks just fine.
Yup it does look good in the log file. Well its all good, i added the --log Fine and no more issues. Thanks Rednoah...you always dive great support