Add a searchable log to your LucidLink filespace

What you gain

Keep shared access and add the source log: known names, useful metadata and ranges that help the next editor start cutting.

You can start with the free base app and your existing storage. Use the first shoot to build a palette, identify known subjects and hand useful ranges to the editor. ClipLogger does not replace LucidLink’s shared storage or migrate its permissions. Mounted-storage behavior needs a check on your own setup.

1. Bring the files and keep the old log

Record the filespace root, user permissions, folder ownership, and the current backup process. Keep a manifest of full paths and file sizes for the pilot. Pin or otherwise make the pilot's media available using your storage administrator's documented workflow.

Use a copy of one shoot for the first rename or metadata-writing attempt. Include repeated camera filenames from different cards, and retain the full source paths so you can tell them apart.

2. Reuse the work you already did

Download the mapping worksheet. It is a checklist for your records, not a file to import into the app.

If your existing filenames already describe the shoot, open that directory and choose Learn from these files… from the palette picker. With at least three visible files, ClipLogger can infer a palette you can edit. Supported XMP fields can also be read from media; that does not convert every vendor’s custom field or AI index.

3. Give the next editor a better log

Import a roster, menu or code-replacement table for the names and terms you know. Set fields such as action, shot size and rating, then choose a small batch for suggestions. Use a supported local model for no per-clip service fee, or choose Rush for hosted processing. Review the suggested values against the footage.

Use Drill-down to see nested camera folders together. Search by meaning, transcript or the reviewed fields, then narrow the results with the values available in the directory. Mark the useful ranges and promote the ones you want to log separately into virtual clips. Search and filter guide.

4. Write something you can keep

Enable .logger.json output and confirm the sidecars have been written beside your pilot media. Preview a filename built from your reviewed fields, then apply it to the copy. Keep names stable once the editor links the footage, or plan to relink after a rename.

Open a supported export in a test NLE project. Check the actual names, metadata and source timing there. If you need a separate media file, choose subclip export; a virtual clip by itself still depends on the original. Naming · Sidecars · NLE handoff.

5. Decide what you still need to pay for

Use a mounted LucidLink folder for accessible media and keep ClipLogger’s log beside it where writes are supported. Test a small folder for reads and sidecar writes first. Analysis can trigger network reads even when you do not manually download the whole shoot. Finish naming before distributing NLE links when possible.

Download and retain the media and sidecars you want to keep before ending filespace access. A mounted file is not proof of an independent local backup. ClipLogger can continue to browse and log the retained files for free; it does not replace LucidLink’s remote access service.

Keep a way back

Stop ClipLogger work on the pilot folder and continue using the original NLE and filespace. Preserve any new metadata separately; the storage arrangement can remain as it was.

Retain the original media and old exports until an editor has used the new handoff. Back up the ClipLogger project/catalog as well as sidecars, especially when some work has not been written beside the files.

Return to the LucidLink comparison for capability and cost details.