This paper presents an introduction to the color pipelines behind modern feature-film visual-effects and animation:
- VES Technology Committee White Paper: Cinematic Color: From Your Monitor to the Big Screen. (pdf, 6.4 MB)
- Course Notes from the Siggraph 2012 Course (pdf, 6.6 MB)
More information can be found on cinematicolor.com
Authored by Jeremy Selan, and reviewed by the members of the VES Technology Committee including Rob Bredow, Dan Candela, Nick Cannon, Paul Debevec, Ray Feeney, Andy Hendrickson, Gautham Krishnamurti, Sam Richards, Jordan Soles, Sebastian Sylwan, and Haarm-Pieter Duiker.
Questions and Discussion
The VES Technology Committee has assembled an expert panel that can be reached at email@example.com with questions, comments and errata related to the Cinematic Color document and the use of color in production generally.
A key ingredient to creating high quality visual effects is the ability to recreate a digital replica of the environment in which the scene was captured. Accurate knowledge of the camera information and key measurements of the set are critical to aiding this process. The Visual Effect Camera Reports are the key record for most of this information.
Despite the fact that most studios agree on the fundamental data that needs to be captured on set, there has yet to be any consensus on a standard camera report format to record this information. We've set out to fix that.
The primary goals for developing the VES camera report are:
- Provide a known standard set of fields and a well specified format for exporting (or importing) the data.
- Make it as easy as possible for a facility to ingest camera reports and their associated data even though they may have been created by another company or production.
The secondary goals are:
- Provide baseline camera reports that productions can adopt which output the standard set of fields correctly. This will serve as a useful tool for some productions, while providing an example application for others to improve on in the future.
- Provide versions of camera reports for film and digital shoots, as well as stereo shoots. Multiple cameras are supported.
Interchange Format Introduction
The file format is a csv file, that combines slates and takes into a single row per take, repeating the slate information for each row. The take fields will be prefixed by "tk" to make them easy to identify. The first line will include the file fields. For more details see: Camera Report Interchange Format.
How to be Involved
Where you are a studio, vfx vendor or data wrangler we welcome your input. Please review the camera report specification and give us feedback. Even if you have no input at this time, please join the ves-tech-camera-reports google group.
The camera reports are available to download as a filemaker database. This is intended as a baseline. We encourage 3rd party vendors to produce custom solutions that support this format as a standard for interchange.
We plan to list additional 3rd party applications that support this interchange format. 3rd party support might allow integration directly with ingest, the digital cameras and script supervising systems, or simply a better interface than filemaker can provide.
- Camera Report Database for Filemaker 12/13 (version 2.12.)(9 MB)
- Camera Report Database for Filemaker 11(version 1.)(17 MB)
- Self-contained filemaker camera-report OSX application (59 MB)
- Free IOS Filemaker 13 to go app
- Blank camera report PDF for a paper backup (160KB)
3rd Party Integration
3rd party tools supporting the interchange format:
- Complete Camera Report Proposal
- Developer Guide if you want to adapt the VES database, or if you want to adapt your own filemaker database to export the VES exchange format.
- Change Log for the specification and camera reports
- Samples and Screen shots
Laptop entry screen:
Sample PDF output:
This is been developed by Sam Richards as a project of the VES Technology Committee, with assistance from numerous visual effects artists and data-wranglers. The original Filemaker database used as a starting point for this project was graciously contributed by Rhythm and Hues.
Security Best Practices
Deny unauthorized access to facilities, equipment and resources. Protect personnel and property from damage or harm.
- Only invite employer authorized visitors into your place of work.
- Never share your work ID badge, access fob or keys with other individuals.
- Keep sensitive physical items like scripts, props and removable storage devices locked in secure storage when not in active use.
Minimize risk of unauthorized access to your accounts.
- Never share your password or allow anyone else to use your account, you are responsible for all activity carried out by your user account.
- Periodically change passwords and always use strong passwords for all of your accounts.
- Use different passwords for content access and other services.
- Never send login and password credentials together, share the information via two separate channels, i.e. email the username and text the password.
- Keep passwords secure, never with a device containing content (e.g., a Post-It note on a computer, laptop or encrypted drive is a no-no).
Minimize unauthorized access or loss of digital content.
- Only transfer digital content using secure methods approved by your client or place of work, never by email or unencrypted services like FTP.
- Your place of work has a secure network and it is your responsibility to keep it secure by not connecting any unauthorized hardware or installing software without permission.
- Store digital content in the appropriate location to ensure it is backed up regularly.
- Only use cloud storage or backup services such as Google Drive or Dropbox for client content or other sensitive material if you have explicit approval from the client or your employer to do so.
Beware of Social Engineering
The practice of manipulating individuals to involuntarily divulge confidential information. A common tactic.
- Always make sure you read and follow the security policies provided by your client and/or employer. Never share content with people who are not approved by the content owner to receive, handle or view it. Only people who are directly working on a project may have access to such content.
- Professional profiles, such as LinkedIn and IMDB, should never include any information about unreleased projects you have worked on unless you have clearance to do so.
- When possible, always refer to projects using code names rather than the actual title.
- Talking with colleagues about your work in a public place should be done with great care and never within earshot of anyone who does not currently work with you.
What if you suspect a breach of security?
- Any suspected loss of content should be reported immediately to your employer or the content owner.
- Do not condone security negligence or breaches by others, or “turn a blind eye”; not reporting an incident you are aware of makes you liable too.
- When in doubt, please seek advice from your supervisor or technology team.
Please note: these are general guidelines written by the VES Technology Committee. Specific security policies may vary by studio, facility or production.
If you have any doubts or questions, please do not hesitate to ask your producer, supervisor or the HR department of your employer.
For more information see http://www.fightfilmtheft.org/facility-security-program.html
Feedback? Email firstname.lastname@example.org
Download the VES Security Best Practices Form
Available in multiple languages.