Logging with backLogger
In the backLogger application you can log already shot, but not logged footage using Lumberjack's keyword logging system. See below for instructions on how to log multicam/multiclips in backLogger.
The backLogger interface includes the Web Logger, so operation is the same as logging in the Web Logger, except that media selection and playback controls are added.
If you do not yet have an Event, Create an Event.
Sign in to Lumberjack System in backLogger's web interface.
Note: The computer running backLogger must have an active Internet connection.
Click 'Open Media Folder' and select either:
The media files will populate the list below the player.
Select a media file and click play.
Log the file by setting Keyword Ranges while the media file is playing.
New for Version 2.0: You can pause, rewind, fast forward or scrub the media file and the Keyword Range will match the logged times.
Once you have a clip selected in the player for backLogger you can control it using the keyboard, or by dragging the scrubber bar.
Logging existing Multcam Clip footage requires a slightly different workflow.
The Lumberyard application applies logs to Multicam Clip footage using the media time of the first angle in the Multicam Clip.
Locate the media file for the first angle - either by opening the file directly in backLogger, or by exporting an XML from your Final Cut Pro X Event - and select that file in the backLogger interface.
Log this media file as normal in backLogger. Continue to log the first angle from other Multicam Clips before finalizing the process, as below.
Import the media to Final Cut Pro X, and export an XML file to Lumberyard in the normal manner.
Open the Event XML you used for backLogger into Lumberyard and export the Logged Event to Final Cut Pro X.
backLogger uses an AVFoundation player that does not natively support Red Digital Cinema R3D files. However there is a way to use backLogger with R3D files:
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.
Copyright 2014-2017 Lumberjack System, Inc