Install the part you need.
Use synthesis without a 3D engine, draw without audio, or put a scene into your own Three.js renderer. Each package exposes its public contracts and explicit resource adapters. Full editors remain in the ParamRig application.
Core
@paramrig/core
Contracts, validation, bindings and animated values.
Installation and exampleAudio
@paramrig/audio
Patches, synthesis, modulation and block rendering.
Installation and exampleSound Labs
@paramrig/audio-labs
Seeded generation, variation, fusion and catalogs.
Installation and exampleBrowser audio
@paramrig/audio-browser
Independent AudioWorklet players and host-owned transport.
Installation and exampleVector
@paramrig/vector
Drawing and layout documents, bindings, SVG rendering and exports.
Installation and exampleScene
@paramrig/scene
3D documents, scene instances and an optional browser viewer.
Installation and exampleReact controls
@paramrig/controls
Controlled parameter inputs and an extensible registry.
Installation and exampleWeb
@paramrig/web
Connect a running website to the ParamRig workbench.
Installation and exampleSmall installs and explicit ownership.
Separate packages reduce installation dependencies. Sub-entries let bundlers include just the APIs you import. React belongs to the host when you add controls; Three.js belongs to the host when you add a scene.
Supply your fonts, textures, images and wavetables through resource callbacks. Instances release the resources they own. An audio player never closes your AudioContext, and a scene never destroys your renderer.
Know where each API runs.
Core, audio rendering, Labs generation, document serialization and bindings work under Node. Browser adapters provide playback and visual rendering. Browser typography and canvas exports are not advertised as equivalent server rendering.
The guides name their dependencies, supported environments, exports and errors. Each includes a runnable consumer of the published packages.
Browse the examples