Platerra - plate reverb based on Dattorro

[joulupukki]

I published some code for the Hothouse today that implements the Dattorro reverb (plate reverb). I'm sure there are plenty of things still needed to get it working 100% correct, but it's sounding pretty decent. The code is available here: https://github.com/joulupukki/hothouse-effects/tree/main/src/Platerra

[clevelandmusicco]

This is awesome! The demo sounds good to me ... I need to take this for a spin later this week after I process some holiday orders 😁

I assume you saw the Dattorro example I posted in Pd? https://github.com/clevelandmusicco/HothouseExamples/tree/main/pd.

The Platerra is a great C++ alternative, it seems. Once you're comfortable, I can port your work into the HothouseExamples repo and development can continue there. (I guess that's more a question?)

[sletz]

Another way would be to compile the Faust dattorro version, see https://faustlibraries.grame.fr/libs/reverbs/#redattorro_rev and the directly usable one: https://faustlibraries.grame.fr/libs/demos/#dmdattorro_rev_demo, to be compiled using faust2hothouse.

[clevelandmusicco]

👀 I'll be adding faust2hothouse and other new community additions to the README today. Just wow. Many thanks.

[joulupukki]

Didn't know about either one of those things! I'm not familiar yet with PD and have no idea how it works, but I'll look into it.

I also just integrated my Platerra into the Flick pedal and the Flick pedal is becoming very usable. It now has the ability to go into reverb edit mode with a double press of footswitch 1 and also has a factory reset option as well. I still need to add some functionality to all the toggle switches that I have planned and then I'll make a new video of it. See the README for what features it has. https://github.com/joulupukki/hothouse-effects/tree/main/src/Flick

I'll take a look at these other Dattorro options as well and if it makes sense to switch to one of them, I'll do that as well.

I'm not sure yet about where this will ultimately live @clevelandmusicco. I do like the ability to make and publish updates without needing to wait for pull requests to get into an examples repo. But, maybe after I get it to a point where I feel it can live as a full-on pedal that may make more sense. I'm open to ideas there, for sure.

[clevelandmusicco]

Just my opinion: since you're a C++ developer, it probably doesn't make much sense to "switch" to Pd. I only added it to HothouseExamples at the request of folks that aren't code-slingers and/or that prefer the visual programming approach.

[joulupukki]

A lot of it needs to be cleaned up and reorganized. I'd love to think more deeply about cleanly supporting double-pressing footswitches into the main Hothouse code since that opens up a bunch more possibilities (like how I'm using reverb edit mode and supporting both tremolo and delay from one footswitch).

[clevelandmusicco]

I'm not sure yet about where this will ultimately live @clevelandmusicco. I do like the ability to make and publish updates without needing to wait for pull requests to get into an examples repo.

@joulupukki If you had a HothouseExamples fork in your GitHub account and did development there, the updates to your fork are published in real-time as usual. I'd pull changes into HothouseExamples from specific commits in your fork as you deem them "ready". In fact, this is the only way to easily get your code into the official repo. Any other way requires logistical gymnastics.

I'm looking forward to more of your stuff and glad you're enjoying!

[joulupukki]

Ah, that makes more sense. Now that the landscape of the Hothouse and Daisy is a bit more familiar to me, I’ll see if I can rearrange it so that I’m working in a fork of HothouseExamples. Silly thing, but it’d kinda be nice if it was named something besides “Examples”. That always kind of gives me the vibe of something you’d never really use as a finished product. But, I get where it’s coming from. Thanks for the direction and pointers.

[clevelandmusicco]

[...] it’d kinda be nice if it was named something besides “Examples”

Yea, I hear ya and don't disagree. The naming convention is simply borrowed from the DaisyExamples repo, which is a part of the same ecosystem. Electrosmith lists the Hothouse on its Daisy Seed product page, so I decided to make it consistent.

Philosophically, the Hothouse—as a finished product—is more a hardware platform (wrapped around another hardware platform) than anything else. The companion code will always be a rolling-release collection of examples to demonstrate some things that can be done on the hardware; the software will never be for sale or considered a product (by me, anyway). The idea is that smart folks like yourself with a passion for DSP will DIY your own software projects or products on the hardware, and share them in a libre community sense.

I know it's obvious to you, but it bears repeating for folks that may not know: GPL code can be used in commercial products. Our OSes, routers, phones, TVs, every website we ever visit, etc., likely all use GPL software. So, the plan is coming together thanks to contributions like these 🙌🏼

So, perhaps someday I'll refactor the code into separate Hothouse library and HothouseExamples repos, but even then, a separate Hothouse library is only useful on the Hothouse hardware—same as the examples. When the Hothouse unexpectedly sprung to life last fall, this was just the easiest approach for DSP beginners (like myself). Still much to think about ... cheers again!