Hey @seanvree. I wanted to thank you for the work you have done so far on this - it definitely helped give me a better picture of how all the different pieces need to interplay to get this working. I will admit I was a bit frustrated by some lack of clarity in your guide however. I’m sure that it took you a few drinks to get this all working and I know putting a guide together like this is a chore mostly for the benefit of others. So again, thanks.
That being said I would like to offer some constructive criticism and suggestions on how to make this better and hopefully the next person won’t stumble through all the same blocks that I did.
I’ll try to go in order of the guide - though some things may be out of place.
-
Most importantly…link this guide at the very top of your other guide so people don’t waste time with the other method.
-
It isn’t really clear (in either guide) that all these steps you are taking are:
a) because you have a separate seed box machine
b) because you are trying to seed the files and want to avoid locks
Yes you do mention in passing that this guide solves all those issues, but not everyone who wants an “auto-process .rar” solution is going to have that configuration. Many pieces here are overly complex or simply don’t make much sense if you don’t fit the above criteria. It would be very helpful if you both explained clearly that is your setup at the onset AND commented on each piece as to what part of the puzzle it solves so that those who don’t have that particular challenge know that they can skip it/go an easier route.
-
The directory names you have chosen are confusing. Calling the directory “drone” confuses the issue since we are specifically doing away with the drone folder. I know this is just semantics, but it does muddy the waters. Personally I call my folder “processing”, but anything to distinguish it as “not drone” would be better.
-
You don’t stay consistent with your directory names. You show your tree structure up top, but then down in your autoproecssmedia.cfg and log files you have a different structure. This makes it very difficult for people to follow how you should set up the autoproecssmedia.cfg.
-
On the same note, the section for configuration of the autoproecssmedia.cfg is difficult to follow. Part of it is the naming I mention in #4, part of it is the bad color coding the site here does to it. And part of it is the wall of text with no real indicator of what specific variables one needs to set.
-
While we are on autoproecssmedia.cfg. I’m pretty sure the default_downloadDirectory is optional and probably will never come into play with how this is configured.
-
In you section “6. Process explanation (How this shit works):” your two flow examples could use a little clarification. I believe that step #5 in the non-Rar flow “Sonarr doesn’t import because the remote path is EMPTY.” should also be step #5 in the rar flow. I know Sonarr wouldn’t import anyway because the files are archived, but that doesn’t mean that the workflow step isn’t there. You should try to mirror the text in both workflows to be exactly the same except where they actually differ.
Another example here is your step 10/9 in the two flows. In both cases sonarr “Sonarr imports, post-processes, and MOVES release to final destination.” Just because the file isn’t a rar doesn’t mean that the NTM script doesn’t act on it. For example it may download subtitles for a file that is already an .mkv. Likewise, in both cases sonarr does additional post processing in the form of moving and renaming the files.
I know this seems minor, but when you are looking at this through fresh eyes little omissions/differences like this are very confusing as to how they should be interpreted and what is responsible for what.
-
The section on the code change to autoProcesstv.py. A change like this is a big deal (since as you state it may be lost on upgrade of source). It doesn’t hurt to point out here again exactly what this is being used for and why you probably don’t need it if on a single box config.
This is the one thing that I think I can offer some additional assistance on (rather than just nitpicking 
). You can actually get around this by writing your bat script as follows:
if /I %3==D:\queue\processing\tv\torrent\\ (
"d:\Program Files (x86)\nzbToMedia\TorrentToMedia.py" %1 %2 %3
) ELSE (
# do nothing
)
Ofc you would substitute your path for mine above (after the %3==). This way even though the deluge script will always execute, it will only actually run NTM for torrents in the appropriate directory. Less processing and cleaner logs!
Well, that’s about it for now…it is really late and I’ve been working on this whole configuration for too long today. I’ll probably read this over again in the next couple of days so would appreciate your feedback and if you care for any more of mine (if I have it).
thanks again.