Turn video
into a live stream of
Unicode glyphs

Load the mesh demo

The editor’s demo picker has a single-image project wired with all six mesh effects in one stack. Open it and toggle the eye icons one at a time to see what each contributes — no video import needed.

The six effects

Each effect computes per-cell offsets independently; the GL pipeline sums them and applies one perspective transform per layer.

• fly-through — luma → depth, animate cameraZ to fly into the picture
• wave-blanket — radial ripple from a focal point
• blanket-shake — 1-D travelling wavefront at a chosen angle
• jelly-mesh — tap-driven damped oscillator
• cloth-drag — drag-point pull with gravity sag
• char-arrival — cells fly in from / out to scattered 3-D space, driven by segment progress

They compose by summing offsets

Stack two and the wobble is additive — drop a slow wave-blanket under a fast jelly-mesh for breathing motion under tap response, or animate fly-through’s cameraZ while a cloth-drag tugs the corner. No special compositing flag — just toggle both effects on the same layer.

• Per-cell vectors: each effect emits its own dx/dy/dz texture; the pipeline sums them before the perspective pass, so two effects can’t fight for the same pixel.
• Same hot path: mesh offsets are computed in the same WASM crate that converts pixels → glyphs, no extra worker hop per frame.

Real perspective, not a fake

The GL vertex pass treats every cell as a point in 3-D space: cameraZ moves the camera, FOV controls the cone, and the per-cell dz drives a real z-divide. Animate cameraZ from 3 to 0.2 on a fly-through layer and you get a true dolly-in, not a 2-D zoom.

The HTML export bundle reads cell depth from the binary stream and runs the same vertex shader, so a baked fly-through looks pixel-identical to the editor preview.

Load the demo

The editor's demo picker has a synthesised two-layer project — moving subject + inpainted plate — wired with all five depth-occlusion effects plus a spotlight. No video import needed.

Spotlight follows the subject

A pre-baked tracking point ships with 16 keyframes along the subject's trajectory; focusX and focusY are bound to it. Compare with vs. without — same frame, same subject position, but the spotlight only tracks when the binding is active.

Edit it from the inspector

The ⊕ Tracking button on the timeline toolbar swaps the inspector's per-segment view for a tracking control panel: add / delete points, keyframe positions by clicking on the preview, and wire points into effect params with either a pos (raw position) or spring (damped overshoot + settle) transform.

• Highlighted button when the selected segment lives on a layer that already has bindings — no need to open the panel just to check.
• Per-binding transform: swap pos for spring on a binding you already have to add overshoot to a previously snappy follower.
• Sparse keyframes: set 3-4 keyframes, the resolver linearly interpolates everything between. Sparse data is enough.

Compare the five depth effects

All five depth/occlusion effects ship in the demo, but only the spotlight is enabled by default. Toggle the eye icons one at a time to see what each contributes:

• occlusion-echo — per-cell brightness lift on freshly revealed cells (visibility-diff)
• occlusion-light-leak — warm tint on the same revealed-cells channel
• depth-refraction — per-cell row/col offsets driven by the depth-map gradient (Sobel kernel)
• interplane-bleed — per-cell brightness mix toward the neighbour layer's luma at the same coordinate
• depth-shadow-cast — per-cell dim where a closer-camera neighbour has high alpha (silhouette-shaped shadow)

On layers without their own per-cell mask (single-layer projects, metadata-only depth split) every effect transparently falls back to the original scalar approximation — no regression on existing projects.

One key per account, derived from a master secret

The first time you sign in the server runs HKDF over its master secret and your user id and produces a deterministic Ed25519 keypair — no key-generation event, no per-export key churn. Re-derive on any future call: same input → same keypair → same public key.

• Domain-separated: info = "cinerune-user-ed25519-v1" in the HKDF expand step. Bumping the version means cutting a new generation of keys deliberately, never by accident.
• Public key ships with the export: a downstream verifier doesn’t need to call our API to check a signature.

Per-leaf Merkle tree, batched 24 frames at a time

The editor hashes each frame’s source cells — before effects and watermark — into a 32-byte leaf, groups 24 leaves into a Merkle tree, and asks the server to sign the root. One Ed25519 signature covers 24 frames; per-leaf paths come back with the response so any single frame can be verified independently.

• Source frame, not render output: hashing before the watermark draws means the live preview can drop the watermark the instant a signature lands — no stale frame painted with an outdated proof.
• Self-verify in the browser: the editor re-runs Ed25519 verification client-side as a diagnostic before trusting a server response.

WASM verifies, watermark drops

Inside the render loop, WASM rebuilds the Merkle root from the leaf + path, verifies the Ed25519 signature against the embedded public key, and only then sets skip_watermark = true. No proof, wrong proof, or no public key → watermark draws as usual.

The IDE preview surfaces the gate state as a small ✓ signed as [email protected] badge so you can see the watermark removal isn’t a UI bug.

HTML exports carry the proofs offline

When you export to HTML, every signed batch — root, signature, per-leaf paths, content hashes — gets baked into meta.signatures alongside the public key and (opt-in) signer email. The standalone player wires the payload through the same WASM verifier, so the watermark gate works without our server in the loop.

• Tamper-resistant identity: the bundled email is also covered by an Ed25519 attestation over a canonical JSON of email + plan + projectId + issuedAt. A viewer who doesn’t trust the bundled field can re-verify the attestation offline.
• “Signed by” footer: the player reveals a <div id="signedby"> in the exported shell when a signer is present — fast-lookup chrome that sits next to the cryptographic proof, not in front of it.

Text-only projects skip the watermark overlay altogether — there’s no per-cell content stream for an attacker to swap, so the gate has nothing to defend.