Release notes
Release notes
Track verified Oraphim release behavior, documentation baselines, important workflow changes, and known release boundaries.
Updated August 27, 2026Release notes
Use release notes to understand what changed in a shipped Oraphim build. Feature availability should be based on the installed release and current manual—not an old screenshot, roadmap item, or development certificate from another build.
Current documentation baseline
The public manual was reconciled against the current Oraphim release branch on 27 August 2026. It covers Edit, Composition, Motion Graphics, Color, Audio, VFX/3D, real OBJ/FBX/glTF/GLB scene import, OpenVDB volumes, proxy media, local AI model packages, MCP authoring, the audited effects catalog, and current professional delivery formats.
How to read release notes
- Available means the behavior is exposed by the current product path described in the manual.
- A certification document proves the scope it names; it does not automatically certify unrelated features or a later build.
- Hardware-dependent paths such as GPU features or hardware encoding can vary by machine and driver.
- Roadmap/planned features are not documented as shipped behavior.
Current release
Before delivering client work after an update, open an existing project copy, verify media links and critical effects, render a short representative range, then proceed to the full delivery only after that check passes.