I wanted to share my first ever plugin with the JUCE community. It’s called Synerator - a VST3 instrument host that lets you load any soft synth and randomize its parameters to discover unexpected patches. Think of it as a sound design slot machine.
I’m a mixing/mastering engineer and EDM producer by trade, not a programmer. I built Synerator using JUCE and Claude AI over the course of a couple weeks - initial build in about two days, then another week or so getting Apple Developer notarization sorted out. It’s a universal binary on Mac (x86_64 + arm64) and runs on Windows.
I’ll be honest - I’m very new to C++ and JUCE. I leaned heavily on AI to get this built, and I know there’s a ton I still need to learn about the framework, memory management, DSP, all of it. Deadmau5 actually roasted me about this tonight and he’s not wrong. But this project lit a fire under me and I’m committed to learning the fundamentals properly as I continue developing it.
The core randomization engine works well and I’ve already gotten great feedback from early users. There are rough edges I’m actively working on - undo, MIDI CC blacklisting, saving plugin instances with presets — and I have a roadmap that includes an FX version and a multi-slot host called InSynerator.
Would love any feedback, criticism, or suggestions from people who actually know what they’re doing. Happy to answer questions about the process of building a plugin as a total beginner too, in case that’s useful to anyone else starting out.
So what we pay you for your vibe coded plugin and test it and tell you how it could be better? This is not the place for that, if it was open source maybe someone would take a look.
This is a software developer’s forum, where you ask us buy and test your vibe-coded plugin. It does not matter if you built it using JUCE if your post is in no way related to the code. Please realise that almost everyone here has worked for years developing their products. One could well argue that you have used a plagiarism machine to develop yours.
…and I’ll also gently point OP to the forum’s Code of Conduct, which begins:
Any content posted to this forum that is determined to be the output of generative artificial intelligence (large language models (LLMs), ChatGPT, Claude, Gemini, DeepSeek, Grok, Cursor, CoPilot, etc.) may be deleted without notice. Please do not use LLMs to help create content for this forum. Doing so will constitute unacceptable behaviour as set out in our code of conduct.
This forum is built upon the contributions of people within the audio development community, and its value as a resource of the community is that the content posted on the forum is predominantly thoughtful, correct and based on experience.
i test a lot of plugins (also one that is a lot like your new release btw, it’s called AudioDice), and i can tell you i typically get a plugin’s license for free in exchange for my work. for code reviews it would also help to open source the code. you should probably do that because especially in the beginning, and coming from no programming background, it is good to get help from actual human beings. LLMs include a lot of JUCE rookie mistakes like using unique_ptr for attachments to avoid initializer lists, using slider listeners at all or using getRawParameterValue in processBlock. none of this is fatal, but those are the most obvious mistakes everyone knows. I want you to know that not everyone and not every programming community is against vibe coding. the audio programmer youtuber for instance has a discord group with a vibe coding channel where we often discuss limitations and potentials of these techniques
