Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Establish the reference
Keep an unchanged source and identify the passage or signal relationship described below.
Separate the monitoring path from the saved file
Record a short spoken count with headphones. Save it and listen with monitoring stopped. If the second voice appears only during live monitoring, inspect duplicate monitoring paths and wireless output before changing the recording. If the repeat remains in the saved file, check room reflections or an enabled effect. Do not play a live microphone through speakers while diagnosing feedback.
Verify the saved result
Reopen the downloaded file and compare the relevant event with the source. Keep the source and the settings note for a later revision.
Build a timing budget without claiming a device measurement
A hypothetical 256-frame buffer at 48,000 frames per second represents 256 ÷ 48000 = 5.333 milliseconds of audio. Two such buffers account for 10.667 milliseconds before converters, scheduling and other buffers. This arithmetic is a component budget, not a round-trip latency measurement.
Swipe or scroll sideways to read all columns.
| Item | Value or action | Meaning |
|---|---|---|
| One 256-frame buffer | 5.333 ms | At 48 kHz only |
| Two such buffers | 10.667 ms | Other costs excluded |
| A 250 ms delay | 12,000 frames | Intentional repeat spacing |
Apply the result within the tool’s limits
The browser recorder is not a calibrated round-trip latency meter. Turning off a delay effect cannot remove hardware latency. For an intentional repeat, use Delay; for a late performance recording, align the track in an external editor only after checking the source timing.
Common questions
Are the example numbers device test results?
No. Numerical examples and worksheets on this page are authored explanations. They do not measure your recording, browser latency or listening accuracy.