15 thoughts on “Build A Custom DIY Effects Pedal With The Daisy Seed & Hothouse Case”

1. Thanks for sharing Floyd’s awesome video! Note that the version he assembles in the video is the earlier mono version. The current version of the Hothouse (released yesterday) is fully-stereo and can do mono-to-mono, mono-to-stereo, or stereo-to-stereo depending on how you program it. Cheers and happy hacking!

2. I’d like to hear about the latest capabilities of the Daisy itself.
   I can run PD patches directly, right?
   Which bunch of the native/vanilla modules, which externals?
   Freeverb?
   How many freeverb instances?
   Or how many sigmund instances?
   Not that I’d place many sigmunds in a patch but just as a metric

   1. PD is unfortunately not that straight forward. All this info can be found on the daisy forums (even without registration).

      Loading Gen~ patching is really simple on the other hand.

      For PD, one of the best platforms I have found is the Bela hardware.

      1. There are some simple examples in the HothouseExamples Github repo as well: https://github.com/clevelandmusicco/HothouseExamples/tree/main/pd

         plugdata (https://plugdata.org/) is recommended for its built-in direct flash feature, and because it already includes the necessary board.json file for the Hothouse. I (or a user) will probably port/post several more examples in the coming weeks and months.

3. Also, why am I having this mysterious feeling as if Hainbach has shapeshifting capabilities?

   : )

4. These kinds of open or semi open devices are super interesting; but they seem to be aimed at users who are willing to commit the time to build, configure, troubleshoot, etc.; but also write code for their desired results.

   I’m not sure how open the Zynthian (v5), Mod Dwarf, Poly Beebo, Empress ZOIA, etc. are; but they seem to offer at least some amount of additional configurability/flexibility. Not sure how they stack up against a more standard multi-fx/modeler like HX Stomp or Fractal FM3– but I assume the latter would sound better right out of the box.

   Blokas Pisound promises high quality audio/MIDI i/o, but seems to be more for learning, experimenting, and isn’t as turn-key.

   1. Ok, I’ll bite : )
      Care to elaborate “sound better”?

      1. less noise?

         1. I just meant the quality of the DSP software, not the fidelity of the audio hardware.

      2. It’s a fair question; I guess “sound better” is shorthand for more realism, musicality, playability. For examples: the amp modelers and reverb in both Fractal & Line 6 have evolved over quite some years of firmware updates. In their sims, dynamic response to different kinds of playing that is similar to how an amp reacts. For reverbs, there is big difference between merely adequate reverbs and those that are well-designed and perhaps more CPU hungry.

         It’s not really fair for me to comment, since I’ve only listened to demos of some of those semi-open devices; but have no direct experience.

         Though I’m intrigued by those devices; especially pisound and zynthian; I’m finding myself downgrading my expectations, as I think the concept limitless possibilities is more appealing than the real-world results.

   2. The Zoia offers a considerable degree of flexibility and configuration. Take a look at the range of patches that have been developed for the Zoia and you can see why it is still a viable option.

      And, in the larger scheme of things, using multiple unit allows you to create both instruments AND effects processors, within the same programming platform (if you can call it a platform!).

      What’s better than one Zoia? Two. What’s better than two? THREE! 🙂

   3. Re: “but they seem to be aimed at users who are willing to commit the time to build, configure, troubleshoot, etc.; but also write code for their desired results”

      I think this is largely the nature of the beast in terms of the software/micro-controller development side of things, but your point is a good one. The Hothouse is aimed at people who have some know-how and interest in the DSP development space, but don’t want to muck with all the required hardware sourcing, UX and industrial process design, BOMs, etc. associated with other DIY or kit options. We’re trying to make things as turnkey as is reasonable by making available ready-to-flash effects @ https://github.com/clevelandmusicco/HothouseExamples/tree/main/pd.

      If you have a micro USB cable and a web browser that can run https://electro-smith.github.io/Programmer/, you can flash any of the (growing list of) examples at https://github.com/clevelandmusicco/HothouseExamples/releases/tag/v24.08.01 with virtually no configuration of a development environment.

      But, back to your point: at least a little development experience and interest (particularly with DSP and micro-controllers) is a core competency requirement to get the most out of this sort of kit. Is it a turnkey beginner’s kit or a way to save money on a classic digital effect clone? Not exactly, but that may depend on the gumption of the individual.

      Cheers for the input and interest!

5. very cool. keep up the good work!

6. I’d love to see something like that that supports Korg multi-engine effects.

   The multi-engine platform is fantastic, and I love being able to add really good custom effects to my Prologue.

   Unfortunately, the NTS-1 platform is sort of a glorified testing platform. If Korg or someone else could put the same brain in a case like this, or in a purpose-built Euro module, it would really be fantastic. This seems like a missed opportunity for Korg.

   1. fwiw, Korg supplies design info for the front panel (only). you can put whatever physical interface you can design for it.