VES Camera Report
VFX productions have been using multiple vendors for their VFX work for many years now. Additionally there is increased pressure from the production to keep the number of on-set people to a minimum, so VFX Studios need to rely on production crewed data-wranglers to record the camera reports for the VFX studios.
This frequently results in completely different types of camera reports been given to the studios. Each which have their own challenges in how the studio should ingest them. This becomes part of the hidden cost that cannot be passed onto the client, but yet the VFX Studio needs to absorb.
The goals for developing the VES camera reports:
The initial deliverable will be a filemaker-12 database, but we would like to explore other options, especially if it allows better integration directly with the digital cameras. The key advantage of filemaker 12 is that the ipad client is now free, which lowers the barrier for some productions.
Key Interface Guidelines
The database needs to be easy to extend, making it easy to extend certain types of fields (in particular checkboxes related to what's on set, or what is being recorded).
Wherever possible, fields should be selection lists to help with rapid (and accurate) data entry.
The ipad screens should be designed for easy display and entry using fingers, which mean the font-size and boxes should be quite a bit larger than normal.
We plan to split the scenes and takes into separate tables, which should make it easier to handle an unlimited number of takes per scene.
Additionally we have tables for the following:
The default export format will be a single CSV file, where we will merge the scene and takes. The take fields will be prefixed by “tk” to make them easy to identify. The first line will include the file fields. We are actually going to be using a mail-merge format, which is mostly CSV based, but there is some special handling of some characters.