AlexPearce3D Studio documentation¶
AlexPearce3D Studio is a node-based workspace for compositing, restoration, color, and delivery. These guides cover the current development preview and distinguish built-in workflows from features that depend on optional runtimes, hardware, or services.
Development preview
Interfaces, availability, and system requirements may change before beta. Use the availability guide to understand the current boundaries.
Start here¶
| Goal | Guide |
|---|---|
| Learn the workspace and make a first comp | Getting started |
| Understand every node and its status | Node reference |
| Bring in media and build a composite | Import and composite |
| Export a comp or create reusable delivery recipes | Export and delivery |
Featured workflows¶
- HDR to SDR covers tone-mapped SDR delivery from an HDR comp.
- Temporal denoise explains FastDVDnet review, export, and resume behavior.
- OpenEXR describes playback, processing precision, and file output choices.
- Camera RAW explains available controls and runtime-dependent support.
- Stage Program feed documents the experimental operator workflow and its hardware boundaries.
How to read status labels¶
The node reference uses four practical labels:
- Available: implemented in the development application.
- Runtime-dependent: requires an optional package, trusted runtime, model, SDK, or service.
- Workflow: coordinates another node or delivery path rather than transforming pixels directly.
- Viewer-only: changes monitoring or inspection without changing rendered output.
Availability in a development checkout does not guarantee that a given beta package includes every optional runtime.