First pedals should be over drives and other tone shaping effects and compression.
Second pedal/pedals should be an amp sim and a cab sim, mic sim.
if real amp, time based effects go in the loop…
Third pedal time based effects. reverb delays modulation.
stereo panner? sounded nice for studio tool. in home/in ear listening.
things are seldom stereo live in medium to large venues.
Two completely different channels would be a very stimulating use. is that a possible capability? to switch between left and right channels and have two completely different processing situations.?
maybe the midi switching make that a moot point.
the other effect i need would be octave down with something approximating the EH BASS9 or other guitar to other instrument synthesis. for looping. which should be the last pedal in chain?
the other need i have on stage is a midi tone generator. something i can plug a drum or keyboard into.
also the possibility of breaking out electric drums to various channels would be useful.
The order of the effects is up to you. Nothing about the platform prevents that. Every musician has their own needs and order they like to use.
All different effect types you mentioned are definitely possible to create and run on this pedal hardware. But my personal goal, is not to be the one that builds it all.
My goal with the pedal hardware is to provide a blank slate piece of hardware that has a similar set of capabilities (powerful dsp, stereo audio, relay bypass, midi, knobs, foot switches, leds, display, 9v power, etc) to other popular commercially available digital effects pedals like the ones from Chase Bliss, Meris, and Empress. This hardware can then run any custom software to produce whatever kinds of effects you’d like (unlike commercial pedals that locked to primarily 1 function).
My goal with the software framework is to help make it as easy as possible for individuals to get started experimenting their own effects without having to get bogged down into all the little supporting elements that are common across all digital effects pedals (input handling, parameter storage and mapping to ui elements, visual indicators such as leds, menus, and display, etc). With the way things are now, it’s pretty easy to write your own effect module, and have it make sound and do all those other supporting things with almost no additional code.
If folks want to contribute to the available effects and improve on the overall framework (software and hardware) along the way, I absolutely welcome it and always try to be supportive and help where I can. Definitely a big thanks to all the folks that have already contributed, and I welcome any contributions you’d like to make as you get up to speed on the platform as well!
@tele_player I agree with you 100%. I wish it was easy to keep the chain in the digital domain, ideally in an industry standard way like with S/PDIF connectors. I did a bunch of research into this, the only two options I really founder were doing S/PDIF or SPI.
Upside of S/PDIF was that it would work with a lot of other non pedal devices too, downside was that it would require additional codec hardware and that it didn’t look that easy over all to get working. The parts look something like this https://www.hifiberry.com/digis/
Upside of SPI is that it’s already onboard the seed and seems way more easily feasible, the downside is run length distances and it wouldn’t easily interface back to other external hardware etc.
Actually, I was thinking of a PCB with multiple Daisy, connecting with I2S using SAI… yes, it gets trickier if you try to use S/PDIF. But it would be so cool.
Wanted to share an effect module I wrote for the 125b OLED pedal, it’s a reverb/delay, and I threw in a few fancy tricks as well. This is my first time writing a stereo effect, and my first time trying out modulation features, so feedback is appreciated. Here is the link to the compiled binary, so you can just flash the daisy seed to get it:
And if you follow the readme link you can find documentation on all the controls, and the code. Planning on doing a proper demo video at some point, as well as developing more modules for this platform. If you want to modify and build this module yourself make sure to check out the notes at the bottom of the readme, there’s a few minor changes I made to the framework code to get it running. Thanks @kshep for the sweet pedal!!
I shared this on the Discord awhile ago and, in case it will encourage more people to build these cool boxes, thought I should post it here as well! Below’s a short video demo of some firmware I’ve been working on for Keith’s pedals. The programs are built on top of an old version of the repository (before everything was organized into EffectsModule classes) and eventually I’ll get around to porting them to the current framework…
From right to left: strobe tuner / distortion, spectral processor / denoiser, granular synthesizer. The sound source is electric bass.
Hey everyone and Kshep! Super excited about this project! Went through the directions uploaded the BOM and the CLP file. These were missing PDS1-S5-S5-M ( to be expected) . I have them in my cart in the global parts section but I didnt purchase them yet. Will they show up as not be missing? and do I need to purchase the C133069 if they already populated the BOM automatically?
A bit confused on this step everything else is seems straight forward. Much appreciated! Hopefully this makes sense.
Before you order the PCB / Assembly, you need to first purchase the PDS1 through global parts and wait for them to arrive at JLCPCB. Then if you were to come back to this page they will show up properly. If you don’t do this, they will simply assemble the pedal without the PDS1.
The C133069 is stocked by JLCPCB these days, so you do not need to purchase it before hand anymore.
Thank you so much Keith that makes sense. Also how many should I order? Oddly enough the BOM says 7. I think all parts should be multiples of 5 on the BOM because 5 is the minimum order?
Yeah, there is some amount of expected loss of some parts during manufacture / assembly. For the PDS1 they expect to lose 2. So if you want 5 made, you have to have 7 total. It’s kinda annoying since those are expensive parts. Not sure why they lose 2 each time!?
I know! oh well small price to pay! Was wondering if its possible to use PD2DSY. I can only program in pure data! I think the hardware might only be C compatible?
I’ve done some experimentation using Plug Data. It works for the knobs, encoder, switches, and audio in/out, but Midi and the Display won’t work. I need to add my json hardware config and example PD patch to GitHub sometime.
With PD, it’s a little bit out of my control to enable Midi / Screen. At least with PlugData you have to define the hardware using the JSON file and behind the scenes it converts the JSON file to C++ code using the json2daisy utility. The way the configuration is defined for midi and displays is pretty rigid and won’t let you customize which pins on the seed it uses. json2daisy would need to be modified to be more flexible. You can get around it if you are willing to modify that C++ code that is generated from PlugData though.
