Move a Kyno shoot into a smarter logging workflow

What you gain

Keep the browsing habits you like and put ClipLogger’s subject lookup and logging suggestions to work on one Kyno shoot.

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. There is no direct Kyno metadata-folder importer. Preserve the old XML and exports, then recreate the fields and ranges that matter in your first ClipLogger shoot.

1. Bring the files and keep the old log

Copy the shoot with Kyno’s hidden metadata folders intact. Retain a shot list or supported metadata export, including subclip names and in/out points. Open the camera media in ClipLogger; browsing the folder does not require a Kyno catalog conversion.

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

Keep Kyno for a camera format or transcode it handles well. Use supported originals or clearly identified derivatives in ClipLogger for roster lookup, palette-driven suggestions and source selection. Keep original paths and timing with any derivative so the editor can relink.

Kyno is not a subscription trap: its purchased version remains usable without renewal, and it stores user metadata in XML inside hidden folders beside the media. ClipLogger’s advantage here is free entry and the richer logging workflow, not a claim that Kyno takes your metadata away. Keep Kyno’s metadata folders with an archive; write ClipLogger sidecars for the new work.

Keep a way back

Your Kyno license and original metadata remain usable. Keep the unmodified shoot and its hidden metadata folders until you have checked playback, names and the receiving NLE export.

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 Kyno comparison for capability and cost details.