FileBot

Hi,

Whenever I call AMC from utorrent after download - copy works fine, Move does not, I assume from the seeding locking the file.

So I thought I would introduce a delay into the script to give time for utorrent to finish and release the file, I've tried a few various things with no luck.

Introducing a sleep command into the .groovy is no good, the script still tries to lock the file as soon as it is called.

So I tried to put the filebot -script fn:amc etc etc , into a batch file with a TIMEOUT DOS command in front for a specified time.

Problem is the %D %K and so on in the utorrent parameters, how do I then pass those along to the batch file? they seem to not be passed along correctly.

I do have log files, but I've tried so many various permutations, at this point, the log files would show 20 different outputs, and I'm wondering if theres a more general solution?

so in the utorrent Run Program field I put something like
and then in the Bat file I put;
I read somewhere after a google search that the utorrent commands such as %K etc are converted to numbers when passed to a batch file, in order of when they were called?
so I replaced them with numbers, and it jumbled up with sometimes the title being listed fine, but ut_file coming back as %F and that seemed a dead end.


I do hope I'm missing something very stupid and obvious, I have googled and searched for hours, safe to say scripting and coding of any sort is alien to me....


Perhaps I'm going about it the wrong way completely, I think I probably am, essentially, I just want the filebot script to wait until the seeding is complete, and I've probably tried to go about it in a very roundabout way.

Any Ideas?

Does utorrent have a "Finished" state that works? This switch makes the script abort if ut_state is anything but the given value: You can try setting this switch and launching the script onStateChange hopefully state 11 is in fact Seeding Finished. Just says Finished in the docs.

PS: The script most certainly does not lock any files until it starts processing them, obviously.

Hi,

Yeah I thought the solution would probably be based around utorrent rather than the script,

And as for the script locking the file - it says its being locked as soon as the cmd window pops up, although whether the script fails due to utorrent already using it, or another reason is hard to ascertain.

Thanks for the answer,

I will look more at run on state change - finished, to trigger the script, I think I was making it much harder than it needs to be.

It's locking the file it says it's locking, namely the log file, as to make sure only one filebot instance is processing at any given time.