Use Pulp's MIT-safe Cmajor support lane via source-owned patches, an external `cmaj` toolchain, and explicit generated-artifact workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this skill when a task involves Pulp's current Cmajor support lane.
Pulp supports Cmajor as an external toolchain, not as a vendored runtime.
Supported now:
.cmajor / .cmajorpatch source examplestools/scripts/cmajor_external.py doctorcmajNot supported by this skill:
Processor adapter for arbitrary Cmajor patchesdocs/guides/cmajor.mdtools/scripts/cmajor_external.pydocs/contracts/pulp-dsl-v1.mdexamples/cmajor-gain/python3 tools/scripts/cmajor_external.py doctor \
--patch examples/cmajor-gain/CmajorGain.cmajorpatch
Use --require-tool when the next step truly depends on a real cmaj.
cmaj externalPreferred resolution order:
--cmaj /path/to/cmajCMAJ_BIN=/path/to/cmajPATHDo not turn the upstream Cmajor runtime/toolchain into a bundled dependency of Pulp unless the repo's license policy changes.
python3 tools/scripts/cmajor_external.py generate \
--patch examples/cmajor-gain/CmajorGain.cmajorpatch \
--target cpp \
--output /tmp/CmajorGain.cpp
Pass through target-specific args with repeated --arg flags.
When editing this lane, keep these in sync:
docs/guides/cmajor.mddocs/reference/capabilities.mddocs/guides/examples.mdplanning/v3-phase14-gap-closure-status.mdFor the current Cmajor lane, verify:
cmaj, not an assumed bundled toolThis skill is for the MIT-safe external lane only.
If a user wants true runtime embedding:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.