Choose overlap based on whether both clips may play at the same time. Keep its default enabled when you want a crossfade with concurrent audio; set o=0 when the first clip must finish before the second begins. Then choose the fade duration and each side’s curve separately, and verify the rendered duration and boundary. These settings control different decisions: curves shape the transition, while overlap determines the timing relationship.
Decide the timing and set the filter
The FFmpeg `acrossfade` documentation says the filter crossfades one audio stream into another near the end of the first. Overlap is enabled by default. Its examples show o=0 for crossfading without overlap. The filter also accepts a duration and separate curves for the first and second streams.
Use this sequence:
- Mark the intended boundary. If the incoming sound must begin while the outgoing sound is still audible, leave overlap enabled. If the clips must play one after the other without simultaneous content, disable it.
- Choose a fade duration that fits the editorial moment. A longer fade takes more time at the boundary; it does not decide whether that time is shared or sequential.
- Choose
curve1andcurve2for the outgoing and incoming sides independently. FFmpeg refers to theafadedocumentation for available curve types; a curve choice is not a substitute for the overlap decision. - Estimate the output duration before rendering. For two hypothetical 20-second inputs sharing a 3-second overlap, the planning estimate is 37 seconds: 20 + 20 - 3. The documentation does not establish a corresponding duration estimate for the no-overlap setting, so render that candidate and record its actual duration for acceptance.
- Render a short candidate and listen around the boundary. The filter supports multiple inputs and processes them in sequence with crossfades; the documentation gives
n=3as an example for three inputs. For a longer chain, check each join, not just the first.
Acceptance worksheet
The figures and observations below are hypothetical, proposed checks, not test results or guaranteed FFmpeg output. They help distinguish a duration choice from an unwanted content overlap.
| Candidate | Hypothetical duration estimate | Before / during / after listening | Decision to record |
|---|---|---|---|
| Overlap on, 3-second fade | 37 seconds | Before: outgoing clip alone. During: both sources may be audible. After: incoming clip alone. | Keep only if the simultaneous passage is acceptable and the shorter total suits the edit. |
| Overlap off, 3-second fade | No duration estimate; record the rendered duration | Check whether the outgoing content has finished before the incoming content begins; listen for an unintended gap or abrupt handoff. | Keep if preserving sequential playback is more important than concurrent sound; use the measured output duration for acceptance. |
| Either option, changed curves | Same timing estimate for the selected overlap mode | Compare the transition’s level and character without changing the overlap setting at the same time. | Record both curve choices separately from the overlap choice. |
For each candidate, note the actual output duration and listen to a range before, through, and after the join. If the duration differs from your estimate, use the rendered file’s measured duration as the acceptance result rather than inferring an undocumented counting rule.
Limits and what to try next
A curve changes the fade shape; it cannot make two spoken phrases, musical beats, or other content suitable for simultaneous playback. If the overlap candidate sounds confusing, first decide whether the source material should overlap at all. If sequential playback is required but the boundary still sounds wrong, try a different fade duration or curve on a new candidate, changing one choice at a time.
The official filter documentation defines the options, but it does not promise a particular perceived loudness, musical fit, or exact duration behavior for every source. It also points to afade for curve types rather than defining all curve behavior on the acrossfade page. Multiple-input processing is documented, but this guide does not assume how a particular command will map stream selection or produce an output container. Check your command’s selected inputs and inspect the resulting audio file. Do not treat acrossfade as a way to restore missing source content.
Common questions
Does `overlap=0` remove the crossfade? No. The documented option disables overlap between the first stream’s end and the second stream’s start; the filter still applies a crossfade of the specified duration.
Do I need to use the same curve for both sides? No. The filter exposes separate curve options. Choose them independently, then listen to the combined transition.
Can `acrossfade` connect more than two inputs? Yes. The documentation provides an n option and a three-input example; inputs are crossfaded in sequence. Check every join in the rendered chain.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.