skills.rest
danielraffel
danielraffelCOMMUNITY
Explore all skills by this author →
GitHub

aax

Build and validate AAX plugin binaries for Pulp on macOS and Windows.

13|1|Updated Apr 6, 2026
Search Tags:#validation#sdk#plugin#cmake#aax#avid#digshell
One-click install
npx skills add https://github.com/danielraffel/pulp --skill aax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aax
Source: https://github.com/danielraffel/pulp/tree/main/.agents/skills/aax
Command: npx skills add https://github.com/danielraffel/pulp --skill aax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear, repeatable guidance for enabling optional AAX support in Pulp so developers can build, validate, and troubleshoot AAX plugin targets without committing proprietary Avid assets into the repository.

Core Features & Use Cases

  • SDK discovery and setup: Guidance for locating and pointing Pulp to a developer-supplied Avid AAX SDK and validator via environment variables and recommended directories.
  • CMake integration: Instructions to enable AAX builds using PULP_ENABLE_AAX and PULP_AAX_SDK_DIR and to build AAX-specific targets on macOS and Windows.
  • Validation workflows: Advice on using DigiShell/AAX Validator and pulp validate / pulp validate --all to test built bundles and avoid validator collisions.
  • Use Case: A plugin developer who needs to locally validate an AAX target before release can follow the SDK discovery, CMake enablement, and validation steps to confirm binary presence and pass validator checks.

Quick Start

Build AAX targets by enabling PULP_ENABLE_AAX and setting PULP_AAX_SDK_DIR to your AAX SDK path before running CMake and building the target.

Frequently Asked Questions about aax

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

FAQPage Schema
How do I build AAX plugins locally using CMake?▼

To build AAX plugins locally, enable the PULP_ENABLE_AAX flag and set PULP_AAX_SDK_DIR to your Avid AAX SDK path before running CMake and building the target on macOS or Windows.

Why do I need a developer-supplied Avid AAX SDK for local validation?▼

A developer-supplied Avid AAX SDK is required for local validation to avoid committing proprietary Avid assets into the repository while enabling Pulp to build and validate AAX plugin targets.

Can I validate AAX targets on Linux?▼

No, AAX validation is excluded on Linux. Local validation and building workflows for AAX plugins are supported exclusively on macOS and Windows developer environments.

What's the best way to run DigiShell and AAX Validator without collisions?▼

To avoid validator collisions, use pulp validate or pulp validate --all to test built bundles, ensuring DigiShell and the AAX Validator are installed out-of-tree and properly configured.

Does building AAX targets require committing proprietary assets to the repository?▼

No, building AAX targets does not require committing proprietary assets. You point Pulp to a developer-supplied Avid AAX SDK via environment variables and recommended directories out-of-tree.

How do I set up CMake flags for AAX SDK discovery?▼

Set up AAX SDK discovery by configuring the PULP_ENABLE_AAX and PULP_AAX_SDK_DIR CMake flags to locate and point Pulp to your developer-supplied Avid AAX SDK path before building.

Related Skills

Explore More Software Engineering Skills→
yebotyebot
9

cross-platform-builds

Automate cross-platform JUCE plugin builds with CMake and CI/CD.

Community
Advanced
danielraffeldanielraffel
1

trace-analysis

Analyze Pulp trace data to identify slow operations and suggest fixes.

Community
Advanced
Generous-CorpGenerous-Corp
13

aax

Integrate and validate AAX audio plugins within the Pulp framework.

Official
Advanced
afoveaafovea

engine-tools-programmer

Architect engine subsystems, editor tools, and build pipelines for platform stability.

Community
Advanced