Concord 🍇 Web Synth

con·cord /ˈkɑnkɔɹd/ n 1 An agreeable combination of tones simultaneously heard; a consonant chord; a consonance; a harmony. 2 A variety of sweet American grape, with large dark blue (almost black) grapes in compact clusters; a Concord grape.

An idea that's been kicking around in our mind for a while now, the beginning of which has been made real thanks to the Make Literally Anything Jam '26!

The Juno is a beloved synthesizer, and we are among those who adore its sound. It has a straightforward architecture, but is still incredibly expressive. Its heavy use from its release in 1982 to this very day is a testament to its timeless sound. As a way to better understand how it works, and because we wanted to expand on its capabilities with a semi-modular approach, we've been wanting to create our own Juno clone. We don't know many tools that can make synths. But we know the Web Platform and have wanted to use the Web Audio API for a project.

This is very much a work in progress. It sadly does not have the classic Juno chorus yet — which is really more a flanger, but who cares about such technicalities! It still needs a noise channel, PWM control, an envelope generator, LFO controls. It still needs a routing matrix for our funny experiments. It could use some more accurate modeling for a nicer sound. It also does not have Web MIDI support yet since that's a Blink-exclusive feature, and boy, do we not like using Chrome and its ilk. But you can use your regular normal computer keyboard to play it while using your mouse to control parameters, so hey!

We've met many wonderful and creative people over the past few years, some we're fortunate enough to call friends. Because of them, we've since gotten back into drawing, working with music and sound, and now programming fun projects. Who knows where we'd be without your generosity and gracious hearts. From the bottom of ours: thank you.

This project did not and will not utilize generative AI in any way: no art, no code, no chatbots. It is a product of personal knowledge, pouring through documentation, white papers, some research from others, lots of hard work, and some late nights. There have been times where we've gotten stuck and banged our head against a wall, and it's easy to forget that when you only see the product and not the hard work that went into it. But the result of that trial and error is a better and deeper understanding of how audio engineering and web APIs work. And that's something you can't get by just having the corporate probability machine fart out an answer for you. There is no shortcut for understanding — you must do to learn, and failure is part of that.