auv2

Configure Audio Unit v2 plugin MIDI routing and component types in Pulp.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill auv2-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auv2
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/auv2
Command: npx skills add https://github.com/Generous-Corp/pulp --skill auv2-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complex, silent-failure prone integration of Audio Unit v2 plugins, ensuring correct MIDI routing, component type selection, and host-side compatibility.

Core Features & Use Cases

  • Adapter Configuration: Provides precise guidance on selecting AU component types (aufx, aumf, aumi, aumu) to prevent silent MIDI failures.
  • MIDI Wiring: Offers technical specifications for implementing MIDI input/output, sample-accurate event handling, and factory dispatching.
  • Use Case: Use this skill when debugging a plugin that loads in a DAW but fails to receive MIDI events or when configuring a new MIDI processor to ensure it correctly advertises its capabilities to the host.

Quick Start

Use the auv2 skill to verify the correct component type and factory macro for a new MIDI-receiving audio effect.

Frequently Asked Questions about auv2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Audio Unit v2 plugin load in a DAW but fail to receive MIDI events?

Audio Unit v2 plugins fail to receive MIDI when the wrong AU component type is selected. Configuring the correct factory macro and component type, such as aumi or aumf, ensures the host correctly routes MIDI events to the plugin.

How do I select the right AU component type for a MIDI processor?

Selecting the right AU component type requires matching your plugin's function to aufx, aumi, aumu, or aumf. Using the correct factory macro guarantees the plugin advertises its MIDI capabilities to the host, preventing silent runtime failures.

What is the correct way to wire MIDI input and output in an AU v2 plugin?

Wiring MIDI in an AU v2 plugin involves implementing technical specifications for MIDI input, output, and sample-accurate event handling. Proper factory dispatching and host-side property negotiation ensure the host correctly delivers MIDI data.

How does an AU v2 plugin negotiate host-side caching behaviors?

AU v2 plugins negotiate host-side caching by adhering to AU SDK requirements during initialization. Correctly configuring host-side property negotiation prevents caching behaviors from causing silent runtime failures and missed MIDI events.

Do I need CMake to build an Audio Unit v2 plugin?

CMake is commonly used to manage the build process for C++ audio plugins. Proper CMake configuration helps package the Audio Unit v2 plugin correctly, ensuring it meets AU SDK structural requirements and loads successfully in the host.

When should I use the aumf component type instead of aumu for an AU plugin?

Use the aumu type for audio units that generate sound from MIDI input, while aumf designates a MIDI-controlled audio effect. Selecting between aumf and aumu based on your plugin's exact audio processing role ensures correct host integration.