You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 13, 2023. It is now read-only.
So I have coded some PD externals of my own, and I was wondering if there is any way to compile them along with a patch with hvcc? I guess all (most?) of the standard PD objects must have been already implemented in heavy. Would it somehow be possible to expand heavy with your own custom externals before compiling your patch which uses those custom externals?
Any thoughts?
The text was updated successfully, but these errors were encountered:
Hey, sorry no one replied sooner. In case your question is still relevant, the short answer is no. hvcc only supports a specific part of the vanilla library. You can see which objects are compatible here.
But you can still make your own abstractions to imitate your externals' behavior. For instance, hvcc doesn't support [threshold~], but you can make your own [threshold~] easily enough using [env~] or [snapshot~] connected to [>].
I think you could inject custom C/C++ code (e.g.: your external) in one of two ways:
figuring out how to add it to the heavy core (go through the source code, see where the C code is generated, hook in there to add it)
in the wrapping code: receive/send messages from heavy to your code to implement the message-rate part of your external, and use additional "dummy" [adc~] / [dac~] from heavy to connect the signal-rate outs/ins of your external.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So I have coded some PD externals of my own, and I was wondering if there is any way to compile them along with a patch with hvcc? I guess all (most?) of the standard PD objects must have been already implemented in heavy. Would it somehow be possible to expand heavy with your own custom externals before compiling your patch which uses those custom externals?
Any thoughts?
The text was updated successfully, but these errors were encountered: