
Use Audacity's extended label format when a shared annotation must retain frequency bounds as well as time. The standard label format records start, end and text. A correctly timed imported label therefore does not prove that its original spectral range survived.
Key Takeaways
- A frequency annotation contains more than a timecode and a comment.
- Extended label export is a non-default choice.
- Verify the imported bounds against the same audio revision.
Define what the review note represents
The label import and export manual distinguishes standard and extended formats. The standard tab-delimited record uses start time, end time and optional text. Extended output adds frequency information associated with the label.
Suppose an editor marks a short whistle in a proposed location narration. The recipient needs both its interval and the narrow band to inspect. A comment saying “check whistle” at the correct time does not communicate the selected upper and lower limits. Do not assume a spreadsheet preserves values that were never included in its input.
This task concerns annotation exchange, not rendering audio. The region-label export guide deals with using labels to produce separate audio sections. Exporting those sections does not by itself create a frequency-aware review file.
Preserve the spectral intent at the source
The spectral selection guide documents storing the selected low and high frequencies when a label is created from that spectral selection. Select the intended time and band before creating the annotation. Keep its wording descriptive enough to identify the suspected sound without presenting an unperformed repair as successful.
Before sharing, select the label and inspect its stored bounds using the Spectral Selection Toolbar, or use the label's Edit route to inspect its record. Do not recreate a band later by remembering where a colored box appeared. A change in the spectrogram's scale can make the same visual position mean something else.
The spectrogram display tradeoff helps distinguish display resolution from the underlying selection. A more detailed view is not an export setting.
Choose the frequency-aware exchange
In Import / Export Preferences, inspect Exported Label Style and select the extended format when frequency ranges are required. The official manual describes an additional line carrying low and high values. Retain that structure when copying or reviewing the text; flattening it into a three-column-only table can discard information.
Export a disposable candidate and open it as text to confirm it contains frequency records, not only time and commentary. Keep the original export untouched if another application needs a simplified version. The simplified file should be labeled as a different deliverable.
Reimport and verify one known annotation
Import the candidate into a duplicate project containing the same audio revision. Select one known annotation and compare its time and frequency bounds with the source record. Then check the remaining entries, including any with an intentionally undefined boundary. Confirm non-English text if the exchange passes through another application.
The labeled-audio selection guide addresses a separate editing-scope issue after annotations exist. It does not validate this exchange. Acceptance requires a matching source revision, readable note and retained bounds; no export or import was performed for this hypothetical handoff.
Related tasks
- Why Does Audacity Export Different Narration Sections from My Waveform Selection?
- Why Does Audacity Ignore Some Labeled Passages During a Batch Edit?
- Why Does an Audacity Spectrogram Show Clear Hum but Blur a Short Click?
Sources and scope
- Audacity Importing and Exporting Labels: Frequency-aware versus standard label export.
- Audacity Spectral Selection: How labels acquire and recall spectral bounds.
Proposed documentation-based label handoff; no tested file.
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.