@MondoJim Is this the last version, the same as the one you shared here with a PD patch?
The PD one I managed to build using the MOD Plugin Builder, but I didn’t really test it yet.
If it’s not the same version and you manage to give me a new .pd file I can try to build also the newer one.
They are both version 1.2. When I come up with a ‘final’ version, how would an interested MOD Dwarf user install it? Is there a way to submit it for consideration into the ecosystem?
As far as near future changes, I’m happy with 1.2 but I may take one more stab at the tape saturation simulation since the current version is basically just a soft knee limiter. After that I think it’s done unless a bug pops up that I missed.
Gotcha
The easiest way would be to build it with the MOD plugin Builder. With that, you can generate a shareable link that any user can use to install. With the plugin builder, you can build the plugin, input some/your data, then get a permanent shareable link.
Would that be possible for you?
I’m curious how you managed to build the plugin with the cloud builder. Because last time I tried I got some errors - even though it said the build was completed successfully - because the Pure Data heavy compiler wasn’t up to date. See this comment:
I don’t think the cloud builder got updated yet.
Yeah…there’s something buggy that is not yet fixed. I thought in Firefox it was, because it actually said that the build was succesfull, but then it was not working to install the plugin and I went to check the log and there were lots of errors. So yeah, still not running. That’s why I deleted my post with the build link 
Since the MOD Builder is using an older version of Heavy, I need to remove any expressions from my file.
I tried breaking out the various [expr]'s into basic equations and they worked in Plugdata. But when I compile for my device, one of the functions that controls the “varispeed” no longer functions. It’s the simplest equation possible, multiplying two floats, but I can’t get it to do the thing yet.
Changing this:
Full disclosure, I’m testing this on a PiStomp.
I’ll ask around on the Plugdata discord. This has got to be an incredibly simple fix.
use [t b f] to make sure your [r Vari] is going right-to-left
Oh, ouch. That’s even simpler than I was thinking. Embarrassing. Thanks for you taking time out from doing actually important things to answer the dumbest question you will hopefully get today!
It’s one of those things related to control messages that you just have to get into your system 
At some point it’ll become second nature!
This works on my hardware and uses no [expr] objects. However, I’m not sure which version of Heavy the MOD Builder is using. Hopefully it can handle hv.compressor and hv.tanh. (And ideally it gets updated to a more recent hvcc!)
https://websites.umich.edu/~jauge/echomatica/downloads/Echomatica_1.3.zip
Best of luck to anyone who would like to convert the .pd to something MOD Dwarf likes!
It is working now
You can try with your own PD file or install directly from this link: MOD Cloud Builder
The fix was not specific for this case and will also allow failed attempts from other users to build properly now.
@dreamer , here’s an explanation of the issue fix, courtesy of Claude:
" What broke, and what fixed it
The root problem. The cloud builder cross-compiles plugins for the Dwarf’s aarch64 architecture, but DPF’s build flow ends with a step that needs to run the freshly-built plugin — it executes lv2_ttl_generator <plugin.so>, which dlopen()s the plugin and reads its parameter list to write the LV2 turtle metadata. On a build host that’s x86_64, the kernel rejects the aarch64 binary outright. Every PD/hvcc plugin on builder.mod.audio had been silently failing at this step since the cross-compile setup landed — DaveM and jon’s earlier “build says success, plugin doesn’t load” reports were the same bug, masked by a separate log-status bug that prints “Build completed successfully” regardless of make’s exit code.
The fix. Install qemu-user-static and binfmt-support on the Hetzner host. Together they register a kernel-level handler so that any time an aarch64 ELF is exec’d on the x86_64 host (including inside a Docker container, thanks to the F “fix-binary” flag), the kernel transparently routes it through qemu’s user-mode emulator. After that, DPF’s standard build flow works as upstream designed it: the cross-compiled lv2_ttl_generator runs under qemu, dlopen()s the cross-compiled plugin (also under qemu), introspects its parameters, and writes the TTL files. Nothing in mod-cloud-builder itself needed to change — the fix lives on the host.
A detour along the way: I first patched DPF’s Makefile to force the generator to compile as a host binary. That fixed the wrong-arch generator but exposed the underlying dlopen() layer — the generator was then x86_64 but still trying to load an aarch64 .so, which dlopen() can’t do. That patch has been reverted; the qemu approach makes it unnecessary."
Sorry I don’t understand, there is nothing broken so there is no fix needed. What is this a response to in the first place? (nobody reported any issues)
This vibecoded text is not helping.
I don’t believe there was anything “silently broken”, builds have worked fine for all this time afaik.
the issue is that the plugin was not building, despite the “success” message. The wrong message was a bug in the cloud builder, which was outputting success for unsuccessful builds, and the actual issue is that DPQ was trying to retrieve the metadata of the plugin as if it was a native (x86-64) build. It is now properly building now.
Sorry for the vibe coding. I am happy that despite the vibe, the solution is now there
where are you reading this?
I guess here @dreamer:
That was a response for me, happily sharing a build simply after getting a “Build successfully” message and without testing it before. There was something broken with the MOD Plugin Builder
I still didn’t test it myself, but what I take from what @gianfranco wrote is that it is now fixed and therefore no one will get a “Build successfully” message when the build in fact didn’t work.
This is not solved by anything Gian just vibed together ..
Please don’t turn this platform into slop @gianfranco …
MOD Builder with a more recent version of Heavy would be appreciated, if only for being able to use expressions. They make the ‘mathing’ more elegant and the numbers easier to keep track of.
Thank you for that link. But, ah [uncomfortable silence and shuffling] I may have to put upon on someone with the, uh, proper hardware access to test. [awkwardly wanders off]
ok…I think a misunderstanding/ little testing is happening here.
The MOD Cloud Builder seems to be working. I just removed the Echomatica and then reinstalled it from there (little comment here: I still don’t have the UI on it).
Yet, that seems to work only on Firefox. I tried Chrome first, and it didn’t work. @gianfranco, likely everyone just tested it on Firefox or another and not with Chrome (?). For the sake of clear info, I didn’t test it in any other browser.
Would it be possible to extract the MODGUI files from one of these and pair it with the MOD Dwarf compiled version? https://websites.umich.edu/~jauge/echomatica/downloads.html
