VEHICLE LAB / DOCUMENTATION

Film, capture & embedding

Inside the evolution: the 37.5-second hero

Watch with music or inspect the cinematic study. Ridge R3d opens immediately, followed by the complete recorded 65-node, 68-link tree; wheel, bearing, chain and individual-link inspection; native wheel obstacle courses; matched recorded Chrono contact; coherent system separation; and the separate 73-part Baby AG23 study.

The hero uses 32 frames per second, exactly 15 frames per beat at 128 BPM. The original sample-free electronic score is MIT licensed. media/hero-capture.json binds the actual 1200 captured frames, scene sources and delivered media. media/hero-score.json retains the music generator, source hash and audio measurements.

The homepage plays a smaller silent loop when visible, with a pause button. Reduced-motion and data-saving preferences keep the poster until explicit play. The sound version starts on request.

Reproduce the hero

python3 -m pip install -r requirements-analysis.txt
python3 tools/hero_score.py --output media/hero-score.wav
npm run capture:hero -- --replace
npm run test:hero

Capture requires FFmpeg, Node.js, Playwright and a supported browser. The figure geometry is source-derived; display separation does not establish a viable assembly path. The 96-second educational walkthrough remains separate below.

The film is a deterministic capture of the running browser studio. Its models are project tessellations, and its physics segment replays saved solver frames. The presentation UI is designed for the walkthrough; it is not a recording of physical fabrication or a new solver run.

Deliverables

• media/vehicle-lab-pipeline.mp4: H.264 film for websites and playback.
• media/vehicle-lab-preview.gif: a compact looping preview for a README.
• media/vehicle-lab-poster.jpg: a still poster.
• media/vehicle-lab-pipeline.vtt: English captions.
• media/capture.json: source and media identities, frame count and capture settings.

Reproduce the film

Install Node.js 22, FFmpeg and the pinned browser tooling. The capture tool starts and closes its own isolated local server:

npm ci
npx playwright install chromium
npm run capture

On Linux with a working OpenGL GPU, set VEHICLE_LAB_GPU=1 to enable hardware rendering. Set CHROME_PATH only when using a separately installed browser. The capture script refuses to overwrite a completed film unless you pass --replace. Source changes produce a new capture receipt. The default output is 1920 × 1080 with a 96 second timeline.

GitHub README

Use a linked image or GIF for reliable README display. The repository file link opens the film; the website can play it inline.

[![Vehicle Lab pipeline](media/vehicle-lab-preview.gif)](media/vehicle-lab-pipeline.mp4)

GitHub's supported rendering differs from a general website. See GitHub's non-code file guide. Verify the rendered README after upload.

Portfolio or website

<video controls playsinline preload="metadata"
       poster="media/vehicle-lab-poster.jpg">
  <source src="media/vehicle-lab-pipeline.mp4" type="video/mp4">
  <track kind="captions" src="media/vehicle-lab-pipeline.vtt"
         srclang="en" label="English">
</video>

Keep the transcript and scope note beside the player. Avoid forcing autoplay or motion for visitors who prefer reduced motion.