workflow

String-outs without an NLE

A string-out is a reading tool for the whole shoot, and the order it produces leaves as FCPXML while the metadata keeps moving.

The first watch of a shoot does not need a timeline; it needs a reading surface. For years I used an NLE anyway: import everything, lay the day on V1, and spend the morning building a selects sequence that was a viewing device with a render bar. The reading was the real work, and the timeline was overhead that quietly turned watching into editing before I had seen the day even once. Cutting instincts arrive early and uninvited. A reading tool holds them off until the material has had its say.

A reel you read, not cut

ClipLogger's Reel mode treats the shoot as something to read. Strips layout gives every clip its own filmstrip row, the day stacked top to bottom like a contact sheet, and hovering a row peeks it, so you taste a clip without opening anything. String-Out goes further: the entire filtered set laid end to end as one continuous strip with a playhead, scrubbed in place like a single timeline, ninety minutes of material under one bar. It is not an import and not a render; it is the current filter, in order, right now. Change the filter and the strip re-forms around the new set: ceremony only, B-cam only, everything still unlogged. That is the difference between this and the selects-sequence ritual: the NLE version is a construction you maintain, this is a view you ask for. It reads like a timeline but behaves like a table of contents, and since nothing about it is a cut, it never demands cutting decisions you are not ready to make.

Watch the whole day once

The habit underneath this transfers to any toolchain, including a free player and a notebook. Before forming a single opinion about the edit, watch the day start to finish in shooting order, at speed, taking timestamped notes as you go. Shooting order carries information no bin sorted by filename has: what the light was doing, when the crew got tired, which setup the director kept returning to, where the energy actually lived versus where the schedule said it would. Editors who skip the first read pay it back in week two, re-discovering material they technically already had and re-litigating choices made on a partial picture. One honest pass through everything, then opinions. It costs a morning, and it is the cheapest morning of the whole post schedule. Tools change the cost of the discipline: a string-out makes the read faster and lets it leave marks. They do not change the discipline.

Cull as you read

A reading tool should still leave marks, because the first read is when judgment is cheapest. The string-out carries bulk-action rails, so flags, ratings, and rejects happen in place while the strip plays, no bouncing back to a grid, no losing your position mid-day. Culling here is honest in a way grid culling is not: you see each take in the company it was shot in, between the take before and the take after, so "best of the four" is an observation instead of a guess. By the end of one pass the day is triaged, and because every confirmed value drives the filter, the next string-out can be flagged takes only. That strip is a rough assembly nobody built: the day, reduced to what somebody vouched for, in order.

The sequence freezes, the metadata keeps going

When the order starts telling the story, the reel stops being a reading tool and becomes a handoff. Export it and it leaves as FCPXML; a project sequence leaves as a trimmed FCPXML timeline with an EDL written beside it, timecode emitted in the clip's real dialect, drop-frame included, so the conform lands where it should. Markers travel their own roads: an XMP comment track that Premiere's Markers panel lists, the metadata FCPXML for Final Cut, a dedicated marker EDL for Resolve. Then the boundary, and it is deliberate: the sequence freezes at export. ClipLogger will not trim it tomorrow, because it is an organization and handoff tool, not an editor, and the honesty of that line is worth more than any feature that would blur it. Finishing happens where you already finish. The metadata is the part that does not freeze: keep confirming values next week, rename for delivery, rebuild a sharper string-out from better filters and export again. Sequences are snapshots of an argument at a moment in time. The understanding underneath them keeps compounding, which is exactly the asset the next export gets built from.

Read the shoot as one strip, send the order out as FCPXML, and let the sequence be the only thing that stops moving.

← All articles