ElmoOxygen

Regardless of where the files are physically stored, any operating system (Linux, windows, OS X, etc) looks at where it *thinks* they are and then decides to read / write the file to a new location, or to merely rename it to the location. In this case, the mount points are different for the input and the output. Linux (and windows / OS X) doesn't realize that the source and destination are actually on the same physical hard drive. Hence why it does the read / write instead of a rename. Its just how all operating systems operate. I'm not familiar with filebot, so I can't tell you if you set the same mount point for your input and your output if it will work (ie: use different folders within the mount points) Thanks, that helped me solve my issue. I just stopped using the input folder, grabbed files from output and renamed to output. No more waiting.

I'm pretty new to using filebot, love how much functionality it has, but am having some trouble getting things to work how I want. My folders are set up like this: input: /mnt/user/Downloads (folder is cache only) output: /mnt/cache/ Filebot simply renames and moves everything to the root of the cache drive so that mover can work its magic. Everything is moved within a single drive, so I would expect the renames to happen instantly, but for some reason the files get rewritten to the disk, taking a fair amount of time. Does anyone know what I can do?