Vibe coding Daisy Seed

B

beniboy87

New member
Let me start with saying that I know this following topic might be touching some nerves, but I feel the whole AI development thing is becoming more and more useful and that’s where my project started.

Lately I was thinking about getting a Daisy Seed and start messing with projects.
I am a 40yo backend developer from Hungary and we started using a lot of AI in development which I started to like it in the last 3-4 months, when I have complete freedom I am 3-4 times faster than normal - even with brutal code reviews. A lot of people say it is dangerous to trust it, but lately I feel that I want to hate it, but our code reviews have only minor things and I started using more and I am starting to see the value.

One day on my way home I thought that hey I should be able to generate plugdata projects with AI, it should be fun to try it out. I generated a bunch of crap that did not work and I did not like. It was a total failure.

Since I just had a baby, I have zero extra time to learn DSP even with the libdaisy library, but I thought that Claude Code might be good here even after the plugdata failure. I did not know if anything comes out will work, but I wanted to try at least so here we go..

I really like the Strymon pedals with multiple delay options and modulation (timeline and mobius) so I thought I will try to get some of the features of those on the Daisy.

I generated two projects with Claude to mimic these two pedals and I had a lot of success. I asked it to use encoders instead of regular pots, so the Terrarium project will not be able to run this project but my plan is to design a Terrarium inspired PCB design with encoders and display and have more capability.

I am still waiting for my Daisy Seed to arrive so I had no option to try the code on actual hardware, so I asked Claude to generate a VST plugin with Juce so that I can test the code and set parameters and make changes if needed. The plan worked, the VST plugin works and is using the same code that will run on the Daisy.
Most of the delays are actually good sounding so I have high hopes.

After this delay code worked fine, I copied the project and gave claude the strymon mobius manual in html format and told him to delete all delays and make effects the same way what is described in the manual. I created a big plan with Opus and Sonnet coded the whole thing. That plugin works too, I will post it soon after some code review.

Git: https://github.com/balazsbencs/daisy-delay-pedal

I have CI build set up, so you can download the Daisy firmware file as well as the macos compatible VST3 file.

Since I am so new to this, I thought I’ll post it here and encourage people to contribute, I feel this might be a cool project, even if it is fully vibe coded.

I am planning to breadboard the shit out of it when my Daisy arrives, and perfect things to make it actually usable.
 
Interesting! I've been avoiding LLM coding for a while now and, to be honest, just haven't had that many reasons to do a deep dive. The one area that seemed like an interesting test case is DSP and audio processing. I've done a tiny bit with the Daisy and have also been interested in the norns shield. Your project seems like a good one to use to get oriented, so thanks for sharing!

Is the entire plan contained in the CLAUDE.md file? I see .claude/settings.local.json as well; I gather this is just for setting permissions for the kinds of things Claude should have access to, right?
 
Band of Dans said:
Interesting! I've been avoiding LLM coding for a while now and, to be honest, just haven't had that many reasons to do a deep dive. The one area that seemed like an interesting test case is DSP and audio processing. I've done a tiny bit with the Daisy and have also been interested in the norns shield. Your project seems like a good one to use to get oriented, so thanks for sharing!

Is the entire plan contained in the CLAUDE.md file? I see .claude/settings.local.json as well; I gather this is just for setting permissions for the kinds of things Claude should have access to, right?
Click to expand...
The new models and tools are exciting, not always great, they do mess up stuff, bit with clever planning and lots of reviews, can be a huge advantage.

The entire plan is not in the claude file. The delay project just started without a planning phase, I just wanted to see if this idea is going to work, so I figured out features step by step.
And yes, the settings file is just permissions to let it do some stuff without always asking me before doing them. i kind of let it do everything free since it was an AI only project. Very little code was made by me.
 
I've done that with my last project - it worked well, but be prepared to input lots and lots of hours into it -
FuzzyLotus

Thread 'Phantasmagoria v2 - Native C++ Spectral Delay Engine'

[RELEASE] Phantasmagoria v2: Native C++ Spectral Delay Engine

Project Overview
Phantasmagoria is a lush, atmospheric spectral delay engine designed for shoegaze, doom, and ambient soundscapes. It is a 6-knob, 4-toggle "no menus" pedal built for the Electrosmith Daisy Seed on the PedalPCB Terrarium platform. The engine combines reverse delay, pitch shifting, and an infinite freeze engine with a massive echo-chamber reverb.

This release marks a major milestone in the development of the project. While the original version was built using PlugData/Pure Data, the move to native C++...
  • Like
  • This ROCKS!
It was a fun learning experience, and I am currently working on a new project-
What I have learned: You need to be super specific when creating your prompts, make sure you keep lots of backups of flagship versions, annotate everything and also test one thing at a time.

Best advice I can give you is to always test the stuff on the hardware after a pass, since one thing can easily break the other, then you are working on a broken architecture without even knowing it. This will save you a massive headache down the road.

Also, I noticed that Claude is very good for coding, but not very good with "expression" it will output purely coded stuff, is super good to produce replications of already working items, but will fail miserably when you ask it to "make this knob sound more "cloud like" It will output code that technically works, but doesn't really grasp what an amazing DSP is vs a normal DSP, so a lot of musical theory and DSP knowledge is required if you truly want to make an amazing project.
 
Interesting timing! I just built my first synth/effect kit using a Daisy Seed (the Synthux Academy Simple Touch 2) which has a bunch of open source firmware options that I'm curious to play with and see if I can adapt to specific use cases, etc.

I'll follow along at the very least
 
You must log in or register to reply here.
Back
Top