Google Wants You To Vibe Code Audio Plugins

AI-assisted programming – aka, ‘vibe coding’ – is transforming software development, and is already making a big impact on the scope and variety of software and firmware available to electronic musicians.

Now, Google wants you to vibe code audio applications, saying that producers can now vibe code music production tools with Google Flow Music:

“Every artist, producer, and songwriter works differently. To match those individual creative workflows, Spaces in Google Flow Music lets creators build custom instruments or effects using natural language — no coding experience required.

Now, we’re making it easy to bring these capabilities directly into professional setups. Producers can now export their custom Spaces as VST3/AU plugins, to run inside their Digital Audio Workstations (DAWs).

Simply put, this means producers can easily build things tailored to their processes and styles within their familiar production workflows.”

Are you interested in vibe coding or the idea that you can create your own custom audio tools? Or is the explosion of new applications and firmware options creating ‘noise’ for you? Let us know in the comments!

12 thoughts on “Google Wants You To Vibe Code Audio Plugins”

  1. The unsuspected fun of vibecoding plugins (including AUv3 and CLAP) is in rethinking what you actually want from DAWful musicking. More than a cure for GAS, it can be a way to explore new approaches.
    We didn’t wait for Alphabet to pay attention, either. And we can already bypass JUCE.

  2. I recently build a VST3 using vibe coding. It’s a stereo input quadrophonic panner, that allows you to select from a set of predefince paths in quadrophonic space (spiral, circle, square, figure eight, follower, pendulum and more) and direction. The cycles are clocked to MIDI in whole, half, quarter, eighth and sixteenth notes, so there is a relationship to tempo and patter cycle speed. It is also supports manual mode, where you can yous your mouse/track pad/ball to place the input into the quadrophonic space. There is an X\Y display to visually indiate the path, with persistant trails and volume indicators in each corner to show the level sent to each speaker in the in quad field, adusting as the current panning posision follows its path in quad space. I am about 25 hours into in and will continue to improve. It’s written in C++ using the JUCE audio library. I do not code in C++, though I have ~30 years in IT engineering and architecture. Anyone can do this! You just have to learn how to set up all the tools (coding IDE, Git…etc.) Don’t be intimidated! Just give it a try. I started with the free copilot included in windows, and then subscribed to github copilot, which saved me from having to cut and paste code. Github Copilot intergrates with Visual Studio nicely, so it can paste code changes, automate the build process. It’s been a fun experiment, all to test ideas I want to implement into hardware using microcontrollers like the Daisyseed. It’s a brave new world, if AI doesn’t end our time on the earth or cause us all to be unenployed :-/

  3. with all the vibe coding I would actually love to see someone put out an empty hardware keyboard/knob synth with decent hardware specs an open source vibe codeable basethat you can use to just make whatever you want and experiment – you could even create a sort of visual vibe coding package where you can say use vibe coding to create a graphical representation and simulation that you can then load directly to the synth –

  4. i just used google flow to make a knockoff jomox resonant neuronium, no idea how close this is but it sounds neat and gets quite wild in a fun way.

  5. Way back in the early 2000’s, some SynthEdit plugin creations were cool and useful. The big majority of SynthEdit creations though… not so much!

    I have the same kind of feeling about this vibe-coding stuff… eventually, some will emerge that are unique and useful. So far though, what I’ve been seeing is just usual “run-of-the-mill” stuff. The GUIs in particular feel under-developed.

  6. it lets you try out some crazy stuff… i vibe coded a plugin for making sounds from Cymatic visuals.. you mess with the visuals to affect the sound… turns out, its not very musical sounding
    but its fun to try stuff like this to see what happens

  7. The detail that producers can “export their custom Spaces as VST3/AU plugins” is what makes this more than a toy. A browser-only instrument is easy to forget, but something that sits in the DAW next to the rest of a session might actually get used twice. I’d like to know whether Flow Music lets you open up and tweak the generated plugin afterward, or if every change means describing it again from scratch.

  8. I’m a programmer (a real, breathing, human one) and all the stuff I’ve seen “vibe-coded” has been very low quality stuff. Not a lot of thought put into the actual abstraction and implementation. And it’s spaghetti code. Even I have a hard time parsing out vibe-coded apps. And I make plugins using JUCE, and know C++ as well as Swift and numerous other languages. And I don’t think we’ll be going away in the music space, just like mass produced violins made in China haven’t devalued violins made by Stradivari, or Casio didn’t get rid of Steinway. There will be a desire for high-quality instruments by quality hand-makers of those instruments. Those instruments will just be digital now.

Leave a Reply

Your email address will not be published. Required fields are marked *