Local 3D shot control
Use this optional, portable record when a shot needs an editable local scene, named assets and a camera-match preview. It is a planning and review method, not a hosted production service.
Choose a route
Four valid ways to make a shot
- Cloud
- Use a cloud tool when its current controls, cost and rights fit the shot.
- Local 3D
- Use a local editable scene when asset state and camera control need to remain inspectable.
- Reference image-to-video
- Use a reference-led image-to-video route when that is the smallest useful way to test the intended shot.
- PREVIS
- Use boards, animatics or previs to test timing, geography and camera choices before committing to a final route.
Cloud and reference i2v are valid alternatives. This page does not require Local 3D for every film.
Local asset-lock checklist
- Name editable scene/assets.
- Record allowed state/exclusions.
- Make a camera-match preview.
- Review/revise drift.
- Run validator from shot-unit.
- Keep editable sources beside manifest; JSON does not contain them.
Each item is a local record and review step. It does not render, upload, approve or validate anything in the browser.
Downloads
Download the local asset-lock template (JSON)
Download the local asset-lock validator (Python)
The template contains no media. The validator reads files on your machine and never uploads them or uses a network connection.
Use the folder locally
Place a completed copy of the template at shot-unit/01-authority/asset-lock.json. Keep the referenced preview and editable source files inside that shot-unit, beside the manifest rather than embedded in JSON. Then run:
python3 validate_local_asset_lock.py /absolute/path/to/shot-unitA pass confirms only the listed local metadata, review flag and contained file paths. It does not judge the image, render a shot or grant approval.