And the UI on both shows the simple aesthetic shared by the developers. Set up FCPX production and new FCPX library from template connected to proxies in Postlab drive.Uploading finished proxies to Postlab drive using Hedge. Making re-wrapped in MOV files from the original camera MXF files using Kyno and then.Hedge to copy camera cards two external drives on set, and then Hedge copy the drive to Xsan.While we are exploring various workflow automations we are currently doing the following steps manually. Testing with other tools is always ongoing and during a recent test of the workflow we also tried EditReady from Divergent Media. We are using two other tools in our remote ingest workflow currently: Kyno from Lesspain software for rewrapping and converting camera footage and Postlab, the remote collaboration tool for Final Cut Pro (and Premiere Pro). It also has an API which made it easy to build an app that configures Hedge for its current task, and AppleScript support for extending automations after specified actions. This is very nice and very useful for troubleshooting. It verifies, and double checks its work and leaves receipts. Hedge has an easy interface to copy multiple sources (camera cards, usually) to multiple destinations (two external drives, or two SAN locations etc), and it does it well. Why use Hedge? A nice simple app which hides its complexity well. We use Hedge to copy camera cards to multiple drives on set (or after a shoot if on location) and then we use Hedge once more to copy one of these drives to the office shared storage (Appleās Xsan). This is a snapshot in time of what we are trying now. I am always testing new tools and methods, so workflows change all the time. Note: I want to explain how our current workflow for editing remotely. For the new proxy workflow with FCPX 10.4.9 and Final Cut Pro 10.5 see my new blog post Update: This proxy workflow applies to Final Cut Pro 10.4.8 and earlier.
0 Comments
Leave a Reply. |