JUCE adds a lot of garbage to the final release bundle, maybe uncompiled code as well. Try running all-in-one ripper from ExeInfoPE on a JUCE plugin DLL and just check out what gets dumped

 

Dang. I should learn C++ as well.

 

Getting complicated....

 

Nice thread, I'll revisit it later.

Creating VST (Virtual Studio Technology) plugins involves several aspects of coding, and it typically requires knowledge of C++ and familiarity with the VST SDK (Software Development Kit). If you have specific questions about VST plugin coding, feel free to ask, and I'll do my best to provide guidance on those aspects. Whether it's related to audio processing, user interfaces, or integrating the plugin into digital audio workstations (DAWs), I'm here to assist you.

 

I've been lurking, procrastinating and being a workaholic for too long. I'm about to have more free time than usual and I really want to sit down and make something cool.

Thank you for starting this.

 

many people who used something else before think that C++ would be more difficult or more "professional" than some of the other languages and tools.

in fact there is a lot of stuff which nowadays can be easier in native coding compared to capytalk, maxmsp, flowstone, you name it.


the main difference between these enviroments and C++ on the theoretical layer is that you can go deeper using C++ - if only you know how to.

simple examples: custom memory access, custom disc access, custom data types (such as multirate audio signals of different properties)

some o ther things are easier in graphical apps or specialized languages such as kyma, lisp, csound, max. mainly as they come with a bunch of examples and lively communites.


after almost 25 of maxmsp, when i look at AAX or VST SDK i am completely annoyed that you have to define and set all kind of abstract technial things for a project which are more or less the same for every plug-in.

i max, i couldnt care less if communication between compiled objects are atoms or something else and rather concentrate on the data itself and its mening to what i want to do.
in C++ i have to define such things in C++ terminology where in audio programming enviroments outputs are simply called "output".

otoh, making a proper GUI in max, supercollider or CSound is a science itself, where in modern interface builders you only had to press three buttons to do the same.

 

AI is now better at not only coding, but teaching you probably better than any human has time to teach. Grok3 can code. If you want to learn, have time, and are willing to commit to learning, it's not only doable but it's never been easier than it is now with AI. Got a question? can you read and write? Then use an industrial quality LLM as a learning aid.

 

interesting topic. things changed since. namely AI.
I also wanted to create a VST plugin myself.

Well lets say, it loads. functionalty isn't included as of now. but there is a window, a UI. WOHOO.

What I used:
1. claude code (inside WSL) with agents:
1.1 a project-coordinator/manager: has full oversights of the project and acts like a coordinator (coordinates work of other agents),
1.2 a coder: does the code stuff
1.3 a shell operator: who is aware of the OS environment, installed frameworks, etc. (has the EXPLICIT rights to install or change the (OS) environment - all other agents are not allowed to do so)
1.4 a research agent: web access for research (only used when the topics/problem is hugh)
2. frameworks: nih_plug (rust) and nih_plug_egui

this works quite well. so far

 

Last edited: Aug 24, 2025

ive been making so many plugins and apps with Cursor + Claude Code.

Installers, Project Managers, Audio Duplicate finders etc.. Loving this era of Idea to iteration