The heavy compiler will behave the same way, whatever hardware you use. Using a Pi though, you can use Pd as is, without heavy. That being said, you can use any objects you like, whether native or externals.

PureVST-0.8 is out. This is Miller's message on the mailing list:

PureVST version 0.8 is out on the usual site:

msp.ucsd.edu/tools/purevst/

This might fix some of the bugs in previous versions. It's available as source, or compiled for "M" series processors in MACOS and for fedora linux (Intel processors), or you can compile your own binaries from the source tarball.

"pdnam" returns no results in deken (I'm not hidding foreign architectures, so it's not only the Linux binaries that don't show up).

gain is just a multiplication of a signal with some constant value in digital audio.

First of all, what you're sending to the oscilloscope is a sinewave oscillator, not your granular sampler. Second, we cannot know what is inside the oscilloscope subpatch (you can tell it's a subpatch because its name starts with "pd"). You can right-click on it and select "open" to see what's inside and why it doesn't show anything.
Wild guess, the "samples 1" is probably the number of samples to display. Only one sample is a single value, while you want a bunch of values to display. Try raising the number to something like 512. Otherwise, post a screenshot of the inside of this subpatch.

I just downloaded the Linux amd64 version and it loaded and played fine. Thanks for sharing this!
As for packaging, I think it's best if you create a different package for each architecture. I think that if you just upload each different architecture package with the same library name and version, deken should pack them under the same directory, so when you search for pdnam~ in deken, you'll get one directory with a drop-down menu including all different versions and architectures.

[canvasname] from iemguts. Aparenlty, if you give it an argument 1, it will spit the name of the parent patch out its right outlet.

Check vanillaUrn from here https://github.com/alexdrymonitis/miscellaneous_abstractions.

@willblackhurst how are recent vanilla versions a mess? What issues do they introduce?

I think Pof, which embeds openFrameworks (much like Ofelia did), runs on a different thread (I think). But I have tried closing its window and that crashes Pd. But I could be wrong, as I could be doing this the wrong way.
Switching back to another external that embeds OF, since you have switched from Ofelia to Gem, can be discouraging. I just thought of mentioning that Pof runs on a different thread (I think).