mirror of https://github.com/hanzoai/video.git synced 2026-11-03 04:21:39 +00:00

Files

T

calesthio 50891a75b7 hyperframes: add HTML/CSS/GSAP as a parallel composition runtime

Separates creative grammar (renderer_family) from technical engine
(render_runtime) so HyperFrames can stand alongside Remotion as a
first-class runtime instead of masquerading as a Remotion sub-case.
Locks runtime choice at proposal stage and enforces it end-to-end: the
schemas require it, video_compose routes by it, the reviewer fails
closed on silent swaps, and a parametrized contract test walks every
pipeline manifest to ensure each planning-stage skill explains the
conversation to the user. Adds hyperframes_compose (scaffold/lint/
validate/render/doctor/add_block), a playbook -> CSS style bridge, and
vendored HyperFrames Layer 3 skills from commit d291358, pinned via
PROVENANCE.md for future re-sync. Final_review now records
render_runtime_used and runtime_swap_detected so compose lies are
catchable after the fact.

2026-04-18 18:37:00 -07:00

2.6 KiB

Raw Permalink Blame History

Idea Director - Localization Dub Pipeline

When To Use

Use this pipeline when the user has a source video and wants translated deliverables: subtitles, dubbed audio, or localized videos in one or more target languages.

Your first responsibility is to define what kind of localization is actually required, because subtitle-only, dubbed-audio, and lip-synced translation are different jobs.

Runtime Selection (MANDATORY — present the constraint, don't silently pick)

Lock render_runtime = "remotion" (composed deliverables with per-locale caption burn / lip-sync) or "ffmpeg" (pure subtitle-burn over source with no composition). HyperFrames is NOT a valid runtime on this pipeline in Phase 1 — localization depends on Remotion's caption stack and, for dubbed-with-lip-sync, on the Remotion TalkingHead pipeline.

Per AGENT_GUIDE.md → "Present Both Composition Runtimes (HARD RULE)": do NOT silently default to remotion. Tell the user: "HyperFrames is available, but localization-dub depends on Remotion caption + TalkingHead parity that isn't there yet in Phase 1 — remotion is the only viable choice". Record a render_runtime_selection decision with hyperframes rejected_because: "caption + lip-sync parity deferred on localization-dub".

Reference Inputs

docs/localization-dubbing-best-practices.md
skills/creative/short-form.md
skills/creative/long-form.md

Process

1. Define The Localization Scope

Capture:

source language,
target languages,
review owner,
whether glossary or legal review is required,
whether the user needs subtitles, dubbed audio, lip-sync, or a mix.

2. Classify The Source

Record the source mode:

single_speaker
multi_speaker
voiceover_led
speaker_led_on_camera

Also record whether on-screen text or motion graphics will need manual replacement or coverage.

3. Pick Deliverables That Match Reality

Possible deliverables:

subtitle package only,
dubbed video without lip sync,
lip-synced localized video,
per-language export bundle.

4. Build The Brief

Recommended metadata keys:

source_language
target_languages
deliverable_mode_map
glossary_terms
protected_terms
review_requirements
timing_risks

5. Quality Gate

localization scope is explicit,
target outputs are realistic,
glossary and review requirements are captured,
risk increases from speaker count or visible mouths are surfaced.

Common Pitfalls

Calling every translation request a dubbing request.
Ignoring glossary control until after audio is generated.
Promising lip sync on visually difficult source footage without warning.

2.6 KiB Raw Permalink Blame History