The present and future of post production business and technology

Software Product Updates

We’ve recently added new features to SendtoX – named Favorite ranges from Clips in a Sequence – and Lumberjack System where we developed a workflow for backLogger to support RED R3D media.


We added a new SendToX feature after we had been consulting on the best way to translate some logging from Premiere Pro CC to Final Cut Pro X. The logging was a little unusual because the original editor had strung out clips in a timeline, cut out the dross and renamed the good clips according to their content. Valuable metadata we didn’t want to lose in translation.

As each was unique they were not a good candidate for conversion to Keyword Collections as each Clip would be alone in a Keyword Collection.

That is why there is now a Preference setting to translate clip ranges from a Sequence to named Favorite ranges on the Clip in FCP X.

Update to the latest version and check out the Preferences.

Lumberjack System

We recently discovered that the AVFoundation player we used in backLogger did not support R3D files. But there is a way to use backLogger with R3D files, if you generate proxies in FCP X. It’s a simple solution.
  1. Import your R3D files either into a Library or into an external storage location (do not choose “Leave files in place” when importing or backLogger won’t be able to find the proxy files)

  2. Inside Final Cut Pro X choose File > Transcode Media… and generate Proxy files
  3. Once transcoding has finished, export .fcpxml for the R3D files
  4. Import the .fcpxml into backLogger, and it will process the XML file to find both the .r3d files and the generated proxy files. 
The file list will have (Proxy) after the names of files where matching proxy media was found.
When you select a file for logging the backLogger media player loads the proxy, but uses the creation date timestamp from the R3D files, to create the logged keyword ranges.

There’s actually no information about proxy files in the XML, but if the originals and the proxies are stored in the same library or capture folder then their relative file paths can be determined. This is why “Leave files in place” doesn’t work.