
Audacity's Export Labels combines label tracks rather than filtering them by the track or time region you selected. If another team's notes appear in the exported text, inspect the command's scope before changing the selection repeatedly. Prepare a deliberate recipient-specific copy and verify its contents.
Key Takeaways
- Label-text export is not selected-audio export.
- A selected track does not restrict Export Labels.
- Check every exported note before distributing the file.
Identify the actual delivery command
The label import/export manual documents File > Export Other > Export Labels and states that selected tracks or regions cannot limit that command. When several label tracks exist, their labels are combined in the exported file. The output's default name is therefore not a reliable inventory of which notes it contains.
For a proposed interview film, imagine separate label tracks for client review, pronunciation corrections and internal recording issues. Selecting Client Review before export does not establish that only those notes will be shared. Open the resulting text and read it before sending anything.
This is distinct from labeled-audio editing scope. That workflow determines which labeled audio is eligible for an edit. Its selection rules do not override this text-export command.
Prepare an isolated working copy
Preserve the full project and name a separate working copy for the recipient's notes. Identify the label track that represents the agreed review. Check its wording and time references before isolating it; keeping only one track does not make that track appropriate automatically.
The manual describes temporarily removing the other label tracks, exporting the remaining one, and using Undo to restore them. Perform that only on the recoverable working copy, not the sole project. Confirm which track is being removed and keep its original available. If you cannot confidently restore the workspace, stop and rebuild the recipient edition from the preserved project.
Do not delete the accompanying audio merely to reduce note scope. It is useful as a reference for confirming timecodes. A separate audio-region export is another deliverable and should be identified by its actual content.
Inspect the exported text
The standard label record contains start time, end time and label text separated by tabs. Point labels have matching start and end times. Open the candidate as text and compare its entries with the intended review list, including a note near the beginning and one near the end.
Preserve UTF-8 encoding when another editor changes non-English text. Converting a file in a spreadsheet may alter delimiters or characters. Reimport the candidate into a duplicate project with the same audio to verify where its labels land; imported labels form an additional track rather than replacing the source automatically.
Reconcile the final recipient edition
Check that no internal-only note remains and that every required client note is present. Count and content both matter: an omitted note and an unintended extra can cancel numerically. Confirm the audio revision used, because an earlier edit can make correct time values point at the wrong phrase.
The export metadata guide concerns another carried-over-information risk, not this label-selection mechanism. Record the exported filename, intended audience and revision separately. Acceptance means the actual text and reimported positions match the agreed note set. No project was altered or labels exported for this scenario.
Related tasks
- Why Does Audacity Ignore Some Labeled Passages During a Batch Edit?
- Why Does Audacity Export Different Narration Sections from My Waveform Selection?
- Why Does Audacity Export an Old Artist Name After I Set New Defaults?
Sources and scope
- Audacity Importing and Exporting Labels: Label-text export scope and verification.
Hypothetical review-note export based on official guidance.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.