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

[Tiles]

XD

I tended to do that back in the days when i developed games. For one of my games i ended in an equal amount of build folders like you then, a whopping 2 gb each. Which was the point when i finally migrated to Git. And i eagerly recommend to do the same.

I know it is a bit nasty until you know how it works and until you have set up everything. But with help of AI this is a breeze nowadays. On Windows you can make your life a bit easier with graphical frontends like Git Kraken or Tortoisegit. The latter i would recommend anyways. Easy access to the log ...

Versioning has lots of benefits. Size is just one of it. Every commit shows the code changes for example. So you can follow back the features to the root. Which is super useful to catch some stuff that you did eons ago. This needs of course a bit discipline, doing the commits in a useful manner and with a proper title and description. But with a thousand zip folders you will never find anything anymore.

[Touch The Universe]

Would be cool to simplify the monster in a cover gui like this

4031b501-c84b-42ba-8afb-ca078759f2dc (2).png

[Tiles]

Please choose something else more capable ^^

This UI is clear, no question, but it has low contrast and tiny fonts, and is a good candidate for headache.

[Touch The Universe]

Please choose something else more capable ^^

This UI is clear, no question, but it has low contrast and tiny fonts, and is a good candidate for headache.

oh, haha, no worries, just pay attention the center console, 3-d panels, not the controls on the page or size of the fonts, that drives me crazy. Those will be changed to something more useable, and more clear, atleast ill try

[TechHaus]

Approaching 3 weeks, you could have taken a coding boot camp (and not drained several ponds that our kids will never get to see).

Anyway, good luck getting to the finish line, still.

[Touch The Universe]

Approaching 3 weeks, you could have taken a coding boot camp (and not drained several ponds that our kids will never get to see).

Anyway, good luck getting to the finish line, still.

3 weeks even a deep dive won't be enough as far as I can tell. Why learn code with this thing?

I can think of reasons, just making a counter point. Would you pay to take a html/css class these days?

The ponds are a thing. There is a cost, hope its as simple as water, electricity. I still don't entirely trust this tech. It's weird.

King od getting antsy to wrap this thing up, not going to lie. So probably just fine tuning at this p9int, no new crazy ideas.

Easier said than done

[starflakeprj]

I have, as a complete disaster when it comes to coding, tested to vibe code a few things. Pretty easy projects compared to yours. I've had a few ideas, but I have also completely failed a few projects due to not having a clue about coding. I feel that with vibe coding, it's always good to know a few bits and pieces when it comes to coding.

I have been quite mean to ChatGPT at times when it has completely ruined my code, and I have spent hours trying to get ChatGPT to correct the code, only to later notice that it forgets to remove code that isn't being used at all. So, to my understanding, coding done together with an AI is not very clean or effective.

I would probably go deeper into vibe coding for a few commercial apps that I have been thinking of, if it weren't for the fact that I would never trust it to help out with bugs, as this is what users would expect if you were ever thinking about selling the software.

Happy to follow your progress though; you have come far in quite a short time

[Tiles]

Yep. Vibe coding without any clue does simply not turn out well

[Touch The Universe]

I have, as a complete disaster when it comes to coding, tested to vibe code a few things. Pretty easy projects compared to yours. I've had a few ideas, but I have also completely failed a few projects due to not having a clue about coding. I feel that with vibe coding, it's always good to know a few bits and pieces when it comes to coding.

I have been quite mean to ChatGPT at times when it has completely ruined my code, and I have spent hours trying to get ChatGPT to correct the code, only to later notice that it forgets to remove code that isn't being used at all. So, to my understanding, coding done together with an AI is not very clean or effective.

I would probably go deeper into vibe coding for a few commercial apps that I have been thinking of, if it weren't for the fact that I would never trust it to help out with bugs, as this is what users would expect if you were ever thinking about selling the software.

Happy to follow your progress though; you have come far in quite a short time

I noticed this. It likes to hide the code, or worse hide the knobs on the screen, though they still affect the sound, haha - out of sight out of mind. It did this one time, out of 1000, so it's not a big issue, but i have no doubt a lot of code can be removed from previous ideas and likely, i need to refractor the 4 massive pluginprocessor and plugineditor files i have. I bunched up all the code in these two documents to be "easier" to track, lol, but for working with ai and tokens, going through such huge documents is a waste, though still can't bring myself to likely devote a whole day to this task.

