# Testing 84 BPM lo-fi swing: a controlled protocol, not a verdict

Evelyn Porter · October 17, 2026

> Swing timing varies across DAWs. Learn how to test 84 BPM lo-fi swing using a controlled protocol to measure actual interval timing and verify sequencer behavior.

The denominator is not universal. Some sequencers apply swing to 8th-note pairs, others to 16th-note pairs, and implementations may define the percentage differently. Before comparing settings, render one isolated pair at the target swing value and measure its first interval against the 357.143 ms pair; if it does not match the calculated share, the DAW is using a different denominator or note value.

A null-tested control matters because swing changes only relative placement within the pair. Render straight 16ths first, then compare the swung render to that control by nulling or phase-canceling identical elements; any residual should represent timing displacement rather than level or tone changes. This isolates the swing variable from other processing.

The 54–68% range should be treated as an untrusted headline hypothesis until the denominator is fixed and the same one-bar MIDI is rendered consistently. The math above gives expected intervals, but the DAW's actual implementation must be verified by measurement.

![The denominator is not universal. Some sequencers apply — Testing 84 BPM lo-fi swing](https://static.mm-ais.com/article-images-ai/testing-84-bpm-lo-fi-swing-a-controlled-ai-e3808ac8.jpg)

## Evidence Audit: No Drum Data in Grounding

This section audits only the supplied grounding, not the audio. I checked every source provided for the article and found no swing percentage, BPM, MIDI, onset deviation, or lo-fi drum-pattern protocol. That absence is not a minor gap: it means the headline swing claim has no drum-specific support in the material supplied, so it should be treated as an untrusted hypothesis until a controlled test produces the missing evidence.

The Justin Bieber Wikipedia deep read is a biography and career record. It supplies occupation, years active, works, spouse, children, parents, family, awards, origin, and genres. Those facts are useful for artist context, but none of them is a rhythm-generation experiment, a tempo test, a MIDI rendering, or a drum-timing measurement. It contains zero BPM, swing percentage, MIDI, onset deviation, or lo-fi drum-pattern protocol.

The Britannica and Billboard snippets describe Bieber's career and commercial profile. They mention his teen-idol rise, albums, signing by Scooter Braun at age 13, birthday, height, and tour-notification details. They are artist-profile material, not experimental records; they contain no rhythm-generation experiment, no tempo test, no straight-versus-swung comparison, and no drum timing measurement.

The TikTok and policy snippets concern perceptions of political content and policymakers' perceptions of the wellbeing economy. None of these pages supplies a drum experiment, a swing definition, a DAW setting, or a listening-test protocol.

| Source | What it documents | Drum-timing evidence |
| --- | --- | --- |
| Wikipedia deep read | Biography, works, genres, spouse, children, awards | None: no BPM, swing, MIDI, or onset data |
| Britannica and Billboard snippets | Career and commercial profile | None: no rhythm experiment or timing measurement |
| YouTube channel snippet | Page styling and navigation | None: no music-analysis protocol |
| TikTok and policy snippets | Political-content and wellbeing-economy perceptions | None: no drum experiment or DAW setting |

As the audit above shows, no source provided contains drum-timing data, so the swing range cannot be validated from these pages. The audit does not claim the hypothesis is false; it claims only that these pages cannot support it. Validation must come from the documented protocol with its own control condition and measurement record.

![Quiet rain streaked window over vinyl turntable cable tangle](https://static.mm-ais.com/article-images-ai/testing-84-bpm-lo-fi-swing-a-controlled-ai-5793fd8e.jpg)
Quiet rain streaked window over vinyl turntable cable tangle

## Options Compared: Straight vs 54 vs 68

Straight 16ths is the control-condition winner: its equal first and second 16ths provide a fixed reference, so a later perceptible difference can be attributed to swing rather than to sample choice, gain, or humanization. The two swing candidates are not yet winners; they remain hypotheses until they pass the same blind comparison.

| Option | Timing shape | Test role | Winner? |
| --- | --- | --- | --- |
| Straight 16ths | equal first and second 16ths | control that isolates swing | yes, as control |
| 54% swing | first slightly longer | subtle late-first test | no, not yet |
| 68% swing | first much longer | near-triplet extreme test | no, not yet |

The control wins by definition, not by sounding better. Because straight 16ths keeps the first and second 16ths equal, it removes timing variation as an explanation for a difference you hear. If a swing candidate is preferred, that preference must be shown against this fixed reference, not against another uncontrolled render.

The lower swing candidate is the harder perceptual call. Its first note is only slightly longer, so its late-first shape can be mistaken for straight timing, sample attack, or level differences. Treat it as unproven until it wins the blind comparison on its own merits.

The higher swing candidate is the more obvious timing distortion, but obviousness is not evidence. A near-triplet extreme can be useful or distracting depending on the part, so it also remains unproven until it wins the same comparison.

Use the table as a decision aid, not as a result. Only the control condition has earned its label; every swing percentage must be re-tested against the same one-bar MIDI, with humanization off, before it can replace straight 16ths as the working timing.

## And Copyable Worksheet

Run the test as a controlled render, not a preference poll. Set 84.000 BPM, load one bar of 16th-note hi-hat or kick-snare MIDI, use the same sample set, gain, and limiter, turn humanization and groove pool off, and export 24-bit WAV at a -6 dBFS peak. Change only the swing value between renders.

Checkpoint 1 fixes the DAW's swing definition before listening. Render one 16th pair and measure the first interval; at 84 BPM the pair lasts 357.143 ms, so the first interval equals that swing percentage of 357.143 ms. At the 61% midpoint, that is 217.857 ms first and 139.286 ms second. If the measured interval does not match, the percentage label is not comparable across tools.

Checkpoint 2 is the null test: render straight 16ths twice and confirm the files cancel. This verifies that the export chain is deterministic before any swing setting is judged.

Checkpoint 3 renders straight, 54%, 61%, and 68% at matched loudness. Checkpoint 4 randomizes the A/B/X listening order for blind comparison, then scores each candidate against straight in five repeated trials. Keep a swing setting only if it wins at least 3 of 5; otherwise keep straight 16ths as the control. Treat the 54–68% range as an untrusted headline hypothesis until it passes this worksheet.

Use the worksheet below as the reusable record for every candidate. Fill it before listening, then fill the score after the blind trials; a candidate that fails the null test, loudness match, or 3-of-5 rule is rejected even if it sounds subjectively better.

If 54% and 68% both lose to straight 16ths, keep straight 16ths at 84 BPM and move the groove change to velocity or accent variation. Do not rescue a losing percentage by changing the test material, monitoring level, or listener panel after the results are known.

Edge cases: if the DAW rounds the displayed percentage, record the rounded value and measured interval together; if a candidate wins 3 of 5 but only by a margin you cannot repeat, rerun the same five comparisons before promoting it; if the control take is altered in any way, restart the series instead of patching old results. Until a candidate passes both the measurement check and the blind-test gate, the 54–68% range remains an untrusted headline hypothesis.

## Frequently Asked Questions

**What measurement exposes a hidden denominator mismatch before comparing swing settings?**

Render one isolated pair at the target swing value and measure its first interval against the 357.143 ms pair; if it does not match the calculated share, the DAW is using a different denominator or note value.

**Which note-value pairings can change the meaning of the same swing percentage?**

Some sequencers apply swing to 8th-note pairs, others to 16th-note pairs, and implementations may define the percentage differently.

**Why render straight 16ths before the swung version in a controlled test?**

That straight render is the null-tested control because swing changes only relative placement within the pair.

**What should remain after nulling or phase-canceling identical elements?**

Any residual should represent timing displacement rather than level or tone changes.

**When can the proposed lo-fi swing range be treated as reliable?**

Only after the denominator is fixed and the same one-bar MIDI is rendered consistently; before that it remains an untrusted headline hypothesis.

**Does the supplied grounding support a drum-specific lo-fi swing protocol?**

No swing percentage, BPM, MIDI, onset deviation, or lo-fi drum-pattern protocol was present, so the headline swing claim has no drum-specific support in the supplied material.

## Quick answers

| Why is the denominator not universal when comparing swing settings across sequencers? | Some sequencers apply swing to 8th-note pairs while others apply it to 16th-note pairs, and implementations may define the percentage differently. |
| --- | --- |
| What step should be taken before comparing swing settings? | Render one isolated pair at the target swing value and measure its first interval against the 357.143 ms pair; if it does not match the calculated share, the DAW is using a different denominator or note value. |
| How does a null-tested control isolate the swing variable? | Render straight 16ths first, then compare the swung render to that control by nulling or phase-canceling identical elements, so any residual represents timing displacement rather than level or tone changes. |
| How should the 54–68% headline range be treated? | As an untrusted headline hypothesis until the denominator is fixed and the same one-bar MIDI is rendered consistently. |
| What did the evidence audit of the supplied grounding find? | No swing percentage, BPM, MIDI, onset deviation, or lo-fi drum-pattern protocol, meaning the headline swing claim has no drum-specific support in the material supplied. |

Also worth reading: **Lo-fi drum patterns: 90 Beats Per Minute Ableton Live Freeze Wins vs Bounce**: [Lo-fi drum patterns: 90 Beats](https://getrhythmm.com/blog/lo-fi-drum-patterns-90-beats-per-minute-ableton-live-freeze-wins-vs-bounce.php) · **Ableton Live 12 MIDI vs Bounce at 75 BPM Over 200 Bars**: [Ableton Live 12 MIDI vs](https://getrhythmm.com/blog/ableton-live-12-midi-vs-bounce-at-75-bpm-over-200-bars.php) · **2026 140 BPM AI Drums: -12 dB Sidechain Cuts Masking for Streams**: [2026 140 BPM AI Drums:](https://getrhythmm.com/blog/2026-140-bpm-ai-drums-12-db-sidechain-cuts-masking-for-streams.php)

### Related reading

- [55% vs 62% Swing: A Verify-Before-You-Commit Ableton Test](https://getrhythmm.com/blog/55-vs-62-swing-a-verify-before-you-commit-ableton-test.php)
- [Sync Licensing Audio Specs: 48 kHz/24-Bit WAV vs 44.1 — Do AI Rhythm Tools Export It?](https://getrhythmm.com/blog/sync-licensing-audio-specs-48-khz24-bit-wav-vs-441-do-ai-rhythm-tools-export-it.php)
- [Transient Shaper Settings: 1 ms vs 10 ms Attack and Release — Tighter or Smoother?](https://getrhythmm.com/blog/transient-shaper-settings-1-ms-vs-10-ms-attack-and-release-tighter-or-smoother.php)
- [Drum Levels With Live Bass: -12 dBFS for Shared Low End](https://getrhythmm.com/blog/drum-levels-with-live-bass-12-dbfs-for-shared-low-end.php)
- [Drum Timing Tests: 56% Is Continuous—Test Timing-Head Updates](https://getrhythmm.com/blog/drum-timing-tests-56-is-continuoustest-timing-head-updates.php)
- [Lo Fi Hip Hop Kicks: 3ms Synth Wins 4-1 vs Stack at -9 Loudness Units (LUFS)](https://getrhythmm.com/blog/lo-fi-hip-hop-kicks-3ms-synth-wins-4-1-vs-stack-at-9-loudness-units-lufs.php)

### Latest

- [55% vs 62% Swing: A Verify-Before-You-Commit Ableton Test](https://getrhythmm.com/blog/55-vs-62-swing-a-verify-before-you-commit-ableton-test.php)
- [Swing Quantization and Lo-Fi Drums: How to Verify a 10% Change in Ableton Live...](https://getrhythmm.com/blog/swing-quantization-and-lo-fi-drums-how-to-verify-a-10-change-in-ableton-live-12.php)
- [Sync Licensing Audio Specs: 48 kHz/24-Bit WAV vs 44.1 — Do AI Rhythm Tools...](https://getrhythmm.com/blog/sync-licensing-audio-specs-48-khz24-bit-wav-vs-441-do-ai-rhythm-tools-export-it.php)

Canonical: https://getrhythmm.com/blog/testing-84-bpm-lo-fi-swing-a-controlled-protocol-not-a-verdict.php
Markdown: https://getrhythmm.com/blog/testing-84-bpm-lo-fi-swing-a-controlled-protocol-not-a-verdict.php/index.md