aax
無料Optional AAX support for Pulp, including developer-supplied Avid SDK setup, CMake enablement, DigiShell/AAX Validator workflows, and local AAX builds on macOS or Windows.
日本語の概要は準備中です。原文の説明を表示しています。
Create Faust DSP plugins in Pulp using Pulp-owned reference DSPs, optional external code generation, and the FaustProcessor template wrapper.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when a task involves writing, generating, or testing FAUST-based processors in Pulp.
Pulp supports a narrow Faust lane built around FaustProcessor<T>, Pulp-owned
reference DSP implementations, and optional external code generation. The
Faust compiler is supplied and licensed by the developer; Pulp does not vendor,
download, redistribute, or require it for normal builds.
Supported now:
.dsp authoring examples and external code generation to developer-selected artifactsFaustProcessor<T> template that bridges any compatible dsp subclass into Pulp's Processor model.dsp examples is claimedbuildUserInterface() into StateStoregetNumInputs() / getNumOutputs()prepare() for the exact prepared channel
topology and blocks up to the declared maximum sizename, author, version) into PluginDescriptorPulpFaust.cmake (pulp_faust_generate, pulp_add_faust_test)Not supported by this skill:
declare options "[midi:on][nvoices:N]"@gfx / FAUST GUI — FaustProcessor reports has_editor() = false| File | Purpose |
|---|---|
core/dsl/include/pulp/dsl/faust_base.hpp | Pulp-owned Faust compatibility interfaces (dsp, UI, Meta) |
core/dsl/include/pulp/dsl/faust_processor.hpp | FaustProcessor<T> template and PulpFaustUI |
core/dsl/include/pulp/dsl/dsl_processor.hpp | DslProcessor base class shared across DSL lanes |
tools/cmake/PulpFaust.cmake | CMake module: pulp_faust_generate(), pulp_add_faust_test() |
examples/faust-gain/ | Stereo gain — simplest FAUST example |
examples/faust-filter/ | Parametric filter example |
examples/faust-tremolo/ | Tremolo with rate/depth |
FaustProcessor<T> accepts a default-constructible class derived from ::dsp.
Pulp provides the narrow compatibility interfaces in faust_base.hpp, which
are used by its reference DSPs and can also adapt a compatible artifact produced
by an externally supplied Faust compiler.
buildUserInterface() to discover parameters and metadata() for plugin infodefine_parameters() registers each FAUST zone as a StateStore parameter with correct range/unit/groupprepare() validates the declared input/output channel topology, stores
the maximum block size, pre-sizes the raw channel-pointer arrays, and calls
dsp::init(sample_rate)process() accepts only that prepared topology and a block no larger
than the declared maximum. It reuses the pre-sized pointer arrays, syncs
StateStore values into FAUST zone pointers, and calls dsp::compute()
without constructing or resizing vectors. An unprepared call, a channel
mismatch, an undersized buffer, or an oversized block fails closed by
clearing the output without calling the FAUST DSP.// examples/faust-myplugin/myplugin.dsp
declare name "MyPlugin";
declare author "YourName";
declare version "1.0.0";
import("stdfaust.lib");
gain = hslider("Gain [unit:dB]", 0, -60, 24, 0.1) : ba.db2linear;
process = _, _ : *(gain), *(gain);
This requires an externally supplied faust executable. Record or pin the
compiler identity and verify its output before claiming that an artifact
corresponds to a source file.
faust -lang cpp -cn MyPluginDsp -o build/myplugin_faust.hpp \
examples/faust-myplugin/myplugin.dsp
Or let CMake handle it (regenerates when .dsp changes):
include(PulpFaust)
pulp_faust_generate(
${CMAKE_CURRENT_BINARY_DIR}/myplugin_faust.hpp
${CMAKE_CURRENT_SOURCE_DIR}/myplugin.dsp
MyPluginDsp
)
The helper is inactive when faust is unavailable. Pulp's checked-in reference
DSPs remain buildable independently of the optional compiler.
// examples/faust-myplugin/faust_myplugin.hpp
#pragma once
#include "myplugin_faust.hpp" // developer-owned, verified external artifact
#include <pulp/dsl/faust_processor.hpp>
namespace pulp::examples {
using MyPluginProcessor = dsl::FaustProcessor<MyPluginDsp>;
inline std::unique_ptr<format::Processor> create_my_plugin() {
return std::make_unique<MyPluginProcessor>();
}
} // namespace pulp::examples
if(PULP_BUILD_TESTS)
add_executable(pulp-faust-myplugin-test test_faust_myplugin.cpp)
target_link_libraries(pulp-faust-myplugin-test PRIVATE pulp::dsl pulp::format Catch2::Catch2WithMain)
target_include_directories(pulp-faust-myplugin-test PRIVATE ${CMAKE_CURRENT_SOURCE_DIR})
catch_discover_tests(pulp-faust-myplugin-test)
endif()
Follow the pattern in examples/faust-gain/test_faust_gain.cpp:
descriptor() metadata matches the values exposed by the selected
dsp classdsl_name() == "faust", dsl_params(), bus_layout())# Build the Pulp reference DSP examples (no faust needed)
tools/ci/governed-build.sh cmake --build build
# Run all FAUST tests
ctest --test-dir build -R "faust" --output-on-failure
# Run one example
ctest --test-dir build -R "FaustGain" --output-on-failure
# Generate every registered optional artifact (target exists when faust is found)
cmake --build build --target faust-regenerate
When modifying the FAUST lane, verify:
faust
installeddsp class's buildUserInterface() metadatagetNumInputs() / getNumOutputs()prepare() declares the largest block a test or host will submit; larger
runtime blocks are rejected and cleared rather than processedprocess()DslProcessor reflection (dsl_name, dsl_params, bus_layout) is accurateexamples/CMakeLists.txtThis skill covers the Pulp reference DSP and optional external Faust codegen lane only.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Optional AAX support for Pulp, including developer-supplied Avid SDK setup, CMake enablement, DigiShell/AAX Validator workflows, and local AAX builds on macOS or Windows.
日本語の概要は準備中です。原文の説明を表示しています。
Configure, implement, and test Pulp's optional desktop Ableton Link tempo-sync adapter while preserving the developer-supplied SDK, licensing, realtime, latency-compensation, and no-install boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain Pulp's installed design-time agent capability manifest and public-surface ledger. Use when adding, removing, renaming, or materially changing public audio, MIDI, signal, timebase, or sequence APIs; registering a new algorithm for generators; changing capability support or deprecation state; or repairing agent-capabilities freshness, schema, fingerprint, tombstone, or installed-SDK tests.
日本語の概要は準備中です。原文の説明を表示しています。
Android platform development for Pulp — NDK cross-compilation, Oboe audio, Dawn/Skia GPU rendering, JNI bridge, touch interaction, emulator workflows, and end-to-end smoke validation. Covers build, deploy, debug, and the gotchas discovered during bringup.
日本語の概要は準備中です。原文の説明を表示しています。
Optional ARA support for Pulp, including developer-supplied ARA SDK setup, CMake enablement, adapter companion APIs, validation, and ARA-aware plugin implementation guidance.
日本語の概要は準備中です。原文の説明を表示しています。
The measurement surface for ALL Pulp DSP and audio-pipeline work — read it BEFORE writing or gating DSP, not only when something already sounds wrong. Covers the C++ harness (signal generators, metrics, assertions, RenderScenario, contracts), the offline Audio Doctor (magnitude/frequency response, THD/THD+N, phase/group delay), and their Python sibling the Audio Quality Lab (tools/audio/quality-lab — null residual + alignment, LTAS log-spectral distance, spectral flux/centroid, HNR, Theil-Sen drift slope, Kaiser-sinc resampling, license-guarded corpus, regression-net ratchet). TRIGGER on AUTHORING work — "build/design an oscillator/filter/synth/effect", "add a DSP module", "what should the acceptance gate be", "how do I measure aliasing / anti-aliasing / alias floor", "null against a reference", "is this DSP correct", "choose a tolerance", "golden/regression corpus for audio", "measure drift or jitter", "A/B two renders" — AND on DEBUGGING work — "is there sound / no audio / I hear nothing", "does this filter/compressor/synth/delay produce the right signal", "prove the DSP / prove the contract", "measure the frequency response", "what's the THD / is it distorting", "what's the group delay / phase response / measured latency", "magnitude response curve", "render a test tone and assert", "audio regression", "64-frame works but 128 is silent", "sample-rate change pitch-shifted it", "describe what's in this buffer", "audio doctor", "compare before/after a DSP refactor". Reach for this BEFORE hand-rolling any FFT, null test, alias measurement, pitch tracker, or golden-render script — most of it already exists in one of the two lanes. Test/tool layer over HeadlessHost — deterministic, no audio device, no speakers. Off the realtime thread entirely.
日本語の概要は準備中です。原文の説明を表示しています。