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
Sorry if this issue is out of place, but I had no idea where else to ask this question. I've been working on rust-vst2 (vst bindings for rust) and ddcore (a rust vst gui lib) for some time now and would like to assess what kind of work is involved in doing a similar thing for audiounit. With vst, simply exporting the right extern functions and compiling as a cdylib, packaging into a bundle and placing it in your plugins directory is enough to start a working vst plugin. I assume that au is similar, but am unsure where to start.
I have noticed some audiounits and vsts out there actually share a binary, (eg same binary, just copied into different bundles, .component and .vst) and have extern entry points for both vst and audiounit in the one binary. This also gives me some hope it might be possible to unify the vst and au work.
Does anyone have any clarity on this?
The text was updated successfully, but these errors were encountered:
My work in the audio_unit module so far has mainly been focused on exposing an audio output node for CPAL. That said, from what I remember I think a lot of the AudioUnit API should be exposed.
I haven't looked into this a great deal myself but would be happy to review/test any additions or changes that are necessary to support compiling audio unit components.
@mitchmindtree do you have any pointers on where to start? I'd like to make a simple AU that loads in logic (either an instrument or effect, even if it does nothing other than load).
Sorry if this issue is out of place, but I had no idea where else to ask this question. I've been working on
rust-vst2
(vst bindings for rust) andddcore
(a rust vst gui lib) for some time now and would like to assess what kind of work is involved in doing a similar thing for audiounit. With vst, simply exporting the right extern functions and compiling as a cdylib, packaging into a bundle and placing it in your plugins directory is enough to start a working vst plugin. I assume that au is similar, but am unsure where to start.I have noticed some audiounits and vsts out there actually share a binary, (eg same binary, just copied into different bundles, .component and .vst) and have extern entry points for both vst and audiounit in the one binary. This also gives me some hope it might be possible to unify the vst and au work.
Does anyone have any clarity on this?
The text was updated successfully, but these errors were encountered: