Beat Sync Explained: Pulse, Hits and Shake

Continuous motion is the easy half of a visualizer — bars that follow loudness, particles that swell with energy. The thing that makes a scene feel locked to a song is discrete: a visible hit that lands on every single beat. In Novus, beat sync means exactly that — one clean, countable hit per beat, produced deterministically so the export is identical to the preview. This post walks the pipeline from raw audio to that hit, then shows how to tune it with the three controls that shape it: Beat Response, Pulse Intensity and Shake Amount.

Two kinds of reactivity

Every engine mixes two response styles. Continuous reactivity tracks levels — spectrum height, particle density, glow strength follow the energy of the track from moment to moment. Discrete reactivity fires events: on each beat, the scene visibly punches. Continuous motion makes a scene feel alive; discrete hits are what a viewer actually perceives as “synced.” If you have read How Music Visualizers Work, continuous reactivity is the FFT side of the story — this post is about the beats.

From track to beat grid

When you load a song, Novus analyzes it up front: it estimates the tempo (BPM) and lays a beat grid across the whole file, and each grid point becomes a scheduled hit. Because the analysis happens once on the complete track rather than being guessed live during playback, the schedule never wavers — the same file with the same settings produces the same hits on every play, and the export replays that exact schedule. There is no re-listening at render time, so a hit you see at 0:47 in the preview lands at 0:47 in the finished MP4.

Why silence stays still

A naive beat grid has an embarrassing failure mode: it keeps ticking through silence. The intro fades in, the bridge drops to a lone vocal, the outro rings out — and the visuals keep pulsing to a metronome nobody can hear. Novus gates hits against the actual energy of the track: a grid point only fires as a hit where the music genuinely carries a beat, so quiet passages hold still and breakdowns feel like breakdowns. When the drums come back, the hits come back with them. That gate is the difference between “synced to the song” and “a metronome stapled over the song.”

The three controls that shape a hit

• Beat Response — the master depth of the reaction: how much the scene as a whole leans into each hit. This is the first knob to reach for when everything feels too strong or too subtle.
• Pulse Intensity — the size of the pulse each hit produces: how far elements swell and brighten on the beat before easing back.
• Shake Amount — a brief frame shake on each hit. A little reads as impact; a lot reads as chaos. It is the most powerful and the easiest to overdo.

A supporting cast rounds out the feel: Rotation Speed adds continuous motion between hits so the scene never sits frozen, and glow and chromatic aberration style the frame so each punch lands with more atmosphere. None of these change when hits happen — only how they look.

Tuning by genre

• EDM, hip-hop, trap — the beat is the product: Beat Response high, Pulse Intensity strong, Shake Amount moderate. Four-on-the-floor tracks can take more than you think.
• Rock and indie — live drums breathe, so go medium across the board; an overly rigid pulse fights the human timing.
• Pop and vocal-led — medium pulse, low shake, so the frame stays steady enough for text and faces to read.
• Ambient, acoustic, lo-fi — Pulse Intensity low and Shake Amount at zero; let continuous reactivity carry the scene and treat hits as punctuation, not percussion.

Troubleshooting

• The scene feels twitchy — lower Shake Amount before touching anything else; shake exaggerates every hit.
• The scene feels flat — raise Pulse Intensity first, then Beat Response. Pulse changes what a hit looks like; response changes how much of the scene joins in.
• Hits feel double-time or half-time — tempo detection can lock to twice or half the tempo you tap your foot to. Neither is wrong; tune by ear, and if every-beat hits feel busy, ease Pulse Intensity down so only the strong beats read.
• Hits look weak in this engine — different engines spend hits differently: Bars snap, Tunnel lunges forward, Radial swells. Try the same track in a second engine before blaming the settings.

Determinism: preview equals export

Because the hit schedule is computed from the file rather than improvised in real time, the render you export is the render you previewed — same beats, same pulses, same shakes, frame for frame. That makes tuning trustworthy: what you sign off on is what your audience sees. Open a beat-forward look such as stacked-bands in the editor, drop in your loudest track, and work the three controls until the drop feels inevitable. For which engines spend their hits best on your style of music, start with the engine tour.