A standalone narration file can be trimmed close to the first word or include silence that preserves its place on a larger timeline. Both can be useful, but they are not interchangeable. When speech files will be delivered separately, agree the start origin and end duration that the receiving editor or playback system expects.
This is especially important for a set of short cues used in a presentation, interactive tour or modular film. An unexpected silent lead-in can look like a delayed response, while removing intentional timing can place the voice too early against the picture.
Distinguish a cue from a timeline export
A self-contained cue may need to begin promptly when selected. A timeline-aligned file may intentionally start earlier, with silence before the spoken passage so it can be placed at a shared origin. Ask the receiving team which convention it needs and describe that convention in the delivery brief.
Adobe's export guidance distinguishes selected-range exports from whole-session exports. That is a technical means of creating different boundaries. It does not decide the appropriate timing for your application.
Keep speech completeness separate from padding
The team should preserve the full performance at the start and end of the spoken material. Once that is secure, decide how much additional silence belongs in the delivered file. Do not ask for aggressive trimming simply because the visible waveform contains quiet space; some of it may be intentional timing or natural decay.
Equally, avoid retaining a long session lead-in in a file labelled as a ready-to-play cue. The recipient may reasonably assume the first audible word will follow its trigger without an unexplained wait. A delivery note should make any deliberate delay explicit.
Use one convention across the set
If several files share a common timeline origin, keep that relationship consistent. If they are independently triggered, identify their expected behaviour individually. Mixing conventions without clear labels creates unnecessary assembly work and can produce mistakes that sound like a faulty playback system.
A hypothetical workplace orientation uses spoken descriptions at several selected locations. Most cues begin shortly after the viewer chooses them, but one exported file retains a long session silence. The receiving team initially thinks the cue is missing. A file-boundary review identifies the mismatch and produces a consistent cue set before launch.
Test in the receiving workflow
A desktop player may not reproduce the timing behaviour of the intended application. Ask the receiving editor or platform owner to test representative files, including the first cue, a short cue and the final one. Confirm how the system handles completion before triggering the next item.
If a revised line changes duration, update any timing-dependent references. A correct new recording can still leave the surrounding sequence wrong if the old duration remains assumed elsewhere.
Acceptance questions include where time zero belongs, whether leading silence is deliberate, how the end is defined and whether the receiving workflow has demonstrated the agreed behaviour. These details turn a folder of speech recordings into predictable production inputs without forcing every use into the same trimming convention.
Discuss the production
Contact Live Images to discuss the proposed film, intended audience and audio requirements. Confirm suitability, scope and availability for your particular brief.
Editorial note
Original commissioning guidance prepared with AI assistance. Examples are hypothetical, not completed Live Images projects. Search intent is an editorial hypothesis, not measured demand. This draft remains unpublished.