Sonic Visualiser
Sonic Visualiser is an application for inspecting and annotating audio waveforms, spectrograms and analytical layers. This page covers import checks, time alignment, annotation workflows and reproducible exports.
What Sonic Visualiser provides
Sonic Visualiser presents audio through waveforms, spectrograms and layered analysis views so a researcher or editor can inspect timing, events and annotations. A visual layer is an aid to interpretation, not proof of a recording's origin or quality; sample rate, window size and analysis settings affect what appears on screen.
Analysis and annotation discipline
Keep the original audio unchanged, record the file format and analysis settings, and use a stable time reference when marking events. Compare a feature across more than one view before drawing a conclusion, and export annotations with enough context that another person can reproduce the observation.
Maintenance note
This page reviews Sonic Visualiser for waveform inspection, spectrogram analysis, annotation and evidence-oriented export. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Sonic Visualiser to this cloud drive
Baidu Netdisk
Save Sonic Visualiser to this cloud drive
Sonic Visualiser audio analysis guide
Import one known recording, inspect waveform and spectrogram layers with documented settings, then create a small annotation set and export it for review.
Before you start
- Prepare an original audio file and a working copy for analysis.
- Note sample rate, channels, duration and any preprocessing already applied.
- Define the events or frequency regions that the annotation should describe.
Installation steps
- 01
Import and verify the recording
Open the working copy, check duration, sample rate and channel layout, and confirm that the waveform matches the expected file before adding analysis layers.
- 02
Add analysis views
Create waveform and spectrogram layers, record window and frequency settings, and compare zoom levels so short events are not mistaken for sustained features.
- 03
Annotate and export
Mark events against the stable time axis, add concise notes and export the annotation or image with the source filename and analysis settings.
Quick start
- 01
Keep time alignment explicit
Check start offsets, silence and edits before comparing recordings, and avoid copying annotations between files with different timing without a review.
- 02
Compare settings deliberately
Change one window, scale or resolution parameter at a time and record the effect so a visualization difference is not mistaken for an audio difference.
- 03
Preserve reproducibility
Archive the source copy, annotation format and analysis notes together so another reviewer can reopen the same segment and understand the conclusion.
Usage tips
- Treat loudness, frequency and visual color as settings-dependent observations rather than universal measurements.
- Use neutral filenames and remove private recording details from shared annotations.
- Export a small representative segment for review before producing a large annotation set.
Troubleshooting and uninstall
Why does the spectrogram look different after changing the view?
Window size, overlap, frequency scale and dynamic range all affect the display. Restore the documented settings and compare one parameter at a time.
Why are annotations shifted from the sound?
Check file edits, start offsets, sample-rate conversion and the active time reference, then test one known event before moving the whole annotation layer.
- Save analysis materialsExport annotations, screenshots or reports, retain the source copy and write down the analysis settings before removing the application.
- Remove Sonic VisualiserUninstall the application through the operating system and remove caches only after confirming that the source and annotation files open independently.
Frequently asked questions
Does a spectrogram prove what a sound is?
No. It is an analysis view whose appearance depends on the recording and settings; use it with the source context and other evidence.
Can annotations be moved between recordings automatically?
Only when timing, edits and sample-rate assumptions match. Verify a known event and review the result before accepting a bulk transfer.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.