The wrong Bluetooth latency test signal can make a slow earbud look innocent and a good test rig look haunted. If you are trying to measure audio delay today, the signal you choose matters almost as much as the stopwatch, microphone, camera, or oscilloscope you use. This guide shows when to use an impulse, square wave, MLS, or chirp, plus how to avoid the tiny timing traps that turn clean measurements into audio goblin soup.
What a Bluetooth Latency Signal Must Prove
A Bluetooth latency test signal has one job: create a timing mark that survives the trip from source device to wireless audio output. That sounds simple until the signal passes through the app, operating system mixer, Bluetooth codec, radio link, earbud buffer, DSP, amplifier, driver, room air, microphone, and your recording chain. By the end, your clean little click may look like a wet matchstick.
For most practical tests, you are trying to answer one of four questions:
- How late is the audio? This is one-way latency from trigger to sound.
- How stable is the delay? This is jitter, which often feels worse than a fixed delay.
- Does latency change by frequency? This suggests DSP, filtering, or measurement-path issues.
- Can I repeat the result tomorrow? Repeatability is the grown-up in the room holding a clipboard.
I once measured the same earbuds with a click, a phone camera, and heroic confidence. The first result looked amazing. The second looked tragic. The third made me suspect the camera more than the earbuds. That is the day I stopped treating Bluetooth latency as a single number and started treating it as a small detective story.
For broader test-rig setup, pair this article with how to build a Bluetooth latency test rig. If your main confusion is whether you are measuring round-trip or playback-only delay, read round-trip vs one-way Bluetooth latency before choosing a signal.
- Use impulse clicks for quick start-time detection.
- Use square waves when edge visibility matters.
- Use MLS or chirps when you need correlation or frequency clues.
Apply in 60 seconds: Write down whether you need one-way latency, jitter, or frequency behavior before picking a test signal.
Who This Is For / Not For
For people testing real Bluetooth delay
This guide is for audio hobbyists, reviewers, rhythm-game players, video editors, app testers, repair techs, and anyone building a home Bluetooth latency benchmark without a university lab hiding in the garage.
It also fits people comparing AAC, SBC, aptX, LC3, or platform behavior across iPhone, Android, Windows, and macOS. If that is you, the platform-specific internal guides on macOS Bluetooth AAC latency benchmarking and Windows Bluetooth AAC latency benchmarking will be useful side doors.
For people who need practical decisions, not lab theater
You do not need to know every codec frame boundary to get useful data. You do need to avoid fake precision. A result like “143 ms average, 12 ms swing across 20 trials” is often more useful than “141.827 ms” with no repeatability notes.
Not for medical, aviation, legal, or certified audio testing
This article is not a formal compliance procedure. If your measurement affects medical devices, workplace safety, courtroom evidence, hearing protection, or product certification, use proper calibrated equipment and qualified review.
Signal Comparison at a Glance
Here is the friendly knife drawer: every tool cuts, but not every tool belongs near a tomato.
| Signal | Best Use | Strength | Weak Spot | Best Tool Pairing |
|---|---|---|---|---|
| Impulse | Fast one-way latency checks | Clear start point | Can be smeared by filtering and DSP | LED trigger plus microphone or oscilloscope |
| Square wave | Visual edge comparison and repeated timing | Many edges for multiple samples | High harmonics may distort or be filtered | Two-channel recorder or scope |
| MLS | Correlation-based delay detection | Good in noise, repeatable math | Assumes system behavior is reasonably stable | Recorded reference plus software correlation |
| Chirp | Frequency-dependent delay clues | Shows smear, filtering, and time spread | Start time can be less obvious by eye | Spectrogram, cross-correlation, or audio editor |
Best plain answer: use an impulse for quick Bluetooth latency checks, a square wave burst when you want repeated visible edges, MLS when you want robust correlation, and a chirp when you suspect the delay changes across frequency.
Bluetooth SIG materials on LE Audio and LC3 are useful background because codec design and buffering affect what your signal survives during transmission. Consumer tests still need local measurement, but knowing the audio path keeps your expectations sane.
Decision card: choose your signal fast
Use this quick decision card before you record anything.
- Need a quick yes/no latency number? Start with impulse.
- Need multiple timing edges in one file? Use square wave bursts.
- Need math-friendly delay detection? Use MLS.
- Need to diagnose frequency smear? Use chirp.
- Need a public benchmark? Run impulse plus one confirmation signal.
Impulse Tests for Fast Answers
An impulse is the classic “click” test. It gives you a sharp event that is easy to see on a waveform and easy to pair with an LED flash, screen flash, GPIO pulse, or reference audio channel. For Bluetooth latency, that simplicity is gold.
In a home rig, the impulse often wins because you can measure the time from a visual or electrical trigger to the first meaningful acoustic arrival. It is the audio version of clapping in a hallway to find the echo, except the hallway has codecs, buffers, and a tiny robot inside each earbud.
When impulse is the best choice
- You need a quick one-way latency estimate.
- You are recording with a microphone near the earbud or speaker.
- You are aligning an LED flash or screen flash with captured audio.
- You want to repeat 10 to 30 trials and calculate average plus spread.
Impulse tests are especially useful for A/V sync checks. If you already use timestamp methods, connect this with timestamp alignment for measuring A/V sync. The signal is only half the job; the timestamp is the other half wearing sensible shoes.
What can go wrong with impulse
Bluetooth audio devices may soften the click. Some earbuds apply limiting, ANC processing, EQ, or noise suppression. The first visible wiggle in the waveform may not always be the perceived start of the sound. In noisy recordings, you may need a threshold rule such as “first sample exceeding 10 percent of peak after the expected window.”
A small lived lesson: I once placed a microphone too far from a tiny Bluetooth speaker and measured the room more than the speaker. Moving the mic closer reduced the chaos. The result did not become perfect, but it stopped doing interpretive dance.
- Run at least 10 trials.
- Keep microphone distance short and consistent.
- Use the same detection threshold every time.
Apply in 60 seconds: Create a click file with 1 second of silence before each click so every event is easy to isolate.
Square Wave Tests for Visible Edges
A square wave is useful because it creates repeated edges. Instead of one lonely click standing in the rain, you get a pattern of transitions. Those edges can make it easier to compare source and recorded output across several points.
For Bluetooth latency, do not use an endless loud square wave. Use a short burst at a safe level. A 100 Hz to 1 kHz square wave burst can be useful for visible alignment, but it contains strong harmonics. Some devices may filter, reshape, or compress those harmonics.
When square wave works well
- You have a two-channel recording with source reference on one channel and microphone capture on the other.
- You want several edges to estimate average delay inside one take.
- You are testing stability across repeated bursts.
- You need an easy waveform for manual alignment in an editor.
When square wave gets rude
Square waves are not polite to audio chains. Their steep edges can expose bandwidth limits, anti-aliasing filters, codec behavior, or DSP smoothing. That is sometimes helpful, but it can also make start detection less clean than expected.
For rhythm games, fixed latency is one problem and jitter is another. If your square wave edges land at slightly different offsets across time, read average latency vs jitter. A steady 130 ms delay can be adjusted. A delay bouncing around like a caffeinated metronome is harder to forgive.
Practical square wave settings
| Setting | Suggested Start | Why It Helps |
|---|---|---|
| Frequency | 250 Hz to 1 kHz | Easy to see without becoming too punishing |
| Burst length | 100 to 300 ms | Gives several edges without fatigue |
| Silence between bursts | 1 to 2 seconds | Makes each burst easy to isolate |
| Level | Moderate, never painful | Protects ears and avoids limiter behavior |
MLS Tests for Correlation Work
MLS means Maximum Length Sequence. In practice, it sounds like noise but behaves like a clever test pattern. You record the Bluetooth output, compare it to the original sequence, and use correlation to find the delay peak.
MLS is not usually the first signal I recommend to beginners. It is better when you have software that can correlate the recorded signal against a reference. It shines when clicks are too ambiguous, the environment is a little noisy, or you need repeatable math instead of eyeballing waveform bumps at midnight.
When MLS is useful
- You are comfortable using correlation tools.
- You need delay detection in a noisy recording.
- You want a stronger statistical marker than one click.
- You are comparing devices under the same controlled method.
When MLS can mislead you
MLS works best when the system is reasonably stable and behaves in a way that correlation can interpret. Bluetooth processing may include compression, dynamic gain, ANC, spatial audio, and codec buffering. Those features can distort the correlation peak or add extra structure.
A reviewer friend once sent me an MLS result with three peaks. The device was not time-traveling. The recording path had a direct acoustic arrival, a reflection from the desk, and a noise-canceling mode adding its own little fog bank. The practical fix was simple: move the mic closer, turn off processing where possible, and repeat.
MLS buyer checklist
Before using MLS for Bluetooth latency, check these items:
- Can your software generate and store the exact reference MLS?
- Can it perform cross-correlation without resampling surprises?
- Can you record at a stable sample rate?
- Can you disable ANC, transparency, spatial audio, and sound effects?
- Can you repeat the same test at least 10 times?
- Can you identify the main correlation peak consistently?
Show me the nerdy details
MLS and chirp methods often use cross-correlation to estimate delay. You compare the recorded output against the known original signal and look for the lag value that produces the strongest match. In Bluetooth tests, the peak may shift if the source device resamples audio, if the codec buffers frames differently between runs, or if the receiving device applies dynamic processing. A good workflow keeps sample rate fixed, records a wired reference channel when possible, repeats trials, and reports average latency plus spread instead of pretending one trial is destiny engraved in marble.
Chirp Tests for Frequency Clues
A chirp sweeps through frequencies over time. For Bluetooth latency work, a chirp is less about getting the fastest simple number and more about seeing how the audio path behaves. It can reveal smearing, filtering, onset ambiguity, and frequency-dependent delay.
If an impulse is a camera flash, a chirp is a lantern moving across the room. It shows where the furniture is. Occasionally, it also reveals that your “Bluetooth problem” is actually a room reflection, a microphone placement issue, or a processing mode you forgot to turn off.
Linear chirp vs logarithmic chirp
A linear chirp moves through frequencies at a steady Hz-per-second rate. A logarithmic chirp spends proportionally more time in lower frequencies and is common in acoustic testing. For consumer Bluetooth latency, either can work, but a logarithmic sweep often gives more practical diagnostic value across the audible band.
When chirp is the best choice
- You suspect earbuds are adding DSP that smears transients.
- You want to inspect the output in a spectrogram.
- You are comparing modes such as game mode, ANC on, ANC off, and spatial audio.
- You need to explain why a simple click result feels different during music or video.
When chirp is too much
If you only need a quick latency number for watching videos, start with an impulse. Chirps are more work. They are useful when your question has grown teeth, such as “why does this device measure okay with clicks but feel late during gameplay?”
Codec and device behavior matter too. For deeper context, see best Bluetooth codec for rhythm games, LC3 latency on first-gen LE Audio, and SBC bitpool settings and latency.
Visual Guide: Pick the Right Bluetooth Latency Signal
Use an impulse click for a fast one-way latency estimate.
Use square wave bursts when repeated visible transitions help.
Use MLS when correlation is more reliable than eyeballing.
Use chirps to inspect smear, filtering, and frequency behavior.
Build a Repeatable Bluetooth Latency Routine
The best signal cannot rescue a sloppy routine. Bluetooth latency measurement needs consistency: same volume, same distance, same app, same codec, same mode, same battery range, same room, same detection rule. Tiny changes are little thieves.
A practical 15-minute test routine
- Choose the signal. Start with impulse unless you need a special diagnostic test.
- Set the source device. Disable sound enhancements where possible.
- Set the Bluetooth device. Note codec, mode, ANC status, and battery level.
- Place the microphone. Keep it close and fixed.
- Record 10 to 20 events. Do not trust one heroic sample.
- Measure with one rule. Use the same threshold or correlation peak method.
- Report average and spread. Include minimum, maximum, and trial count.
When comparing phones, laptops, and operating systems, avoid changing everything at once. If you compare iPhone AAC to Android AAC, keep the earbuds, room, signal, and detection rule unchanged. Then use platform notes such as iOS AAC Bluetooth latency vs Android and Galaxy S series Buds SBC vs AAC latency to interpret the pattern.
Short Story: The Click That Lied
A small studio owner once asked why his Bluetooth monitor test showed only 60 ms of delay, even though every musician complained that the timing felt late. His test used a single click played from a laptop and recorded by a phone across the room. The waveform looked crisp enough, but the phone camera introduced timing uncertainty, the microphone captured room reflections, and the Bluetooth speaker had a “movie sync” mode that behaved differently after the first few seconds of playback. We rebuilt the test with repeated impulse bursts, a closer microphone, a wired reference channel, and 20 trials. The average delay landed much higher, and the jitter explained why the musicians felt uneasy. The lesson was not that clicks are bad. The lesson was that one click, one recording, and one confident eyebrow raise do not make a measurement.
- Run multiple trials.
- Use the same setup each time.
- Report spread, not just average.
Apply in 60 seconds: Add a simple test log with columns for device, codec, signal, mode, trial count, average, minimum, and maximum.
Safety and Volume Guardrails
Bluetooth latency testing is usually low-risk, but test tones can become uncomfortable or unsafe if played loudly, especially impulses, square waves, and high-frequency chirps. Keep levels moderate. Never place earbuds in your ears while running unknown test files. Test with the device on a desk or coupler first.
Organizations such as NIST emphasize uncertainty and disciplined measurement practice in scientific work. For audio testing at home, the spirit is simple: control what you can, admit what you cannot, and do not punish your ears for a prettier graph.
Safe test checklist
Before pressing play, confirm:
- Volume starts low and increases only if needed.
- Earbuds are not in your ears during initial testing.
- Impulse and square wave files are not clipped.
- Chirps do not contain painfully loud high-frequency sections.
- ANC and transparency modes are noted, not forgotten.
- Pets and children are not near sudden loud sounds.
I once ran a chirp too hot on a compact Bluetooth speaker. The speaker survived. My dignity, less so. The fix was boring and perfect: lower level, shorter file, and a sanity listen through a cheap wired speaker first.
Common Mistakes
Mistake 1: Trusting one test signal too much
Impulse clicks are fast, but they do not tell the whole story. MLS and chirps can expose issues that clicks hide. For public comparisons, use at least one primary signal and one confirmation signal.
Mistake 2: Measuring camera delay instead of Bluetooth delay
Phone cameras often use variable frame timing, rolling shutters, and processing. A 240 fps video can help, but it does not magically remove uncertainty. If you use video, compare it against a wired control and read audio latency measurement mistakes.
Mistake 3: Ignoring jitter
A device with 110 ms average latency and 5 ms jitter may feel better than a device with 90 ms average latency and 35 ms jitter. Average latency gets the headline. Jitter does the haunting.
Mistake 4: Forgetting codec and mode changes
Codec switches can change delay. Game mode, low-latency mode, ANC, spatial audio, multipoint, and app-specific sync can all change results. Note them like a serious person with a mildly dramatic spreadsheet.
Mistake 5: Using a clipped or too-loud signal
Clipped impulses and square waves make detection messy and may trigger limiters. Keep peaks below full scale. Moderate signals often measure better than aggressive ones.
Mistake 6: Comparing results across different rigs
A test from a camera-based setup and a test from an oscilloscope setup may not be directly comparable. They can both be useful, but only if the method is described. For bias control, use how to avoid measurement bias in Bluetooth latency tests.
- Lock down the setup.
- Repeat trials.
- Document codec and device mode.
Apply in 60 seconds: Add “codec, ANC, game mode, distance, volume” to every test note before recording.
Mini Calculator and Decision Rules
Use this small calculator to summarize a test run. Enter your measured minimum, average, and maximum latency values in milliseconds. It will estimate jitter spread and give a plain-language interpretation.
Bluetooth Latency Spread Calculator
Risk scorecard for signal choice
| Goal | Lowest-Risk Signal | Confirmation Signal | What to Report |
|---|---|---|---|
| YouTube or movie sync | Impulse | Square wave burst | Average one-way latency and trial count |
| Rhythm games | Impulse burst series | Square wave or MLS | Average, min, max, and jitter spread |
| Device review | Impulse plus repeated trials | MLS or chirp | Method, codec, mode, room notes, and spread |
| DSP diagnosis | Chirp | Impulse | Spectrogram notes and onset behavior |
For interference testing, signal choice is only one part of the picture. Distance, Wi-Fi congestion, and packet behavior can change stability. See Bluetooth earbuds latency vs distance and Bluetooth latency under 2.4 GHz Wi-Fi interference if your results swing wildly.
When to Seek Help
Most Bluetooth latency testing can be done safely at home. Still, there are moments when a second set of trained eyes saves time, money, and a small landslide of frustration.
Ask an audio engineer or measurement specialist when:
- Your results will be published as formal product claims.
- You need to compare devices for a workplace, school, venue, or contract.
- Your method must survive peer review, legal review, or vendor dispute.
- You cannot separate Bluetooth latency from app, OS, or camera timing.
- Your results change by more than 30 ms without a clear reason.
Ask a hearing professional when:
- Test tones caused ringing, discomfort, or pain.
- You accidentally played loud impulses or chirps near your ears.
- You are testing hearing aids or assistive listening devices.
If your test method uses a browser, app, or Web Audio-based generator, remember that software timing can matter. The W3C Web Audio specification is helpful background for understanding browser audio concepts, though a finished measurement still depends on your hardware path.
- Consumer comparisons can be informal.
- Published claims need stronger methods.
- Hearing discomfort is not a measurement challenge; it is a stop sign.
Apply in 60 seconds: Mark your test as “informal,” “review-grade,” or “needs calibrated lab” before sharing results.
FAQ
What is the best test signal for Bluetooth latency?
For most consumer Bluetooth latency tests, an impulse click is the best starting signal because it gives a clear timing event. Use square wave bursts when you want repeated edges, MLS when you want correlation-based delay detection, and chirps when you need frequency behavior clues.
Is an impulse better than a chirp for measuring Bluetooth delay?
An impulse is usually better for a quick latency number. A chirp is better for diagnosis. If your question is “how late is this earbud,” start with impulse. If your question is “why does the sound feel smeared or mode-dependent,” add a chirp test.
Can I measure Bluetooth latency with a phone camera?
Yes, but treat the result as approximate. High-frame-rate video can help compare a visual event with an audio event, but camera processing, frame timing, and rolling shutter can add uncertainty. A wired reference channel or oscilloscope-style setup is usually stronger.
Why do my Bluetooth latency results change between tests?
Common causes include codec switching, app buffering, OS audio routing, ANC mode, game mode, multipoint connection, battery state, distance, Wi-Fi interference, and inconsistent detection rules. Repeat trials and report the spread, not just one number.
Does square wave testing damage Bluetooth earbuds?
A moderate, short square wave burst should not damage normal earbuds, but loud square waves can be unpleasant and may stress small drivers. Start low, keep bursts short, avoid clipping, and never place earbuds in your ears during first playback of unknown test files.
Is MLS good for Bluetooth latency testing?
MLS can be good when you have software that can compare the recorded signal with the original reference using correlation. It is less beginner-friendly than impulse testing and can be confused by heavy DSP, room reflections, or unstable processing.
Should I test average latency or jitter?
Test both. Average latency tells you the typical delay. Jitter tells you how much the delay moves between events. Rhythm games, live monitoring, and tight editing often suffer more from unstable delay than from a fixed delay that can be compensated.
What sample rate should I use for Bluetooth latency testing?
Use a common fixed sample rate such as 48 kHz when possible, and keep it consistent across source, recording, and analysis. Changing sample rate between trials can add hidden resampling behavior and make comparisons harder.
Do Bluetooth codecs change which signal I should use?
They can. SBC, AAC, aptX variants, and LC3 may respond differently to sharp transients, buffering, and device modes. The signal choice still follows the same rule: impulse for quick timing, square wave for visible edges, MLS for correlation, and chirp for frequency clues.
How many trials do I need for a useful Bluetooth latency test?
Use at least 10 trials for informal testing and 20 or more when comparing devices publicly. Report average, minimum, maximum, and the test conditions. One measurement is a clue. A group of measurements is a result.
Conclusion
The opening problem was simple: one wrong test signal can make Bluetooth latency look cleaner, worse, or stranger than it really is. The practical answer is not to crown one signal forever. Use the signal that matches the question.
For a fast result, choose an impulse. For repeated visible edges, choose a square wave burst. For correlation-friendly analysis, choose MLS. For frequency and DSP clues, choose a chirp. Then repeat the test, report the spread, and keep your method consistent enough that tomorrow’s result can shake hands with today’s.
Here is your 15-minute next step: create one impulse file with repeated clicks, record 10 trials from your Bluetooth device, and log average, minimum, and maximum latency. That small routine will teach you more than a single polished number ever could.
For a broader foundation, read Bluetooth audio latency truths and then compare your results against specific platform tests only after your signal and method are stable.
Last reviewed: 2026-06