I also agree, maybe a bit more, knowing coding, or even better the logic,science, or math of whatever you are working on is very important, atleast the general ideas. After learning about reverbs, now i know atleast what to request in a prompt, before i was getting explosions by having feedback come from two sources, the diffusion feedback or the other the delay feedback in the matrices. This can cause explosions, but moments beforehand there is quite a lovely, lush bloom of sound before violence, haha. Next time i go in for reverb, i want to see if i can tame such a wild beast, have quite a few ideas to manage and make use of, but the idea is so huge, it literally is a mountain of a concept that can be it's own seperate thing, so holding off on that, though i'm sure half the ideas will be either not work, or not be so "great" as i think haha. The fun part is finding out what works, then dreaming up other "bad" ideas. I love that part, haha.

Some bits are frustrating with gtp, seems after every edit, some new thing was added but something we just finished was dropped off. i noticed it this time, did it happen before without me noticing? I think this happens with the conversation gets too long, it drops thing, so starting a new chat seems to be the thing to do when noticing this, any issue, or mistake AND it's a long chat, just assume its the limit token per chat causing the issue and begin again, my 2c

[Tiles]

ChatGPT looses context very quick. Claude is much better in keeping context. You could work with a summary and starting a fresh chat when you notice the drop.

[Touch The Universe]

Yep. Vibe coding without any clue does simply not turn out well

Depends on what you mean For the reverb, yes, violence was a result. For coming up with the feedback osc, with a prompt give me the feedback in the oberheim or the legend, and it gave, bleh, so i had to research a bit and describe what i wanted more clearly, there is resonance first 40% of the knob turn. It was so important i had them create a whole panel to tweak just this resonace behavior in the feedback knob and the results can be very interesting, i might keep the panel in there, like a uhe though on steroids. I also usually am like this sounds, good, keep this version then try a variant, and give me a variant filter to try in conjunction with the feedback to see fi it makes a difference, and it does. So, it's like a mini science project. I know nothing of code, but if you can describe in detail waht you hear, that you like, as i said earlier, what your taste it, and wont' settle until you get it, you likely will with patience. You don't need to know code, but you need to articulate taste, which ALWAYS is imporved with learning about the core concept, like feedback, and the components that cause it and make it up. If you are unsure what elements are important, just request the variable and numbers that can affect the sound in the equation, just give me knobs for those variables so i can tweak and find the sweet spot. It usually works, haha.

Maybe ill record a trial and error, troubleshootin, learning how to prompt to get what you are after video, to document how to stumble into a cool sound beginning in ignorance and ultimately coming up with coolness. I'm actually quite surprised how cool the feedback system i implemented turned out being. Maybe for the reverb idea, i ll document the whole process from teh brilliant starting idea, to more humbled realistic, hopefully useful version. I want to see if i can tame that feedback explosion just through prompts!!!

[Touch The Universe]

ChatGPT looses context very quick. Claude is much better in keeping context. You could work with a summary and starting a fresh chat when you notice the drop.

I have the 20 dollar version and can usually get 5 prompts a day out of it, likely because of my monster sized code files, though often just drumming up gui eats the same amount. That absolutely does sound appealing. Also, an ide like cursor does to, which can literally update the code, build it, etc and manage files on the computer. That would be really convinient at this point.

[Touch The Universe]

Figured I'd ask this here too....Is surge xt mit? it seems there is a bit of confusion when i try to get gtp to implement it into a synth. It insists it is gpl3 but google ai insist it is mit if you don't touch the source code just link to it, can anyone help?

I want the modern osc, the fm 2 and fm3 only, and maybe the verbs and delays.

Does Surge XT have an explicit linking/embedding exception that allows its GPLv3 oscillator source files to be linked into a non-GPL JUCE plugin if the Surge source files are kept unmodified?

[whyterabbyt]

Figured I'd ask this here too....Is surge xt mit?

Surely you could have looked at the repository? Its GPL3.

google ai insist it is mit if you don't touch the source code just link to it, can anyone help?

google ai is hallucinating, then.

Does Surge XT have an explicit linking/embedding exception that allows its GPLv3 oscillator source files to be linked into a non-GPL JUCE plugin if the Surge source files are kept unmodified?

No. The original Surge code was released by the original developer under GPL3, so nothing derived from that can have any other license.

[Touch The Universe]

Thanks, that is weird, good thing I checked.