Scaler Music Scaler 3.3 [WiN]

• Product: Scaler 3
• Developer: Scaler Music
• Version: 3.3.0
• Format: Standalone, VST, VST3, AAX
• Requirements: Windows 8 or later
• Source: scalermusic.com/products/scaler-3

Scaler 3.3 is a MIDI chord and arrangement plugin from Scaler Music, running standalone or as a VST, VST3, AU, and AAX plugin inside any DAW. The update centers on Multi-Bind, which lets one MIDI controller trigger and loop chord, motion, and rhythm lanes together instead of one bound track at a time. Detect Mode now runs as a dedicated capture path with its own live history log, separate from standard MIDI capture. It answers searches for chord software built to layer and loop multiple arrangement lanes from one keyboard.

Key Takeaway

Multi-Bind activates once a session already has separate chord, motion, and rhythm lanes built, letting a producer trigger and loop them together from one controller instead of switching bound tracks. It displaces manual per-track auditioning during live takes. The main chord track must stay bound for the other lanes to loop correctly. Producers running one bound track can skip it.

Bound Lanes That Loop Independently

Multi-Bind extends binding from the single main chord track to any combination of chord, motion, and rhythm tracks at once, so one MIDI controller triggers every bound lane from the same keypress. Each bound lane loops the section its own playhead is currently sitting in rather than the section the main track is in, so a motion track can keep repeating a two-bar phrase while the chord track advances underneath it. Play-quantize, when enabled, locks incoming live triggers to the beat and the current chord’s remaining duration rather than firing instantly.

Any bound lane can be muted independently during playback — dropping the chord track leaves only the bass-follow and beat lanes audible, or dropping everything but one motion track isolates a single arpeggio pattern for review. This turns arrangement auditioning into a live mixing decision instead of a stop-start process of soloing tracks in a mixer panel. Switching which lanes are audible does not restart playback or reset loop points.

The main chord track has to remain bound for the session to function at all, since every other bound lane derives its chord identity and loop boundaries from wherever the main track’s playhead sits. Muting the main track removes it from the mix but does not remove this dependency — motion, bass-follow, and beat lanes still read their loop points from the main track’s chord changes even when it is silent. A session built entirely around secondary lanes with the main track unbound will not loop correctly.

Live performers building layered arrangements on the fly get the clearest use from Multi-Bind, since it replaces manual track switching with real-time lane muting. Producers assembling one fixed loop per session have no lanes to bind beyond the main track and see no change in workflow.

A Detection Log That Stays Live

Detect Mode now runs from its own dedicated record button rather than sharing the record/multi dropdown with standard MIDI capture, so pressing it opens a chord-recognition pass instead of a raw MIDI grab. Playing chords, single notes, or a scale into it produces a running detection history that updates in real time and stays open while switching between browsing existing chord sets and recording new detections. Each entry in the history can be renamed, bound directly, saved as a user chord set, or deleted individually without clearing the rest of the log.

The same detection engine accepts dragged-in MIDI files, audio files loaded through a folder browser, or live audio recorded directly into the plugin, running the same chord and scale recognition pass regardless of source. MIDI Capture runs as a separate dedicated button and records raw MIDI performance rather than detected chord identities, and the two capture paths can run at the same time — Detect Mode logging chord recognition while MIDI Capture records the underlying performance for export.

The underlying chord-recognition method is unchanged from earlier Scaler versions — 3.3 restructures how detections are captured and logged, not how accurately a played or recorded passage gets identified. A session relying on ambiguous or heavily processed audio for detection gets the same recognition results it would have gotten in Scaler 2, just with a persistent log to review afterward instead of a single detection result that gets overwritten by the next pass.

Producers transcribing existing recordings or programmed MIDI into usable chord sets get the most use from the persistent log, since past detections stay accessible instead of disappearing after the next capture. Producers who only browse existing chord sets and never record source material rarely open Detect Mode at all.

One Playhead Across Every Page

The main track in the Arrange page now shows a visible, scrollable timeline with a playhead position, replacing the flat lane-only view earlier versions used. Clicking anywhere on the timeline sets loop start and end points without disturbing which chords are bound to which keys.

That playhead position now carries across pages: leaving a chord selected at a specific timeline position and switching to Circle of Fifths, Colors, or the Create page keeps that same position selected, so a chord picked in Colors mode inserts or replaces at the exact point the playhead was left rather than requiring a return trip to Arrange first. Insert pushes every later chord forward to make room; replace swaps only the chord at that position and leaves the surrounding arrangement untouched.

Shift-click selection across the timeline now selects every chord between the two clicked points rather than requiring individual clicks per chord, so replacing a run of chords at a specific measure is a single select-and-replace action instead of one edit per chord.

The visible timeline itself is scoped to the main chord track, so bound motion, bass-follow, and beat lanes don’t get their own on-screen ruler alongside it — adjusting a secondary lane’s loop points still means switching to that lane directly. Producers building arrangements across Circle of Fifths, Colors, and the Create page in the same session get the clearest speed gain from the carried-over playhead. Producers who stay inside a single page for the whole session see little change.

Motions Untied From Track Type

Motions — Scaler’s arpeggio, phrase, performance, and bassline content — no longer require a matching track type to preview or use; a motion designed as a phrase can be dropped into what was previously an arpeggio-only track without creating a new track first. Arming the track auditions the motion with the currently loaded instrument’s actual sound rather than a generic preview tone, so switching between two candidate motions is an immediate A/B on the real patch rather than a silent comparison.

Multiple motions can be auditioned against the same chord in sequence without leaving the track — swapping from one performance-type motion to a different one on the same bound chord happens with a single click and no re-binding step. Any track can now be renamed independently of the motion type loaded into it, since the track is no longer locked to being “an arpeggio track” or “a phrase track” by name.

A dedicated user track can run Multi-Bind’s chord input against a hosted instrument with a “scale notes mapped” option turned on, which snaps every played note to the currently active scale rather than passing raw keyboard input through — playing loosely around a target note maps it to the nearest in-scale pitch instead of the literal note played.

Scale-notes-mapped is not on by default — enabling it is a manual toggle per user track, and only after activation does keyboard input to that track snap to the active scale. Producers assembling melodic ideas from multiple decoupled motions and hosted instruments get the clearest benefit from this workflow, since sound and structure can now be recombined without rebuilding tracks. Producers working from Scaler’s fixed internal 50-sound library with one motion type per session see little change from the update.

No Unbinding the Main Chord Track

Muting the main track drops it from the mix, not from the session’s dependency chain — every bound motion, bass-follow, and beat lane keeps reading its loop boundaries from wherever the main track’s chords fall, silent or not.

FAQs