AS Batch Renderer 0.8
Requirements:
- It's 10.5 only. I can't test it on a PPC, so I'm not too sure what it will do on that platform. I have only tested it with AS Pro 5.6.
Features:
- Can render both files and folders. Simply drag and drop 'm in the list.
- Creates a directory for the finished renders. Each render will sit in a date and time stamped folder.
- Settings will be retained between sessions.
Instructions:
Area 1 is where you drag and drop your .anme files or folders containing .anme files.
When rendering folders, AS Batch Renderer will search through the entire directory of a folder and render every .anme file it sees. It will filter out all files without the .anme extension, so don't be nervous about leaving any non-anme files around. Obviously, every file that's in the directory needs to be looked at = takes up time, so maybe best not to drop your entire HD in the list
. You can always remove items from the list using the backspace key.Area 2 is pretty self-explanatory. The settings here apply to all items in the list. You can't have separate settings for individual items in the list.
Area 3 is where you choose the destination folder for rendering. AS Batch Renderer will create its time-stamped subfolders in this location. If you leave the textfield empty, renders will be saved in the same location as the .anme file, which is to say, it will behave the same way as AS' own batch render window.
Area 4 Does exactly what it says on the tin, it renders.
Known Issues/Facts:
- If items appear more than once in the list, they will be renderer multiple times.
- Items can't be re-arranged in the list.
- Once the render process has started, AS Batch Renderer's interface becomes unresponsive. It can't be stopped other than by Force Quitting.
- It assumes that you keep AS in the default location, inside the applications folder.
- You can't use spaces anywhere in the pathname of the destination folder. It's a command-line thing. There's probably other illegal characters.
Feedback:
I would greatly appreciate some feedback. Some things to look out for:
- Any unexpected behaviour in the user interface.
- How does it deal with large workloads, haven't had the chance to test that.
- How does it perform over a network? I haven't had a chance to test that out. I would recommend caution if you want to test this out.
- Does it do what it says it does? Does the "Anti Aliasing" button indeed switch the anti aliasing on? Or does it work the wrong way around?
- So far I haven't had it crashing on me. But should it happen, please write down exactly what happens. Same of course goes for error messages, which are more likely actually.
Feature Requests:
I'm open for any requests as long as they're reasonable. I'm sort of anticipating two requests, so let me deal with them straight away:
1. I don't own a PC or a Linux machine, so I'm afraid I can't develop for those platforms (and I don't know how to either).
2. Network rendering may also be a bit too ambitious. Believe it or not, this application is really just an Applescript with an interface stuck on it, don't expect it to be able to do really heavy stuff
