Google has announced that producers can now "vibe code" music production tools with Google Flow Music. According to Synthtopia's report, a feature called Spaces lets users describe a custom instrument or effect in natural language, with no coding experience required, then export it as a plugin for use in a DAW. The announcement is on Google's blog.
The coverage doesn't mention MPE, and details such as pricing, release date and platforms were not given. That leaves a lot of open questions, and some of them matter to expressive musicians.
What Was Announced
Based on the available reporting:
- Natural-language creation. You describe what you want, and the tool builds it.
- Plugin export. Spaces can be exported as VST3 and AU plugins that run inside a DAW.
- No coding required. Google positions it for producers, not developers.
Everything beyond that, including how complex the generated instruments can be, is unconfirmed at the time of writing.
Why MPE Players Should Care
MPE support has historically depended on developers doing deliberate work. A plugin must be able to receive a MIDI channel per note, interpret pitch bend, pressure and slide per voice, and handle the configured pitch bend range correctly. Many plugins get this wrong or only partly right, which is why our guide on fixing pitch bend range mismatches remains one of the most practical reads for new MPE users.
A tool that generates plugins from prompts raises two possibilities:
- It could make expressive instruments easier to build. If a generator understands MPE well, someone could describe "a synth where slide controls filter and pressure controls brightness per note" and get a working instrument. That would lower the barrier for custom expressive sounds.
- It could also multiply plugins with shaky MIDI handling. If generated plugins default to treating all notes on one channel, MPE controllers will behave like ordinary keyboards, or worse, produce glitches when pitch bend affects every voice at once.
Which outcome becomes reality depends on whether Spaces exposes MPE as a first-class option. Nothing announced so far says either way.
Questions Worth Asking
When more details emerge, expressive musicians should look for answers to a few things:
- Can a generated instrument receive MPE MIDI in a lower zone configuration?
- Is per-note pitch bend range adjustable, and does it respect the standard defaults?
- Are pressure and slide (CC74) mappable to parameters per voice?
- How does the exported plugin behave in DAWs that handle MPE differently?
For reference, our overview of what MPE support in a plugin update really means explains how to judge such claims.
A Cautious Perspective
Prompt-built software tends to be impressive in demos and uneven in edge cases. MPE is an edge case by its nature: it asks a plugin to track many simultaneous notes, each with several continuous controls. Testing is simple but important. Play a chord, bend one note, and listen for whether only that note moves.
There is also a broader creative upside. Many musicians have a clear idea of how they want to be expressive but lack the programming skills to build the instrument. If tools like this learn to handle per-note expression, they could open a new category of personal instruments.
What to Do Now
There is nothing to download yet beyond what Google has published, so the practical advice is modest:
- Watch for specifics in Google's documentation as it develops.
- Test any exported plugin with your MPE controller before trusting it in a project.
- Keep your existing MPE-ready instruments as your reliable core, and treat generated plugins as experiments.
Key takeaways: Google Flow Music's Spaces feature promises plugin creation from natural language with VST3 and AU export; MPE is not mentioned in the announcement; and the real test for expressive players will be whether generated instruments handle per-note channels, pitch bend range and slide correctly.