Export Director cameras as a USD stage and use runtime shot timing

Address review on #1460:

- Replace the custom JSON manifest and the bpy importer with a plain-text
  .usda stage written from Node (no new dependency) that Blender imports
  natively: Z-up, metersPerUnit 1, one camera per shot with per-frame
  xformOp:transform samples, time codes equal to frame numbers, and lens
  attributes in tenths of a scene unit (Blender multiplies by
  100 * metersPerUnit).
- Take shot timing from shotRuntimeDurationSec/effectiveShotHoldSec, the
  functions Director playback and seeking use, so pack hold overrides,
  minimum holds and evidence-sequence durations match the app.
- Extract runtimeLayerStatesForShot in shotPresentation.js (behaviour
  unchanged) so holds for long scenes are resolved without quadratic work.
- Remove tools/blender Python files; update docs, tests and changelog.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01BahZiNcXqNSvAmR5TCuTAu
This commit is contained in:
UBN606andClaude Opus 5.5 committed 2026-11-03 19:34:33 +00:00
1 parent 6b60b9e969
commit 159c0cfcb0
14 files changed
+624 -865

No files matched your search

+8 -8
View File
@@ -647,14 +647,14 @@ untouched, and the shot is not rebuilt.
See [camera directions](DIRECTOR-CAMERA.md).
An opt-in offline [Blender camera bridge](BLENDER-CAMERAS.md) exports a saved
Director scene as ENU meter camera samples with an explicit WGS84 ellipsoid
origin, horizontal lens and rational fps. It reuses Director seek interpolation
and authored timing; runtime layer timing, implicit live flyTo paths, imagery
and geometry are outside this camera-only format. The Python importer creates
a separate editable scene with per-shot cameras and timeline markers.
The synthetic `tools/blender/check_import.py` check compares actual Blender
projection and saved-file reload against a separate Cesium Camera oracle
without rendering or provider access.
Director scene as a camera-only USD stage (`.usda`) that Blender imports
natively: Z-up meters in a local ENU frame around an explicit WGS84 ellipsoid
origin, one camera per shot with per-frame transforms, lens values in USD's
tenths of a scene unit and rational fps recorded alongside frame-number time
codes. It uses Director seek interpolation and the runtime shot timing from
`shotPresentation.js`, so registered pack holds, minimum holds and
evidence-sequence durations match playback. Implicit live flyTo paths, imagery
and geometry are outside this camera-only format.
Realtime voice composes separate connection, response/tool, Radio handoff, input
and audio-meter, cost, viewport-context and diagnostic owners. The existing