The KVR Developer Challenge 2026 Is Go

[Touch The Universe]

Maybe I'll jump in on this one with claude code etc. How about a plugin that inserts gaps of silence instead of muting for that same gate effect, so its not HELLO, the usual gate is H*L*0 but this method is H*E*L*L*O, etc. Unless this exists already and i can just download instead.

[Touch The Universe]

So I am up and running, compling my own code and exporting vst3's. now the fun part, adding dsp code, hopefully that I can customize. This is looking easier than I thought, though a headache on the backend on a mac with apple id stuff and xcode. but it seems i have the general flow worked out. JUCE framework, cursor with ai to compile code, with gtp and later claude, that utilizes xcode to export the vst3. Yay

[gambero]

AI generated stuff should be clearly marked. That should be part of the rules.... Just my 0,02

I think vibecoders shouldn't be allowed in this tbh

[wikter]

AI generated stuff should be clearly marked. That should be part of the rules.... Just my 0,02

I think vibecoders shouldn't be allowed in this tbh

As far as I know, ludites aren't banned here. Let's see what Claude can add. I've seen very interesting content coming front vibecoders. We're not judging programming skills, it's just about plugins.

[GaryG]

We're not judging programming skills, it's just about plugins.

I generally agree but the performance of the plugin should be judged too. If a plugin doing something simple maxes my CPU due to inefficient code then it should be marked down, that applies to trad or vibe-coded plugs of course.

[wikter]

We're not judging programming skills, it's just about plugins.

I generally agree but the performance of the plugin should be judged too. If a plugin doing something simple maxes my CPU due to inefficient code then it should be marked down, that applies to trad or vibe-coded plugs of course.

That's a good reason to avoid a plug-in, and this applies to hardcoded ones too.

[gambero]

As far as I know, luddites aren't banned here.

AI-bro gets mad he can't participate with 0 effort HAHA

[wikter]

As far as I know, luddites aren't banned here.

AI-bro gets mad he can't participate with 0 effort HAHA

Out of sense joke. Ai assisted DSP software means not 0 effort.
0 effort criticize? Oh, cheap, it's free.
Now tell me: which Code/environment sounds and performs better? C, Ai-assisted Code, ASM, Python, Pascal, Java, Sync Modular, Synthedit, Reaktor? Do your guess and add something useful to the thread.

[GaryG]

I generally agree but the performance of the plugin should be judged too. If a plugin doing something simple maxes my CPU due to inefficient code then it should be marked down, that applies to trad or vibe-coded plugs of course.

That's a good reason to avoid a plug-in, and this applies to hardcoded ones too.

Oh sure, that's what I meant by 'trad' coded plugs.

[gambero]

0 effort criticize? Oh, cheap, it's free.

Not much of a Developer Challenge if the dev is an LLM.
Also, keep in mind that I specifically mentioned vibecoders, not AI assistance.

[wikter]

0 effort criticize? Oh, cheap, it's free.

Not much of a Developer Challenge if the dev is an LLM.
Also, keep in mind that I specifically mentioned vibecoders, not AI assistance.

If you're a vibecoder, please read.
Apr 27, 2026

If you're someone who "vibecodes" audio plugins or any kind of audio software, here's a list of free resources to actually learn the basics of DSP applied to audio and music, in the hopes that one day you'll start to write your own software with your own knowledge.
1. Aaron Lanterman's ECE2026 Course

A really excellent, full GeorgiaTech course, completely available on Youtube for free. You'll need a quick refresher on trig and complex numbers. Watch it here.
2. DSP First

The curriculum on which the previous course is based. More here
3. The Scientist and Engineer's Guide to Digital Signal Processing

Another really excellent resource. This is a free book covering a lot of topics, many of which are also covered in the previous two resources. Read it here
4. Julius O Smith's CCRMA pages

Collection of notes and lectures by Julius O Smith III Read them here
5. The Theory and Technique of Electronic Music

A book by Miller Puckette (PureData, Max/MSP, important figure in music DSP). Read his book here. I recommend checking out his other resources too.
Tips on reading

Take your time, don't skip to conclusions, and especially DONT ASK LLMS TO SUMMARIZE IT FOR YOU. If you're stuck with anything, ask someone who knows on KVR or DSP StackExchange. Use a graphic programming language (PureData, Reaktor, Max or many others) to experiment and prototype. Learn GNU Octave. Learn Faust. Keyword is learn, If you can, turn off all AI features in your IDE.

Call me a luddite, but if you're proudly showing your stuff as vibecoded, I won't touch it with a 10 meter pole (more than 10 feet!). Put some effort in what you do, I promise you'll like it.

[gambero]

If you're a vibecoder...

Good job man! You found my website! You should've kept the links though, that's the most useful part of that page!

[wikter]

If you're a vibecoder...

Good job man! You found my website! You should've kept the links though, that's the most useful part of that page!

Nice, now you need just a vibecoder to read you. So isn't it easier to say: For vibecoders...
and maybe more constructive.
PD: Nice reverb btw.

[gambero]

So isn't it easier to say: For vibecoders...
and maybe more constructive.

What's more constructive than direct links to free resources?

Anyways, we're derailing the thread.
I maintain my position. Fully vibecoded entries should be banned or placed in a separate category.