Hi guys,
I just wanted say that I’m now a happy father to a one of these pedals (actually 5 but I only completed one (and when I say completed I mean that the guts are completed)).
Wonderful project!
There are some hangups, mostly software, I haven’t been able to figure out but I plan to dig deeper into it.
One thing that bother me though is what to call this project? I call it a bkshepherd-pedal, but maybe it should have a proper name? :^)
Awesome, glad you got one built! A proper name would be great, let me know if you have any ideas!
I would encourage you to get the software portion working the longer way so that you can make changes, however in the short term, if you want to confirm the hardware is working, I just wanted to make sure you saw this set of instructions as well DaisySeedProjects/Software/GuitarPedal at main · bkshepherd/DaisySeedProjects · GitHub for using the web flasher and the precompiled .bin files!
FWIW I like calling it the bkshepherd pedal, I think maybe if a new hardware revision were to come out of that repo, a name would be appropriate, but until then, it’s his hardware design and is easy enough to deliniate it and reference it across other forum posts (and compare it to funbox, hothouse, terrarium). ALLL that being said, I am a square and a fun name would certainly work too 
Edit: Because it always cracks me up seeing @kshep socks and funny fisheyed POV in the main screenshots whenever the projects is linked too, my vote would be something along the lines of mixing socks + Daisy Seed
@xconverge I’ve gotten it up and running with the software built from scratch so it’s basically fine.
Actually I’ve built both this and the Funbox so I’m a little mixed up on what issue I had where.
I did definitely have problems with the function of the foot switches though. It’s a bit hazy, I need to retest, hopefully I will figure out what my problem is then.
Haha, something with socks and seeds sound like a plan 
chatgpt didn’t help me come up with anything I liked other than Sockwave, I think someone else should handle the creative stuff and I will just stick to c++
You all are too funny! I didn’t realize my socks are famous now.
Finished up my other three pedals, I had fun with the UV printing on these. The one on the left might be my favorite pedal I’ve ever made, because I covered every side in drawings from my kids that I scanned in. The other two have a lighthouse sketch I drew, the black one is zoomed in and the yellow is the full sketch. All three builds went smoothly. Now to make some music with them!
I like the yellow one. Reminds me of some of the Walrus designs.
They all look amazing!! 
And it’s so awesome that you have a pedal that features drawings by your kids!
Added two new modules in a branch labeled grandelay-fmsynth, still doing some testing on them but it will build and run. The modules are a granular delay and a FM synth over midi. Before doing a pull request I’ll comment out the synth since most people don’t use the pedal with a keyboard. Enjoy! Let me know if there are any problems with them.
Dang those look sweet! I especially like the one with your kids art on it!
Need to add this! Schemo?
I used the same circuit as the Funbox expression, and soldered to existing 3v3, 5v, and ground points, as well as directly to ADC 6 on the daisy seed. It looks like there’s room around the top right side for a smd version of this circuit, I was thinking about modifying the KiCad to add it and have 3 terminals to wire the TRS jack to.
I tried using the expression without the dual op amp out of curiosity, and just wired the trs jack like the other potentiometers. There is a good reason for using the op amp circuit! It seemed to work OK with the expression plugged in, but when I unplugged it the parameter I assigned to expression was randomly drifting, and not near 0, some point in between. The result was that the screen constantly displayed the value changing slightly. I don’t know the reason behind that, but you do need something besides just the TRS jack for expression.
I got the hardware and software and I love it, its fantastic seeing how great open source projects can be. I was wondering, as somone with beginner C++ experince, where one would start with building their own guitar effects on this platform? nothing crazy (yet) but I wanted to start with the simple oscillator example, but I wasn’t sure if I could just copy and gut an effect module to start on my own, or if there’s other things I need to keep in consideration.
Yep that is exactly it, here (Initial distortion module playing around by xconverge · Pull Request #61 · bkshepherd/DaisySeedProjects · GitHub) is my last pull request adding a single module, it guides you to the necessary files to change. Copy paste a .h/.cpp of an effect module, rename everything (remember m_name in the .cpp file (constructor is what the first function is called) which is shown in the UI), add to make file, add to loaded effects, compile it and flash it to the hardware and make sure it shows up. Once you have done that, then you have your playground to make tweaks in just the effect file!
Because it is an open source project with a permissive license, I wouldn’t have too many hestitations about pasting large portions of code into ChatGPT with questions like “using this as the basis, and the daisySP library, how would I write a chorus effect”, etc. I have found it to be a lot of fun to explore new concepts with this method + reading around/asking questions. The compressor_module.cpp is probably the simplest file I have made, because it just utilizes a single component within the DaisySP library, so it is basically as small/light of an effect as you can get. ProcessMono() is the main place you want to be looking in each effect
Also feel free to ask any questions here or in the project issues if you want! Using the “parameters” and knobs in an effect can take a little bit of getting used to, but are super handy.
I added two new modules in a separate branch, an IR module and a Drum module! I wanted a standalone ir separate from what’s in the amp module to be able to use larger, better sounding IRs while running nam on a separate pedal. The Drum module uses a the DaisySP drum classes and a keyboard to play drum sounds, and it also has an “auto” mode that plays a preprogrammed beat. I’m still working on it but basic functionality is there, and it has tap tempo. You can set a dry through option to play along with the beat on a guitar as well.
Happy Pi Day!
Cheers all for sharing this code.
I have a Daisy Pod, and wanted to try this out. So I did a quick hack to get this code running on the Daisy Pod.
It’s not particularly useful since there’s only 2 pots. But enough to get a feel for some of the effects.
It should be possible to wire two more pots to A1 and A7.
Another option, would be to get midi in working, and use external controls.
Code is here:
Usage:
Plug a guitar into a preamp and then to line in on the Pod. To toggle effects, hold down SW2, and rotate the encoder (careful some effects are louder that others).
This is such a cool project, I’ve been following along for a few years now and I’ve loved witnessing its development. Heck, I think it’s time to try one out for myself! Have any of you folks used this with a synthesizer/line level instrument? I’m just wondering if much noise is introduced, and if I should modify the input circuit to my needs.
Amazing work, thanks for sharing 
Hi Kevin. I have a potentially dumb question for you. I have built 2 of your pedals so far and they work great. Except - I’m wondering - when do the LEDs light up? I realize they’re under software control from the Daisy, but I have not seen them light for any reason and I was worried I put them in backward (I didn’t). But perhaps I’ve done something wrong twice now (I’m onto building my third).
Thanks!
Joe
