Shypike, I am downloading on a Windows box, and want to move the final files to my network NAS. I want to repair/unpack the files locally on the Windows box, and move the final file to the NAS (since repairing/unpacking directly on the NAS is much slower, since it's being done over the network).
I think I raised this subject on this forums while on the 7.0 beta cycle, and I was told this was how sab already did it, that I just needed to specify a directory on the NAS for completed download folder.
I took the answer as correct, but during some unpacks today, and noticed, that repairing/unpacking is done on the NAS directly. And after everything is done, the files are just moved up one directory (the temporary unpack directory).
While sab is reporting unpacking xx/xx, there's a temporary directory on my NAs, where the file is being expanded...
Is this something that could be tackled on a future beta? Using the "temporary download folder" to repair/unpack/expand the files, and when they're done just move them to the completed download folders (compared to repairing/unpacking/expanding on the completed download folder directly).
I ran some comparisons between unpacking directly on the NAS, or doing it locally, and then moving the resulting file to the NAS (using a post process script), and I managed to shave several minutes (specially on big files).