FileBot

Hi - I'm looking for software to keep my media server clean and organized for Plex, and after difficulties with Hazel, tried FileBot. I'm running Mac OS X/Maverick on my server.

1. How do I use relative (or absolute) directory structures to rename/move files? e.g. I have files to be moved in my Downloads directory, so I was using ../Television/Showname/Season Nbr/New Name but I got a directory access error. I also tried /Users/username/Television... etc. but got the same error. How do you move from one directory to another on Mac OS?

I should note that I get the "Drop 'em to Unlock 'em" error. And now even though I removed the directory info, I get it all of the time. So I can't even change the names manually. And I'm logged in as admin and there are no funky permissions issues on my directories.

2. How do I automate FileBot to run on an hourly basis?

I would have much preferred a demo copy first. I thought the software could do more than it seems capable of doing, and am now unhappy I shelled out $5. Please help, or I'm back to Hazel (ugh).

1.
FileBot in the App Store is a GUI application. App Store applications will run in a sandbox and need to ask for permission before accessing files. Screenshots and more system information would help.

I'd suspect that especially when running as admin you will have more funky permission issues, especially when app sandboxing is involved. So you're running as admin user, trying to mess with files in another users home folder? The app sandbox would naturally prohibit that.

I've run some tests and it all works fine. What's your format exactly?

Absolute format: Relative format:

2.
App Store apps cannot include console tools. If you require more automation (i.e. the filebot console tools) then you can use brew to install those:
http://www.filebot.net/forums/viewtopic ... 049#p11797

The filebot console tool can then be called by Hazel, Automator, Scheduler, any torrent client, any other program. There's lots of tutorials here in the forums. brew will also setup the non-App Store package so if you can't get around the funky permission issues on your system you could try running that instead.