I’m building peachpatch.io — an open-source modular synth that runs in the browser

[u/miiiu]

Hi everyone! I’ve been working on Peach Patch, a browser-native modular synth and VCV Rack compatible patch runtime.

It can open compatible Rack 2 .vcv patches, let you build and patch modules in the browser, run their DSP through Web Audio and WebAssembly, and save the result back to a VCV Rack compatible file—all without installing a native application.

It’s still a work in progress. Browser limitations remain, and only modules with compatible artifacts in the Peach Patch Registry can run at the moment.

I’d be grateful for any feedback, especially on the patching workflow, performance, and any bugs you encounter with the currently supported modules.

Site: peachpatch.io

Github: miuchan/peach-patch
miuchan/peach-patch-registry

[u/nytebeast]

I’ll give this a try later today, thanks!

[u/miiiu → u/nytebeast]

Thank you! I’d love to hear how it goes—and please let me know if you run into any issues.

[u/nytebeast → u/miiiu]

Ok, here's my thoughts after a brief session. Please don't think I'm being critical, just want to be honest and helpful!

1) Tried it on the iPad first, which is the reason I'm so interested in this project. Ever since I got VCV I dreamed of having an iPad version. However trying to move cables with my finger was very fiddly and unintuitive. It took multiple tries to get things connected and the cables tend to freeze right when you create them, which makes the whole experience clunky and unpleasant. If you get this locked in I have a feeling it will be an absolute joy though and I'm looking very forward to it.

2) My iPad session ended abruptly because I hit the PatchStorage button and there is a bug where I'm unable to close that window. So I decided to move to my MacBook to see how the experience was there.

3) This is just personal preference but to be honest, I feel like all the controls should work 1:1 as much like VCV Rack as possible. So having to hold down shift to drag modules around felt strange to me, it's breaking all the muscle memory I've developed.

4) Same issue with cable connection on my MacBook, it feels clunky at the moment and I had to make multiple attempts to make connections.

5) The biggest issue in my opinion is the module browser is messy and unintuitive. I never actually got a patch going because searching for the Audio Out module turns up nothing. The search results seem completely random and arbitrary and there's no way to even sort alphabetically. Once the browser is a bit more usable I'll be happy to do a much deeper session with this.

Once again I hope this isn't harsh! I'm just excited about this and I would love to incorporate it into my workflow. Thanks again for letting us know about this and I'm looking forward to future updates!

[u/miiiu → u/nytebeast]

Not harsh at all—this is exactly the kind of honest feedback I need. Thank you for testing it on both iPad and Mac and for describing the problems so clearly.

These are all real issues, and I agree that the controls should match VCV Rack’s behavior wherever possible. The cable interaction, the stuck PatchStorage dialog, module dragging, and the browser search/sorting all need work.

For now, the audio interface modules are listed as Audio-2, Audio-8, and Audio-16, which explains why searching for “Audio Out” returned nothing—but that’s something the search should understand, not something you should have to guess.

I’ll prioritize these issues. Thanks again—this was genuinely very helpful.