Skip to content

AUv2 support #2

Description

@wrl

few pre-requisites for this:

  • Params should have a hash (or otherwise opaque) u32 ID instead of just an index. this allows for stable automation even when parameters are rearranged.

  • we will need some mechanism for wrapping a compiled plugin into a bundle (.component for AUv2), which may rely on cargo-make or similar tool.

  • referencing above, metadata defined in the source code will need to make its way to bundle metadata in the Info.plist file. this will be things like AU type, subtype, manufacturer, etc. do we parse the source, or how does this work?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions