
Read as Zero changes invalid input into silent samples; it does not repair the intended numeric waveform. Audacity's Sample Data Import expects plain ASCII text containing sample values. Keep Throw Error while diagnosing unexpected text, then correct the data representation before accepting the reconstructed audio.
Key Takeaways
- Numeric sample text is different from a compressed sound file or a binary RAW file.
- Use periods for decimals and the documented separators.
- Treat substituted zeros as changed audio data that needs explicit review.
Identify the file's actual contents
Open a working copy in a plain text editor. The documented input is a TXT file with numeric values separated by spaces, tabs, or line breaks. Values are read as floating-point sample amplitudes; linear values in the usual minus-one to plus-one range represent audio amplitude, rather than dB measurements.
A spreadsheet's heading, a comma-decimal export, or an annotated column is not automatically a valid waveform file. Renaming a CSV or an MP3 to TXT does not convert its contents. Preserve the original data while preparing a separate import file.
Make parsing strict before importing
Choose Tools > Sample Data Import and use Select file to choose the intended TXT. Leave Invalid data handling at Throw Error during diagnosis. If it stops on a word that should be a comment, either remove that non-data material from the working copy or prefix the complete comment with a semicolon. Do not remove a sign or decimal point merely to make parsing succeed.
The alternative Read as Zero replaces an invalid value with a zero sample and continues. For a hypothetical sequence containing 0.25, the word missing, and minus 0.25, that option inserts silence at the invalid token. It has not inferred the missing amplitude. Record any intentional substitution as a change to the data.
Check channel interpretation separately
The manual describes stereo input when a stereo track is selected before opening the tool; otherwise data is treated as mono. Stereo numeric data must interleave left and right sample values. A file listing every left value followed by every right value does not satisfy that arrangement.
Use a tiny known test before a longer import. For a hypothetical stereo ramp, make the left values positive and right values negative, then inspect that each resulting channel follows its intended direction. Check sample count and duration at the actual receiving sample rate. Successful parsing alone does not prove correct channel order or timing.
Accept the reconstructed waveform as a derived file
Keep the numeric source, import settings, and resulting project identifiable. Inspect unexpected discontinuities and compare any supplied listening reference before exporting an audio deliverable. A zero-filled region can be numerically valid while still failing the requested reconstruction.
This text-data task differs from choosing a listening reference or final master. Retain an approved-version record so a diagnostic import is not silently substituted for accepted audio. The examples are proposed checks, not executed imports.
Related tasks
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Audacity Manual: Sample Data Import: PlainASCII TXT numeric format, decimal periods and separators, ThrowError versus ReadAsZero, semicolon comments, stereo selection and interleaved channel values.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.