Final Cut audio stems: map roles to the files you need

An editor asks for dialogue, music and effects as separate files. Before exporting, turn that request into a small map: which material belongs in each group, what the files should contain and how the recipient expects to open them.
Agree on the package before preparing many outputs. One container with several audio tracks and several separately named files can be useful deliveries, depending on the request. Write down which one the recipient needs.
Map the request to the project
Use the blank role-to-file map to record the project revision and the intended contents of each output. Keep the requested group beside the role or subrole you intend to include.
Pick one recognisable passage for each group. For dialogue, that might be an agreed sentence; for music or effects, use a passage where the intended material is easy to identify. These are planning examples, not a project or listening test performed for this guide.
If a group's contents are uncertain, inspect the relevant role assignments in the project before sending the export. Use the versioned Apple export guide below to inspect how those groups enter the delivery. A folder name cannot establish which project material was assigned to a role.
Inspect the export grouping
Apple's Final Cut Pro 12.4 role-export instructions describe the Export File destination and its Roles pane. The available export choices depend on the selected format settings.
Two relevant choices in that guide are:
- Multitrack QuickTime Movie: the selected roles are delivered within one movie file.
- Audio Only as Separate Files: the selected audio roles are delivered as separate files.
Inspect the output rows as well as the overall choice. Apple documents adding roles or subroles to an output, so a row can combine material. Record the groups you actually included and the selected mono, stereo or surround channel arrangement.
Use the documentation for your installed version if its controls differ. Keep an unavailable option marked unavailable until you understand the selected format and the recipient's requirement.
Make the output inventory explicit
| Planning question | Record before exporting | Check after exporting |
|---|---|---|
| What package was requested? | One multitrack file or separately named files | Actual files received |
| What belongs in each group? | Intended roles, subroles and content | Recognisable passage heard |
| What channel arrangement is needed? | Agreed arrangement for each output | Recipient's import result |
| Which part of the project is required? | Intended beginning and ending | Actual boundaries |
For a partial-project delivery, inspect the range being shared. Apple's instructions distinguish a range selection from simply selecting a timeline clip. Keep this boundary decision beside the grouping decision so a correctly named file still contains the intended passage.
Export a small agreed comparison to a new folder first. Preserve the source project and earlier results while checking the output. If a choice is unhelpful, keep the failed comparison identifiable before trying a new revision.

Listen to the intended content in each output
Open the delivered copy in the intended recipient workflow. Confirm its filename, the content you hear and the passages used for the check. Record unexpected music, missing dialogue or uncertain routing without treating a matching file count as acceptance.
If you receive one container and need to inspect its structure, the FFprobe stream and channel guide separates streams from channels. That is a file-structure check. The recipient still needs to confirm the intended content and import procedure.
When a result differs from the request, return to the map. Check the chosen output row, included groups and project revision before repeating the same export. Give the next result a separate revision so earlier notes remain traceable.
Further reading: a role-based delivery example
Larry Jordan's Roles, Role Components and Audio Stems works through a specific dialogue, effects and stereo-music request. It was published in July 2018 for Final Cut Pro X. Use it as an older practitioner example of matching groups and channel intentions, then check current controls against your installed version's Apple guide.
Send the map with the files
Include the agreed inventory and the passages the recipient should compare. If an editable project was requested as well, identify that as another deliverable with its own dependencies. Keep the source available until the handoff is accepted.
The versioned Apple export section and practitioner example were rechecked on 13 November 2026. No Final Cut project, role assignment, export, recipient import or playback was operated for this guide. The map is a blank acceptance record, not proof of a completed handoff.