Skip to content

Conversation

@davemollen
Copy link

@davemollen davemollen commented Aug 28, 2025

I want to create an AUv2 plugin of type "aumf" (music effect) when the MACOSX_EMBEDDED_CLAP_LOCATION is set.

In the first commit I made INSTRUMENT_TYPE take precedence over setting the plugin type based on the present CLAP features. This way you could also create all the other possible AUv2 plugin types.

In the second commit I changed the automatic AUv2 plugin type assignment a bit. When the CLAP plugin has both the AudioEffect and the Instrument feature the "aumf" plugin type is assigned. Also, this checks the whole set of features, instead of only the first.

I wouldn't be surprised if this not mergeable yet. Maybe I'm missing some caveats. But I'd be happy to contribute. I could also turn this into an issue if this is way off.

@defiantnerd
Copy link
Collaborator

Hey, thanks for your input. I'll check it out tomorrow.

@baconpaul
Copy link
Collaborator

Can’t you do this instead with the au extension which lets you set your type explicitly?

char au_type[5]; // the au_type. If empty (best choice) use the features[0] to aumu aufx aumi

If your clap implements that extension it should use it in the compile time generation of the plist

@davemollen
Copy link
Author

I tried setting the type explicitly by passing INSTRUMENT_TYPE to the target_add_auv2_wrapper function. But that doesn't work when I also use the MACOSX_EMBEDDED_CLAP_LOCATION. Otherwise it works fine.
Should I pass the audio unit type in some other way to set it explicitly?

@baconpaul
Copy link
Collaborator

Hmm that embedded option must use another path to make the plist indeed. I’ll try and look

@defiantnerd defiantnerd changed the base branch from main to next January 4, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants