Custom Scripting

Final Cut Pro to Final Cut Server Metadata Transfer

Having metadata available for editors to be able to search for footage within a Final Cut Pro project is essential to many editorial workflows. Unfortunatly, once the project and clips are added to a Final Cut Server that metadata remains only with the project and its associated elements. The metadata does not automatically follow the clip into the asset. This issue has caused a lot of problems and confusion for people who traditionally have been entering metadata during log and capture or in their Final Cut Pro bins. That metadata is very valuable and needs to be able to be attached to the asset if you wish to be able to search and/or automate based on it.

This was the basis for creating the Final Cut Pro to Final Cut Server metadata transfer script. This script simply retrieves all of the metadata from a Final Cut Pro project file and enters that metadata into each asset in Final Cut Server which is a part of that project. This metadata can be accessed through a special Final Cut Pro Metadata group on any asset after running this script.

Check out the video below to see how it works, and call Jason Perr at MacHarmony for more information on purchase and installation.

Final Cut Server Bulk Metadata Changes

Being able to change metadata across multiple fields simultaneously is another often requested script that we have created for a number of clients. Our most recent iteration allows for very easy manipulation to configure it to transfer any metadata field from a production to all of the assets contained within it.

Check out the video below to see how it works, and call Jason Perr at MacHarmony for more information on purchase and installation.

Final Cut Server to Final Cut Pro Metadata Transfer

This script simply does the opposite of the previous one mentioned. With this script any metadata that is set in Final Cut Server can be transfered into a Final Cut Pro project so that it becomes available in the Final Cut Pro bin. Check out the video below to see how it works.

Export Metadata From Final Cut Server To CSV

Metadata is very usefull within Final Cut Server to search for assets and to cause a lot of great automations to happen with assets; however, a lot of times that metadata can also be very usefull outside of Final Cut Server for the purpose of generating reports. The reports can be complete reports of everything we currently have, a report about certian metadata fields that pertain to a specific set of asssets we may be sending to someone, or a wide variety of other possibilities. This video shows an example of one way in which we can use Final Cut Server to generate a rather robust report for a given asset or set of assets.

Custom Scripting Overview

MacHarmony works with some of the top programmers in Los Angeles and around to country to create some of the most advanced custom workflows seen in the world of Final Cut Server. Many of our clients have asked for similar scripts, and others just getting started have asked for examples of what kinds of things are possible. Below is a list of just a few of the more popular scripts that we have written and implemented in currently operating Final Cut Server digital asset management systems. Please contact Jason Perr at This e-mail address is being protected from spambots. You need JavaScript enabled to view it if you have any questions or would like a demo of any of these scripts.  Video will be posted soon showing the functionality of many of these scripts.

We offer our services to create custom scripts specific to your company and your workflow.Our philosiphy in programming is that no idea is too crazy and nothing is impossible. Please let us know what you wish your asset management system can do. 9 times out of 10 we can probably make those wishes come true and more.

1. CSV Import/Export Tools
- Create Dummy Assets (not connected to any real video files) based on CSV information
- Create real Assets based on CSV information that includes asset location
- Create Asset and Backup asset based on CSV (intended for client generating 56 assets every 5 minutes that wanted users to be able to delete assets but retain a backup copy with all the metadata)
- Import metadata from CSV file to assets and/or productions currently in the Final Cut Server Database
- Export metadata from Assets and/or productions in Final Cut Server to a CSV file

2. Final Cut Pro Integration
- Import metadata from all Final Cut Pro clips in a FCP project into their appropriate assets in Final Cut Server
- Get metadata from Final Cut Server Assets into Final Cut Pro clips (readable in the FCP bin and timeline)

3. Subclip Creation Tool
- Generate new assets based on timecode in and out points along with descriptions and meta-tags generated in the annotations window of FCSvr. (Can be used by anyone with VPN access to the server)
- This tool can create new assets based on the timecode information, with metadata, as well as a titlecard over black generated for a specified period of time at the head of the new clip
- This new clip can be a standalone complete clip, or can be a quicktime reference file so as not to take up any extra space on disk.

4. Asset Reporting Tools
- We have a number of tools that we have created to generate reports on a given schedule based on any kind of database information
- examples
- Report all assets used in a final cut pro project created in the last month
- Report all Assets used in a Production
- Report all assets currently part of a specific metadata set
- These reports can be generated automatically and emailed automatically to a list of people who need to see it on an ongoing schedule.

5. Transfer Metadata Set
- This script is used to transfer any asset from one metadata set to another along with all of its current metadata.

6. Transfer Metadata from Field A to Field B
- Simply transfers all metadata from one field to another across the whole database or across any specific metadata set.

For any questions on scripts please contact Jason Perr at This e-mail address is being protected from spambots. You need JavaScript enabled to view it .