Vibe Coding Log - Sharing Journey - Git - Glitch/Time Warping FX - More MIT delays, A dozen types of Lush Supersaws

[Touch The Universe]

You better listen to Claude. Licensing is a special mine field, and GPL is a toxic and very strong copyleft license. If you incorporate GPL-licensed code into your project in a way that triggers its terms, your derived work must also be released under the GPL. Attempting to find loopholes or ‘workarounds’ is often a sign that the integration likely already falls under GPL obligations. Don't.

Two options. Avoid GPL licensed code under all circumstances. Don't even try to "borrow" parts of it with the goal to escape the licensing afterwards. And the other option is, simply put the whole project under GPL.

Both ways can bite you. There are licensing terms that contradicts the GPL. We have this for example with open source graphics software. Autodesks FBX SDK has a license that is incompatible to the GPL, which Blender uses. And this leads to the absurd situation that the Blender developers needs to reverse engineer the FBX SDK with every new version.

That's the vibe I got, better safe than sorry, especially since the facsimile is so close. But's it's legitimately a fundamentally different things I am implementing from what I read. The Original is like a tapestop, this is a contineous generator signal. They share the same name, scrape, though.

Yet I'm still not convinced. Hopefully someone with confidence is kind enough to chime in on the difference wise. Even if they say it's unique code, I'd still run it by the orginal author. In fact, it's his code, so I'm sure he'd know best. Best to ask him.

I might one of these days just release an GPL3 synth because there is so much awesome stuff out there. Just combine the cream of the crop into one GPL since, think surge xt, vital, dexed, etc and add a little bit more, just for fun. It's simple enough, and fun enough to sustain the effort in my opinion. Consolidate the best of the best GPL verbs, delays, any other fx. That would be awesome. Right now, I'm combining the best MIT stuff I can find to give me a wide enough range of sounds to sound design so I don't feel a bit limited. I'm a bit crazy on that regard so only 10 delays, 10 verbs, lots of types of synthesis, (all, haha) sample import, multi samples at that ,and at some point i want to add scripting support so nothing is lacking for indepth sample stuff like kontakt or what not.

[Touch The Universe]

Once I'm done with the delays, I might implement a few more small fx like detune, ring mod etc, then I'll focus on removing bloat and stuff I don't need. I can probably remove 10 pages of testing stuff. I'm hoping to have a master osc of 3 layers with as many different types of synthesis I thing useful. Some of these pages will have an advanced button that opens up an entire page of more knobs. I still need to fill in this section, about 5-7 new types of synthesis yet to be added and i want to implement a unique type of INSANE wavetable synthesis if possible. It's laughably insane if it's possible, will depend on interpolation logics to see if it's pheasable. Also have a really unique idea for importing wavetables as well.

Then, I will create a master interface that simplifies that monstrosity into a digestable interface, or a couple versions. Think of how nexus was before it opened. Nice, clean. I can maybe have a closed off version just for myself or other sound designs if interested. Still deciding, though generally, I don't want to hide the synthesis options if I can help it. The main point is to have sound design in and sell banks to be honest. It might be such a cpu hog, it's be the nicer thing to close it off so people don't get angry cause they can't add more layers or stuff with it breaking. Will see.

[Touch The Universe]

Reached out to the guy on linked in. https://www.linkedin.com/in/joaquim-bro ... ivity/all/

and opened up and issue here.. https://github.com/qbroquetas/IV-XDelay/issues/2


First day using git desktop has been quite beneficial, my mind feels more ordered and a little bit more safer. This is not a bad workflow, thanks to whoever recommended that

It is psychological, more than anything, lol

Screenshot 2026-06-05 at 1.09.00 PM.png

[TechHaus]

Too late now but these vibe coding videos really should not have been on your professional sound packs channel.

[Tiles]

But's it's legitimately a fundamentally different things I am implementing from what I read.

Doesn't matter. One line of GPL code in a project means the entire project must be distributed under the GPL. It's really that simple.

There is a third option: write the code yourself. But AI does that for you. And from what I've read, you've already fed it GPL code. At that point, that's pretty much the end of the discussion.

GPL is a toxic copyleft license. It effectively "infects" the code it touches with its licensing requirements.

EDIT, after reading your issue at the effect manufacturer page, that's indeed option number four. A dual licensing, a private agreement with the original author. Fingers crossed that you can find such an agreement with him. Question is if he can. The reason why his effect is GPL might be that he uses a GPL part from somebody else already.

[Tiles]

Too late now but these vibe coding videos really should not have been on your professional sound packs channel.

Agreed. He could always put it into its own playlist if he want.

[whyterabbyt]

That's the vibe I got, better safe than sorry, especially since the facsimile is so close. But's it's legitimately a fundamentally different things I am implementing from what I read.

That's completely irrelevant. If you're directly using or deriving from GPL'd code in your project then it doesnt matter at all what you're using it for, whether that's the original purpose or not; all the code in the project has to be GPL'd.

And yes, that also means if you're directly using or deriving from code with some other license in your project, then you have almost certainly created a significant problem for yourself because you cant just relicense other people's non-GPL code under the GPL.

[Tiles]

Yeah, good point. As told, licensing is a special minefield