What success looks like
Meter passes audio unchanged. RMS is generally below peak; held peaks let you catch events you missed visually.
Meter passes audio through. A configured connection can be silent, and a running state alone does not prove signal. Silence is represented with a finite floor in API telemetry rather than JSON infinity.
01 / Understand
The idea, before the settings.
Peak describes the largest sample amplitude. RMS describes average signal energy. Clipping count reports overload observations; these are different measurements and should be read together.
Signal to inspect→Meter→Same signal onward
Use it in AudioRouter
- Place Meter before or after the stage you want to inspect.
- Read the stereo RMS bars for average energy, white current-peak markers for transients and gold held peaks for recent extremes.
- Check the clipping count and downstream headroom while playing the loudest passage.
If it does not work
Silence at this meter points upstream. Healthy signal here but silence later points to a downstream route, mute or device.
Select the node to open Properties. Click its name to rename it. While playing, supported parameter-only edits save after a short pause. For structural edits, use Save when the canvas marks a change. Enabled and Bypass are distinct live controls; see the in-app help for their behavior.
02 / Explore
Make the behavior visible.
Four level sections include an intentionally over-range third section. The lesson's bar, current peak, held peak and clip count are computed from the same stereo samples you hear, before the quiet browser monitor gain.
The example repeats until you press Stop, and control changes are heard immediately. The picture shows the tool's shape rather than time; follow the timing in Follow the sound below. This is not a DSP measurement or control for your running AudioRouter session.
03 / Configure
Every control, with a reason.
No numeric settings to guess
Meter observes the signal. Read RMS, current peak, held peak and clipping in Properties; it does not change the level.
04 / Put it to work
Start with a useful example.
Find where signal disappears
- Place Meter after a source and another after a suspected processor.
- Run the same source through the route.
- Compare fresh readings and inspect enabled, bypass and failure states at the first silent stage.
Compare level fairly
- Observe both peak and RMS while replaying the same passage.
- Match listening level before judging whether a processor sounds better.
These are starting points. Compare at a comfortable monitoring level and adjust for your own source.
05 / Get unstuck
Small details that matter.
- RMS is not a full perceived-loudness or LUFS measurement.
- A flat meter may mean silence or unavailable/stale telemetry; read its state.
- The current prepared graph snapshot has block RMS and cumulative peak hold; do not promise configurable 300 ms / 1 s controls.