wildergarden

Thanks for the comment! I really love the quality and attention to detail you folks put into your plugins, and I had no idea you made Lossy into a pedal. So cool!

Oh my goodness, hello! Pamplejuce has been a life-saver-- having github actions with pluginval proved to be an absolute necessity when building and linking the hacked encoder libraries. I love reading your juce blogposts as well. Thank you for all that you do!

I would absolutely recommend using JUCE-- it is very well documented, with an active forum full of helpful people.

When starting out, the first plugin I made was a gain/panning plugin, then a simple saturation plugin. These are good ones to start out with, since the output for a sample only depends on the input of that sample, and not the samples before it. After that, I would recommend making a delay plugin: there are a lot of opportunities for creativity with delay, once you have the basic code down.

The plugin project structure can be a bit confusing at first, especially in the interaction between the GUI code and the audio processing code. The tutorials are helpful for that: once you've copied a tutorial, you can try expanding it, adding more knobs etc.

Yes, absolutely! Lossy was one of my main inspirations in coding MAIM, and I would recommend their plugin highly: it sounds beautiful, although it is perhaps a bit less "accurate," since it does not use real MP3 encoders.

Oh that's cool! I didn't know about that program. Now I wonder what compressing and UNCHIRPing a sound hundreds of times in a row would sound like....