Backline

Changelog

Here's what's new.

We're cooking fast, so keep watching for new features.

    • Open your linked agent straight into a first chat about your rig, as the last step before the app
    • Connect Claude, Codex or Cursor in one click, from the Connect panel or during onboarding
    • A plugin that crashes stops only the audio: the window, the chat and the project stay, and Backline names the plugin and offers to restart with or without it
    • A plugin that stops responding keeps its sound and comes back on Retry, and a warning says when a plugin that changed shape cost a cable
    • AUv3 plugins such as AutoPad load into a rig, and a plugin that is missing or still loading keeps its place, cables and sound
    • A continuous control can take a curve: exp, log, S or steps, picked and dragged in its popover or written with Curve in code
    • A rig can have several MIDI Ins, each playing only its own keyboard, and a MIDI strip picks its MIDI device directly
    • A control saved into one scene for the first time fills into every other scene, and any scene still missing a control says why
    • A strip's plugin picker lists by category as well as by maker, and searches names, makers and categories at once
    • Knobs and faders on the workbench show where the hardware sits
    • Add a MIDI split: one keyboard in, up to eight layers out, each to an instrument of its own
    • The scroll wheel turns knobs and rides faders on the workbench
    • The chat asks several questions in one go, a step at a time, with Back to change an answer
    • The assistant builds keyboard rigs from channel strips, one layer per strip with reverb on a send
    • Pick a plugin for a channel strip from a menu of that kind, by maker
    • Channel strips stand side by side on one mixer board, with sixteen built-in buses and a send that brings its own Aux strip
    • Add channel strips to the patchbay: drop plugins into an audio or MIDI strip, route it by menu to the soundcard or a bus, with pan, fader, mute, sends and a solo that keeps its path live
    • Workbench menu splits into Frame Templates and Panel Templates: replace a rig's panel with a pedalboard or keyboard starter, flat or 3D
    • Quickstart reads what you are building and starts keys players on a keyboard: flat and 3D keys starters beside the pedalboard
    • Let a control move under a hand or its MIDI before it has a target, then snap to the target once mapped
    • Name a control from its id when it has no label ("delayMix" reads "Delay Mix"), and turn a name off with `label: null`
    • Write each rig as one file, `custom/rigs/<rig>.tsx`, holding its controls and its panel
    • Map MIDI to one controller by name, remember controllers in Settings › MIDI devices, and pin a control's MIDI in code with `Midi.cc(21, { device: Devices.mc6Pro })`
    • See each rig's types, its nodes and every node's parameters, in a read-only `types/<rig>.d.ts` that rewrites itself as the rig changes
    • Rename a rig or node from the code editor with F2, and open what `Rigs.verse.nodes.amp1` stands for with go to definition
    • Add a 3D Novation Launch Control XL and a flat keys panel of four sound columns to the replicas package
    • Start new projects with a folder per rig: its controls in one file, its panel in another, and pedals laid out on a grid
    • Name rigs, nodes and parameters in a screen's code (`Rigs.verse.nodes.helixNative1.parameters.inputGain`), with completion and warnings in the editor
    • Map a footswitch to open and close the tuner, through a System node every rig carries
    • Upgrade the workbench library and have the Chat rewrite your screen for the releases that need it
    • Add packages to the workbench, each versioned and checked against the library it was built on, starting with 3D replicas of the BigSky, TS9 and nanoKONTROL
    • Buy Backline from a paywall in the app, every option priced in full and paid in the browser with no second sign-in
    • Sign in with a code emailed to you, typed into the app, without opening a browser
    • Onboard new users: scan plugins first, sign in while it runs, and answer three questions about how they play
    • Switch the 3D pedalboard between its angled view and a top-down plan
    • Apply one control's value to every scene from its popover, with a confirmation when the scenes disagree
    • Attach text files to the chat (logs, CSV, JSON, notes) alongside images
    • Keep several setlists in a project and switch between them from the setlist sidebar
    • The chat tidies the patchbay after it changes the rig, and stacks the plugins it adds top to bottom (a switch in Settings turns the tidy off)
    • Pick what a control drives from its right-click popover, unless the screen's code already says
    • Controls say whether they are a knob, a toggle or a trigger, so a latching footswitch stays latched on anything it drives
    • Tidy up the patchbay in one press: cards arranged top to bottom along their cables
    • Search across the workbench's files, and step back and forward through the ones you opened
    • Remember each project's audio interface, and keep its cables when it is unplugged
    • Add a pricing page with Plus and Pro assistant tiers
    • Sign in to open Backline, on up to three computers, with a buy through Paddle
    • Let the assistant play the rig, not just build it
    • Swap a plugin by dropping another card on top of it, cables and all
    • Browse the plugin library by category as well as by maker
    • Open a new project on three questions, then build its first rig from the chat
    • Seed a workbench flat as well as in perspective
    • Add a MIDI velocity curve, with threshold, ratio and make up
    • Name a mixer's output pairs, and switch a send in and out of the mix
    • Split and join mixer channels, and send a channel to more than one output pair
    • Draw built-in plugin editors as web pages
    • Patch a card into its neighbours, from its plug or by dragging it against them
    • Add MIDI transposer