hi jason, the idea of the sd and hd folders is as follows:-
sd folders - this was a way of moving my collection over from sd material (dvdrips) over to hd material (bluray/hd-dvd), what i set it to do is check the sd collection against the hd title (assuming im downloading hd material), if it matches then i must like the movie (i.e. i already have it thus its ok to download and can skip checks) and i can then delete the sd movie manually and replace with a nice hd version :-).
hd folders - the hd folders is simply a check to see if the movie already exists in my collection, if it does then skip the movie as i already have it.
i admit its probably the one part of the script which is very particular to me, so i may change it to be more flexible for other users with different needs.
as to your second question, yep im using https throughout as your login and password credentials are sent thus its gotta be ssl.
im really glad you like the script, ive put a LOT of time into this, i started off with no programming skills so its taken me a long time to get this far :-)
if you have any other questions let me know.
Even more awesome. :) I keep my movies sorted the same way, so it works well for me too. :) I didn't notice in the window output any log of it parsing through my entire directory though the script moves quickly, so I could have missed it. Do I need to enable this feature in the config.ini file other than listing the directories and the # of each?
What exactly is the script checking against when it goes through the file list? i.e., my structure is like this:
HD Movies Dir
-> Movie Name Dir
-> Movie Name.ext
-> Movie Name.nfo
-> Movie Name-trailer (etc)
SD Movies Dir
-> (Same structure as HD)
First, is this structure supported? (i.e. does it scan recursively?) Secondly, I use scripts to rename the movies to a more "clean" title (i.e. the IMDB title) once they are put in my final movie storage area and also change the NFO file to one that contains movie metadata info, so they won't maintain the exact same name as they were when first acquired. Once changed, is the script still smart enough to find/match them, or do they have to maintain the same filename/NFO/NZB as when downloaded?
Last question (for now) :), for the IMDB queuing section, is the idea here that you define a genre that you are more interested in than average and ask it to download and store all NZBs, but keep them in a "holding area" before committing to actually DL them by putting them into your watched folder? i.e. these -might- be movies you are interested in, but it's not as definite as those in the "good" category. Assuming that is the case, is it queuing up the IMDB "preferred" genres from the section above as well, or are those instantly downloaded vs. these that are just queued?
So the order of preference and function of each section would be:
IMDB Good -> These movies meet the highest standards and in any case of a match, we put in the watch folder and DL.
IMDB Preferred -> Allows certain Genres to be named with lower rating standards than the general "Good" standards. When the rating standard and genre are a match, instantly move to watched folder.
IMDB Queued -> Pull NZBs for all movies that meet a mix of Genre and Year criteria (rating criteria ignored, year criteria is a "max" year as opposed to min year in the general "IMDB Good" settings). Script places these movies in a separate location to be manually reviewed and manually moved to the watch folder once the user confirms s/he is interested.
IMDB BAD -> We never download these even if they happen to meet some other criteria above.
I realize some of this is obvious, but I figured after I started asking questions about 1 or 2 of these, I'd just as well write it all out so that it's clear to future visitors what each one does. Assuming it's correct, feel free to lift this for updating your readme or the first post.