ClipHow do I hand a cut order to my editor?
Arrange the relevant clips or ranges in a Reel string-out or supported project sequence, then use its export action. Inspect the resulting FCPXML and any companion cut-list output in the target NLE. Validate source relinking, order, range boundaries, frame rate, and audio before repeating the handoff across a full production.
Can ClipLogger edit the sequence after export?
No, deliberately. ClipLogger is an organization and handoff tool, not an editor. Sequences are frozen at the FCPXML/EDL boundary and finishing happens in your NLE. That boundary is what keeps the app honest about its job: everything before the cut, nothing after it.
How do markers travel?
Marker handoff depends on the receiving format: the app has XMP, FCPXML, and Resolve-oriented marker paths. Check the menu and output used for the target NLE, then verify marker text and timing on a short sample. Timeline timecode and source timecode are different contexts; do not silently substitute one for the other.
What's the Resolve round-trip?
Enable the relevant Resolve CSV export and import the resulting metadata into a test Media Pool. Match the intended clip names and inspect the fields you rely on after the import. Finalize any planned source renames before relying on name-based matching. This is an outbound handoff; there is no general Resolve-project importer back into ClipLogger.
Can I import spreadsheets into the logging system?
The established spreadsheet import is a code-to-value lookup or roster workflow. Map the code, display value, and useful detail columns, then bind the lookup to its intended field. This is not a generic importer for arbitrary clip-level metadata from another DAM. Preserve exported catalog data separately until a specific mapping and importer are available.