SonauditThe best QC export depends on who will use it next. A producer may need a short document that explains a failed file. An operations team may need one row per issue in a spreadsheet. An internal tool may need the complete hierarchy of files, measurements, and findings.
Sonaudit generates PDF, CSV, and JSON from the same scan results, but the formats are not interchangeable. Choose the audience first, then select the file scope, status filter, and report preset.
Use PDF for a human review or delivery record
PDF is the clearest choice when the recipient will read rather than process the report. It can summarize the profile, overall status, file properties, measured values, thresholds, review notes, container information, metadata markers, and SHA-256 value. Optional representative waveform evidence gives a timed finding visual context without turning the document into a waveform dump.
Sonaudit offers three report intents. Delivery excludes unconfirmed candidates, ignored items, and informational notes by default. Internal Review includes pending review items but omits ignored and informational entries. Full Audit retains the technical and review trail, including ignored findings.
Use CSV when rows belong in a spreadsheet
The CSV export places each included issue on its own row and repeats the file measurements needed to understand it. A file with no included issues still receives a row. This works well for filtering by file, category, severity, rule, reviewer decision, sample rate, loudness, or peak value in Numbers, Excel, or another tabular tool.
CSV is intentionally flat. A review note containing commas or line breaks is escaped, and the file uses UTF-8 with a byte-order mark for common spreadsheet compatibility. The trade-off is repetition: file-level values appear on multiple rows when one file has several findings.
Use JSON when another system needs the hierarchy
JSON keeps a versioned document structure instead of flattening every relationship. Sonaudit's current structured export identifies schema version 1 and preserves the selected profile, export options, files, metrics, findings, dialogue or Dolby metadata when present, and review state. It is the better starting point for an archive, custom parser, or later automation.
A version number does not make the schema immutable. A consumer should reject or explicitly migrate an unknown future version rather than assuming that every field will remain in the same shape forever. CSV column names likewise deserve a deliberate import mapping if they feed a production system.
Filter the report without rewriting the scan
An export can include every file or only the selected file, and it can be limited to noncompliant or review results. Source paths can be hidden when a client should not see a private workstation directory. These options change the exported view, not the underlying project or scan.
Review all pending candidates before using the Delivery preset. Its cleaner status is intentional: a file with only unconfirmed candidates may appear as passing in that report because those candidates are excluded. Use Internal Review when the recipient must see the unresolved queue.
A report records a decision; it is not a certificate
Every export is tied to the files and results available at that moment. If audio changes after export, scan it again and create a new report. A SHA-256 value can help identify the analysed file, but it does not prove that a platform accepted the delivery or that a profile matches the receiver's latest specification.
Report export is part of Sonaudit Pro. The free version can scan and review up to three files per batch, which is enough to test the core workflow before deciding whether saved projects and exports belong in the production process.