It will be interesting to see where that goes, but I suspect Electrosmith will want to maintain a clear separation of concerns. Sometime soon, I need to fire up the Arduino IDE, get familiar, and have a think about how best to support it; ideally, in the form of a complement to/extension of DaisyDuino. (I have exactly 0.0 hours of experience with that ecosystem, so “good intentions” and all that …)
I ordered a hothouse a few weeks ago and I’m loving it! I’ve written an overdrive effect as my first foray into DSP and I’m really happy with how it has turned out. One thing I’ve discovered is that at the default block size of 48 and default sample rate of 48kHz there is 1kHz noise coming from the ADC. It appears that this is a known issue with the daisy seed (see https://forum.electro-smith.com/t/questions-about-digital-noise-and-grounding/) where there is noise at the frequency sampleRate/blockSize. In that other thread there are several hardware workarounds mentioned, and I’m not sure if the hothouse is using any of those, but I’ve resorted to reducing block size to 4 samples at 96kHz sample rate to move the noise up to 24kHz and out of the audible range. This is probably not an issue for most use cases, but I am boosting the input signal by up to 96 db at which point the noise becomes significant. I wanted to point this issue and my workaround out in case anyone else runs into the same problem.
I don’t have any 1kHz noise in my hothouse. The fact that this frequency is aligned with the frequency of the data blocks (48 kHz / 48 samples = 1 kHz) makes me think that you have a bug in your software and that it’s not a problem with the hardware.
Can you post your code? Or, can you share a github link?
I’m almost certain it’s not a software issue. FWIW, the 1kHz noise is only 10-15 db above the noise floor, and the noise floor on the pedal is pretty low! It is unlikely to be an issue for anything other than an overdrive/distortion/fuzz pedal or maybe a compressor pedal. I didn’t mean this as a criticism of the Hothouse in any way, I think the hothouse is really great and would strongly recommend it. Just wanted to let people know how to work around this issue in case anyone else happens to run into it.
This wouldn’t make much sense to me. You’d need to change the power input and modify the audio levels to comply to eurorack. This and the stomp buttons not being very handy inside of a modular makes it not particularly worthwhile to do, imo.
Of course it would be cool to have a Eurorack specific Hothouse-like product. Say a Patch.Init() with more knobs and switches, basically.
But this is up to @newkular to envision and execute
I agree with @dreamer here. To be useful in a Eurorack form factor, the mechanical, circuit, and UX designs would need an almost total overhaul. That’s not to say I’d never do it, though. The idea of a Eurorack version has been on my backlog for a while now … it just wouldn’t be a “Eurorack enclosure” for the Hothouse.
like have a main input for music, but also a secondary input channel that I can use to duck the main input for example. Like The Pill or Polyend Press.
Cheers for the clarification; that’s what I thought you meant. I’ll add it to the backlog. However, it seems a highly-specialised feature at face value. I’ll have a think about how to make something like that apply to other use cases.
Since the Hothouse is a true stereo pedal as it is, one could use one of the input channels for a sidechain signal. Of course, this means you’re limited to one channel of audio. But that might work in many use cases.
I’ve added it to the backlog. Cheers for that! A popular YouTuber recently started a series on using Plugdata with Hothouse, so interest has spiked … meaning the backlog is growing quickly. Total transparency: this feature is below things like MIDI I/O and an expression jack for a v2
Exactly ^^ At that point, you’d have a completely new set of use case possibilities, but it’s a different beast altogether (and in a different price range).