Studio Engine

Parallel lines pass through a lens drawn in fine lines and gather at a bright point, then spread out past it, with one small fan of spectrum colors.Parallel lines pass through a lens drawn in fine lines and gather at a bright point, then spread out past it, with one small fan of spectrum colors.

procedural audiovisual engine

Studio Engine is a local Python simulation and rendering engine that generates shader visuals, audio, and motion from one reusable scene description. It exposes a CLI and local HTTP API, can render deterministic PNG frames, and records hashes and a receipt for each generated scene.

Status
active
Access
run
Release
active pre-1.0 source 0.2.0; no release
Checked
2026-08-27

Who it is for

Audiences

  • graphics engineers
  • software engineers

Deployment contexts

  • creative production pipelines
  • local development workspaces

Inputs and outputs

Inputs

  • seed and generator expression
  • render, sound, and motion parameters
  • critique and refinement constraints

Outputs

  • WebGL shader programs
  • WebAudio graphs
  • motion timelines
  • deterministic frames and receipts

Run or evaluate

Entrypython -m studio_engine 7 gyroid
Verificationpython -m unittest discover -s tests

Inspect the public source

Architecture and relationships

Related records

Architecture, dependencies, and relationship notes

Dependencies

None declared in the public registry.

Relation-backed claims

  • Studio Engine can invoke RAW as an optional native bridge
    Studio Engine can locate and invoke the optional RAW native CLI bridge; its Python core remains usable without RAW.

Current evidence

Studio Engine public source

Verified

How we know

The public main branch identifies Studio Engine 0.2.0; no GitHub release is claimed.

How we know

The pinned Python module defines RAW's native CLI as a separately built optional renderer and records honest absence when it is unavailable.

Limitations and authorization boundaries

  • Studio Engine is not presented as a finished product.
  • Browsers, GPUs, and audio hosts realize its programs; the native renderer is optional and APIs may move before 1.0.

Authorization boundary. Generated media must respect the rights, licenses, and consent attached to its inputs and intended use.