The Patch Bay Is Not a Product Roadmap

A backlash against an MCP demo, and none at all for stem separation - years-established technology whose next version was merely announced this week - or for Bitwig's in-house spectral stretch: the line music software users draw around AI runs through the signal path, not through the marketing.

Two arguments about artificial intelligence ran through music software this fortnight, and only one of them was new. The first arrived on r/Bitwig as a working demonstration: an MCP server - the same plumbing that lets software agents drive code editors - pointed at a DAW. The other argument is older than the demo that restarted it: the community's long-settled embrace of machine learning that ships as an instrument - stem separation, most visibly - rather than as an assistant. This fortnight's contribution to it was an update, not a launch: UVR's maintainer surfaced on October 6 to say the next version is coming. The first produced a backlash. The second produced beats.

The demonstration was real, which is what made it upsetting. Model Context Protocol is the layer that lets a general-purpose agent read and operate a host application, and pointed at Bitwig it did what such layers do: opened projects, nudged parameters, assembled clips, all from a chat window. Technically it is the most impressive thing that happened on that subreddit in weeks. The replies were mixed: a sympathetic current read the demo as a preview of assistive, batch-oriented patching, but the dominant counter-current, in a dozen phrasings, held one sentiment - the DAW is an instrument, and instruments do not take dictation. Nobody in the thread disputed that it worked. They disputed that working was the point.

It is worth steelmanning the demo before burying it. Agents driving a DAW could genuinely help with batch preparation, accessibility for musicians whose hands cannot reach the interface, and the tedious migration of projects between arrangements. If a protocol lets someone with limited mobility sculpt a mix by conversation, the patch bay has just been widened, not bypassed. The objection in the thread was never about those users. It was about the default future the demo sketched, in which the person with hands becomes the bottleneck to be optimized out.

Now look at what the same community appears to have adopted without an argument. UVR, the open-source stem separator, has been unmixing records since long before this fortnight's demo - its Roformer-era v5.6 release dates to September 2023 - and in all that time, on this desk's reading, the argument that greeted the MCP server never arrived. We cannot cite a thread that does not exist; what the record supports is the absence of the complaint, and we will take that observation as ours rather than the community's. The dated news is housekeeping, not hype: on October 6 the maintainer broke a long silence with a development update confirming UVR 6 - a rebuilt PySide interface, a modernized dependency stack, and a release promised within six weeks. Nobody calls UVR an AI product. It is a vacuum cleaner, and the room it cleans is the entire twentieth century's catalog.

The same week, zc devices opened a free public beta of thicket with an introductory post on r/modular, and the post describes a polyphonic modular synth - fifty hand-crafted nodes, first-class MPE, free while the beta runs. That is an instrument pitched at the patch cable, not a model pitched at a benchmark, and the description says so plainly. The features that get used are the ones that never interrupt the session to announce themselves.

And Bitwig itself, the company whose community produced the MCP thread, shipped the third argument back in August, and it is not a machine-learning one. The 6.1 update (announced here, with the full release notes) rebuilds the Sampler around slicing, a new Spectral stretch mode and direct Grid integration. Spectral is documented the old-fashioned way: the release notes call it the product of modern advances and in-house DSP work, a purpose-built stretching algorithm - no model weights, no API key, no preamble about responsible scaling. It shipped as a checkbox in a changelog. No chat window. No apology tour. Just a lever that does something the hands could not.

That is the distinction the backlash is actually drawing, and it deserves to be drawn with more care than the word Luddite allows. The tools that got welcomed remove a chore: the chore of unmixing stems by hand, of scribbling granular maps on paper, of stretching a break without it sounding like a tape deck in mourning. The tool that got heckled proposed removing the musician - or at least inserting a representative between the musician and the signal path, with all the latency and mystery that intermediaries bring. The DAW's oldest promise is that cause leads to effect, visibly, under your hands. A patch bay is a contract. A chatbot is a middleman, and middlemen have to earn their commission.

So the position of this desk, with the r/Bitwig thread as Exhibit A: judge AI in the DAW by what it leaves on the table. A feature that widens the instrument's range - new spectra, new stems, new grains - is on the instrument's side of the desk, whatever technique produced it. A feature whose pitch is that you need not attend the session at all is selling absence, and absence is the one thing a studio was built to avoid. MCP in the DAW will find its rightful, narrow place - the accessibility harness, the batch librarian - and then it will stop expanding, because the community has already been litigating the boundary, in the thread's own mixed register - part wishlist, part downvote.

There is a coda in the news this fortnight that makes the point sideways. Teenage Engineering, a company that sells an aesthetic as much as circuitry, told an interviewer it is considering getting out of synths altogether - MusicTech has the story

• because, roughly, the brand believes it is more than its instruments. Two futures of the tool, then: one in which the maker walks away from the instrument, and one in which the software walks away from the maker. Both are worth resisting, for the same reason. The relationship between a musician and a machine they have wired up by hand is not a market to be disrupted. It is the entire product, and everyone holding a patch cable already knew that.

The relationship between a musician and a machine they have wired up by hand is not a market to be disrupted. It is the entire product, and everyone holding a patch cable already knew that.