Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.
TypeScript agentic-aiaiai-agentsai-videocompilerdslffmpeggenerative-aillmmarkup-languagemonorepoplugin-systemprogramming-languagetext-to-videotypescriptvideovideo-automationvideo-clonevideo-editingvideo-generation
docs: refresh the Studio quickstart
kashorin5b69f7b034ee
diff --git a/docs/quickstart/preview.md b/docs/quickstart/preview.mdindex cd86e266..cad4b949 100644--- a/docs/quickstart/preview.md+++ b/docs/quickstart/preview.md@@ -1,87 +1,40 @@----title: Live Preview-description: Read a Run whose material exists as an editable timeline.+title: Hypit Studio+description: Open a satisfied Run, inspect its picture and timeline, and edit real author Sources.----# Live Preview+# Hypit Studio-**Hypit Studio** opens a Run, traces its Film or Render target back to the projections it can edit,-and draws them — the code on the right, the picture top-left, a timeline bottom-left. It never-writes anything but the Author SVML, and it never calls a Provider.+Hypit Studio opens one `.svrun`, traces its Film or Render target back to explainable Semantic and Track projections, and presents four regions: Source at the upper left, Preview in the center, Inspector at the upper right, and Timeline below.-Studio builds only what it can derive deterministically from Candidates the Run already supplies, so-it needs a Run whose material is satisfied — every generated output either produced by an accepted-Build or standing against a file. That is what you point it at.+Studio never invokes a Provider or creates a Build. Generated material must already be selected by the Run as a real Candidate, either from a project file or from a Record accepted by an earlier Build and referenced through `<build-record>`. The display closure may contain no unresolved Need. Missing facts fail explicitly; Studio does not guess material or create placeholders.```bashhypit-studio --run examples/all-components-preview/studio.svrun --workspace .# ➜ http://localhost:5179/```-::: warning The examples in this repository need material first-`examples/all-components-preview/studio.svrun` is ready to open: it explicitly supplies its-Semantic Takes and the deterministic Script-owned CaptionDocument. Other example Runs may still name shots a Provider has to make, or-footage under `examples/**/assets/` that is not committed. Satisfy those in a Run of your own before-opening them.-:::-| Argument | Meaning || --- | --- |-| `--run <build.svrun>` | The Run Source to open. Required. Studio reads the Author SVML back out of it. |-| `--runtime <hypit.runtime.json>` | Where material earlier Builds produced is kept. Only a Run that reuses an accepted shot through `<build-record>` needs one. |-| `--workspace <directory>` | Defaults to the directory holding the Run. |-| `--port <number>` | Defaults to `5179`. |--The unit of work is the Run, not the `.svml`. What a Source is read *with* — which files stand for-which outputs, which Build records are reused — is an authoring decision, and the Run Source is-where that decision is written down. See [Run Source & Builds](./run).--::: tip Stop the previous server before starting another-A second Studio silently takes another port, and you end up reading a stale preview while-describing a new one. Stop the old one first:+| `--run <build.svrun>` | Run Source to open. Required. |+| `--runtime <hypit.runtime.json>` | Runtime Profile containing earlier Builds and Artifacts; required for `<build-record>`. |+| `--workspace <directory>` | Source access and writeback boundary; defaults to the Run directory. |+| `--port <number>` | HTTP port; defaults to `5179`. |-```bash-pkill -f "hypit-studio" || true-```+The unit of work is the Run, not an isolated `.svml`. The Run chooses the Author Source, targets and Candidates. Every Studio recompile continues to use that same Run instead of selecting another set of material in the background.-Use `--port` when you genuinely want two Runs side by side.-:::+## Which Runs can open-## What Studio draws+Studio requires:-Studio builds the deterministic closure of the Run and nothing else. Opening it never invokes a-Provider and never creates a Build, so every projection it draws was either supplied by the Run as-a Candidate or derived deterministically from one.+- a real Film or Render target;+- a traceable Semantic Track and display Tracks;+- satisfied material Candidates;+- a display closure completed by deterministic Producers.-**Everything structural is real.** Placement Frames, padding, stacking order, motion and the Track-layout are computed by the same functions a build calls, from your Source and your Recipes. A card-in the wrong part of the frame is wrong here too.+Studio refuses a Run that supplies only an opaque finished movie or whose display graph still requires external generation. It edits the current author graph and Tracks; it does not reconstruct a project from final pixels.-**Every timing is measured.** The timeline comes from the `SemanticTrack` — the aligned Takes-themselves — so a cut point you see is the cut point a build produces.--When something the closure needs is missing, Studio says so and stops:--```-Studio cannot start:-- the Studio projection closure requires unresolved capabilities: seedance.video-```--What it asks for:--| Refusal | What it means |-| --- | --- |-| `the Run Source has no target; Studio requires Film or Render` | Nothing in the Run names a finished programme to trace back from. |-| `the Run target is not a Film or Render output from the current SVML` | The target named does not exist in the Source as it stands now. |-| `Film has no traceable SemanticTake / Speech Track chain` | There is no semantic spine to hang a timeline on. |-| `the Studio projection closure requires unresolved capabilities: …` | A Track needs a Provider to exist. Satisfy it in the Run, or accept a Build. |-| `Render target … is an opaque media Candidate; Studio needs the current Film graph` | The Run points at a finished video file. Studio edits the graph, not the output. |--The fourth is the one you will meet most, and it is all-or-nothing: one unresolved capability-anywhere in the closure refuses the whole Run. A programme becomes openable in one step, when the-last of its generated outputs is satisfied.--## Supplying material you already have+A project file can satisfy an output directly. A result from an earlier Build can be reused through `<build-record>`:```svml<file id="take-1" type="@hypit/artifact@1#BlobArtifact"@@ -89,66 +42,35 @@ last of its generated outputs is satisfied.<satisfy output="take-opening.video" candidate="take-1"/>```-A `<build-record>` candidate names something an earlier Build made rather than a path, and needs-`--runtime` to find it.--## Where a Track came from--Selecting a Track names the Candidate that produced it and where it came from — the Run, the Source,-or neither. The header carries the same claim for the programme as a whole: `timing: measured` reads-from the aligned `SemanticTrack`, `picture: measured` that every element shows real material.--## When an agent is doing the work+## The four regions-If you are working through the [Hypit skill](https://github.com/hypit-ai/hypit/blob/main/.agents/skills/hypit/SKILL.md),-the agent starts Studio for you and sends you the link after a step that changes the Source — a-Script edit, a Frame moved, a B-roll placed, a Recipe adjusted.+### Source-Reading a diff is not the same as seeing where a cutaway lands, and this is the cheapest moment to-say "that card is too high".+The upper-left pane shows the current Author SVML with line numbers, highlighting, synchronized selection and text editing. It is not yet a complete Source workspace; browsing related SVS, SVRun, tasks and artifacts remains under separate design review.-## Moving around it+### Preview-The timeline, the source and the picture are three views of the same thing, so selecting in any of-them selects in all three. Click a clip and the playhead moves to its first frame, the picture-outlines it, and the source scrolls to the tag that placed it. Click a marked line in the source, or-whatever is drawn under the pointer, and the same happens.+The center pane uses real material and a HyperFrames picture. Structure, Frames, padding, stacking, motion and Track layout come from the same domain programs used by a Build, not from a Studio approximation.-A Segment encloses a Selection, which can enclose another Selection. Each level is drawn in its own-colour — in the source, on the timeline and on the picture — and an enclosing range stays outlined-while an inner one is, because the nesting is what the markers are for. Everything the playhead is-inside is outlined as it passes, whether or not a Track was hung on it.+### Inspector-Drag the ruler to scrub. `Space` plays and pauses, `←` and `→` step one frame with `Shift` for ten,-`Home` and `End` jump to the ends, and `Esc` clears the selection.+The upper-right pane shows the current entity's origin, timing, operations and adapter-exposed author parameters. Writable fields carry exact Source ranges. Values without one unambiguous write target remain read-only.-## The semantic lane+### Timeline-Above the Tracks is a lane that is not a Track: the `SemanticTrack` itself, drawn as one block per-Segment. It is the skeleton every other row is positioned against.+The lower pane places Semantic Segments, Words, Selections, Moments and component Tracks in one frame domain. Clicking selects and seeks; transport, frame stepping, zoom and scrolling are available. Move and trim are enabled only when an adapter declares the gesture and Studio resolves one author target.-At the whole-programme view a Segment is the useful unit, so that is all it draws. Zoom in and once-a Segment has enough width its words open into a real sub-lane beneath it, the way a pattern opens-into a piano roll. Double-click a Segment to zoom to it; the toolbar has explicit zoom controls, and-`Ctrl`-wheel pinches.+## How edits return to Source-Clicking a word moves the playhead to the frame that word starts on, which is the fastest way to-answer "does this cutaway land on the right sentence".+Studio exposes two structured author mutations:-## Selection, projection and consumption+- timeline gestures submit `timeline.adjust`;+- Inspector fields submit `parameter.adjust`.-A timeline block is not assumed to be the authored Selection. Studio keeps three facts separate:-the named semantic source, the component's projection from that source, and the frame windows the-component finally consumes. Selection ranges and Moment points remain visible on the semantic lane;-an item's projection line connects that source to its realized window. Components with nested-schedules, such as a Ranking Column, expose the total window and their reveal phases separately.+They follow the executed lineage selected by the Run to a real SVML or SVS preimage. Studio recompiles with the same Run after a change. It publishes the new picture only on success; on failure it restores the files and reports the domain error. It creates no hidden Build, invokes no Provider, and never turns a Selection into an anonymous frame span.-The current projection view is read-only. Its data contract and the remaining write-back questions-are recorded in [Studio Temporal Windows](../guide/studio-temporal-windows.md).+The complete selection, projection, consumption and writeback model is documented in [Studio Temporal Lineage](../guide/studio-temporal-windows.md).## Sound-HyperFrames renders a silent picture on purpose: programme audio is a separate Track the media-pipeline muxes in at the end. But placing B-roll against speech means hearing the speech, so the-Speech Track's own material is allowed to sound while the transport is running. Cutaways stay-silent, as they are in a build unless they ask otherwise. The speaker button turns it off.+HyperFrames owns the picture; the media pipeline assembles programme audio at the end. Studio may play the real Speech Track audio while previewing so B-roll can be judged against speech. Visual material without explicit audio is not given sound automatically.diff --git a/docs/zh/quickstart/preview.md b/docs/zh/quickstart/preview.mdindex 7edf8c9b..f0c50ad3 100644--- a/docs/zh/quickstart/preview.md+++ b/docs/zh/quickstart/preview.md@@ -1,70 +1,40 @@----title: 实时预览-description: 把一个素材已经存在的 Run 当作可编辑的时间线来读。+title: Studio 实时预览+description: 打开一份素材已经满足的 Run,检查画面、时间线并修改真实作者 Source。----# 实时预览+# Studio 实时预览-**Hypit Studio** 打开一个 Run,把它的 Film 或 Render target 回溯到自己能编辑的那些投影,然后画出来——右侧是代码,左上是画面,左下是时间线。除了 Author SVML 之外它不写入任何东西,也从不调用 Provider。+Hypit Studio 打开一份 `.svrun`,把它的 Film 或 Render target 回溯到可解释的 Semantic 与 Track 投影,并用四个区域呈现:左上 Source、中上 Preview、右上 Inspector、下方 Timeline。-Studio 只构建它能从 Run 已经提供的 Candidate 确定性推导出来的东西,因此它需要一个素材已被满足的 Run——每一个生成 output 要么由一次已接受的 Build 产出,要么由一个文件顶上。你指向的就是这样一个 Run。+Studio 不调用 Provider,也不创建 Build。需要生成的素材必须已经由 Run 选择为真实 Candidate:可以是项目文件,也可以是早先 Build 接受并由 `<build-record>` 引用的 Record。显示闭包里不允许残留 Need;缺失关系会明确失败,不猜测素材、不制造占位。```bashhypit-studio --run examples/all-components-preview/studio.svrun --workspace .# ➜ http://localhost:5179/```-::: warning 本仓库的示例需要先有素材-`examples/all-components-preview/studio.svrun` 可以直接打开:它显式提供了 Semantic Take 和字幕计划。其他示例 Run 仍可能指名需要 Provider 去做的镜头,或 `examples/**/assets/` 下未提交的素材。先在你自己的 Run 里满足它们,再打开。-:::-| 参数 | 含义 || --- | --- |-| `--run <build.svrun>` | 要打开的 Run Source。必填。Studio 会从它里面把 Author SVML 读回来。 |-| `--runtime <hypit.runtime.json>` | 早先 Build 产出的素材存放在哪里。只有通过 `<build-record>` 复用已接受镜头的 Run 才需要。 |-| `--workspace <directory>` | 默认为 Run 所在的目录。 |-| `--port <number>` | 默认 `5179`。 |--工作单元是 Run,不是 `.svml`。用什么去读一个 Source——哪些文件顶替哪些 output、复用哪些 Build 记录——是一项创作决策,而 Run Source 正是写下这项决策的地方。见 [Run Source 与 Build](./run)。--::: tip 启动新服务前先停掉上一个-第二个 Studio 会悄悄占用另一个端口,于是你一边读着过期的预览,一边描述着新的改动。先把旧的停掉:+| `--run <build.svrun>` | 要打开的 Run Source。必填。 |+| `--runtime <hypit.runtime.json>` | 选择包含早先 Build 与 Artifact 的 Runtime Profile;使用 `<build-record>` 时需要。 |+| `--workspace <directory>` | Source 访问与写回边界;默认是 Run 所在目录。 |+| `--port <number>` | HTTP 端口,默认 `5179`。 |-```bash-pkill -f "hypit-studio" || true-```+Studio 的工作单元是 Run,不是孤立的 `.svml`。Run 决定当前 Author Source、目标和 Candidate;Studio 的每次重新编译都继续使用同一份 Run,不会在后台选择另一套素材。-确实想并排看两个 Run 时,再用 `--port`。-:::+## 什么样的 Run 可以打开-## Studio 画什么+Studio 需要:-Studio 只构建 Run 的确定性闭包,除此之外什么都不做。打开 Studio 从不调用 Provider,也从不创建 Build,因此它画出的每一个投影,要么由 Run 作为 Candidate 提供,要么可以从这样一个 Candidate 确定性地推导出来。+- 一个真实存在的 Film 或 Render target;+- 可以追溯的 Semantic Track 与可展示 Track;+- 已经满足的素材 Candidate;+- 能由确定性 Producer 完成的显示闭包。-**所有结构性的东西都是真的。** Placement Frame、padding、堆叠顺序、动效以及 Track 布局,都由构建时调用的同一批函数、从你的 Source 和 Recipe 算出。一张卡片如果在画面里的位置不对,在这里同样是不对的。+如果 Run 只提供一个不透明成片,或某条显示链仍要求外部生成,Studio 会拒绝启动。它编辑的是当前作者图和 Track,不从最终视频反推一份新工程。-**每一处时序都是实测的。** 时间线来自 `SemanticTrack`——也就是已对齐的那些 Take 本身——所以你看到的剪切点就是构建产出的剪切点。--当闭包需要的某样东西缺失时,Studio 会说明并停下:--```-Studio cannot start:-- the Studio projection closure requires unresolved capabilities: seedance.video-```--它要求的是:--| 拒绝 | 含义 |-| --- | --- |-| `the Run Source has no target; Studio requires Film or Render` | Run 里没有任何东西指名一个可供回溯的成片。 |-| `the Run target is not a Film or Render output from the current SVML` | 指名的 target 在当前这份 Source 里并不存在。 |-| `Film has no traceable SemanticTake / Speech Track chain` | 没有语义骨架可以用来挂时间线。 |-| `the Studio projection closure requires unresolved capabilities: …` | 某条 Track 需要 Provider 才能存在。要么在 Run 里满足它,要么接受一次 Build。 |-| `Render target … is an opaque media Candidate; Studio needs the current Film graph` | Run 指向的是一个已经渲染好的视频文件。Studio 编辑的是图,不是产物。 |--第四条是你最常遇到的,而且它是全有或全无:闭包里任何一个未解决的 capability 都会拒绝整个 Run。一个节目是在某一步里整个变得可打开的——当它最后一个生成 output 被满足时。--## 提供你已经有的素材+项目文件可以直接满足一个输出;早先 Build 的结果可以通过 `<build-record>` 复用:```svml<file id="take-1" type="@hypit/artifact@1#BlobArtifact"@@ -72,40 +42,35 @@ Studio cannot start:<satisfy output="take-opening.video" candidate="take-1"/>```-`<build-record>` 候选指名的是早先某次 Build 做出的东西而非一个路径,需要 `--runtime` 才能找到。--## 一条 Track 从哪来--选中一条 Track,会说明是哪个 Candidate 产出了它,以及它从哪里来——Run、Source,或者都不是。顶部对整个节目给出同样的判断:`timing: measured` 读自已对齐的 `SemanticTrack`,`picture: measured` 表示每个元素展示的都是真实素材。--## 当由 agent 来做这件事时+## 四个区域-如果你正在通过 [Hypit skill](https://github.com/hypit-ai/hypit/blob/main/.agents/skills/hypit/SKILL.md)工作,那么每当某个步骤改动了 Source——改了 Script、移了 Frame、放了 B-roll、调了 Recipe——agent 会为你启动 Studio 并把链接发给你。+### Source-读 diff 和亲眼看见空镜落在哪里不是一回事,而此刻正是说出"那张卡片太靠上了"的最便宜的时机。+左上显示当前 Author SVML,支持行号、高亮、选择联动和文本编辑。当前版本还不是完整的 Source workspace;相关 SVS、SVRun、任务与产物浏览仍在单独调研。-## 在里面移动+### Preview-时间线、代码与画面是同一件事的三个视角,因此在任何一个里选中,另外两个都会跟着选中。点击一个片段,播放头会移到它的首帧,画面上会把它框出来,代码会滚动到安放它的那个标签。点击代码里被标记的行,或者画面上指针所指之处,效果相同。+中上使用真实素材和 HyperFrames 画面。结构、Frame、padding、堆叠、动效和 Track 布局来自与 Build 相同的领域程序,不是 Studio 的近似重绘。-Segment 包着 Selection,Selection 还能再包 Selection。每一层有自己的颜色——在源码、时间线和画面上保持一致——而且内层被框住时外层依然保持框住,因为嵌套关系正是这些标记存在的理由。播放头经过的每一个范围都会被框出来,不管有没有 Track 挂在它上面。+### Inspector-拖动标尺即可走带。`Space` 播放与暂停,`←` 和 `→` 步进一帧、按住 `Shift` 为十帧,`Home` 和 `End` 跳到首尾,`Esc` 清除选中。+右上显示当前实体的来源、时间、操作能力和 adapter 公开的作者参数。可写字段都带精确 Source range;没有唯一写回目标的值保持只读。-## 语义泳道+### Timeline-Track 之上有一条并不是 Track 的泳道:`SemanticTrack` 本身,每个 Segment 画成一块。它是其余每一行赖以定位的骨架。+下方把 Semantic Segment、Word、Selection、Moment 和组件 Track 放到同一帧域。点击实体会选择并 seek;可以播放、逐帧移动、缩放和滚动。只有 adapter 声明且能够解析到唯一作者目标的 move/trim 手势才会启用。-在整片视图下,Segment 就是有用的单位,所以它只画到这一层。放大之后,一旦某个 Segment 有了足够的宽度,它的词就会在它下方展开成一条真正的子泳道,就像一个 pattern 展开成钢琴卷帘那样。双击一个 Segment 可以缩放到它;工具栏上有显式的缩放控件,`Ctrl` + 滚轮可以捏合缩放。+## 修改怎样落回 Source-点击一个词,播放头会移到那个词开始的帧——这是回答"这个空镜是不是落在正确的那句话上"最快的方式。+Studio 有两类结构化作者操作:-## 选择、投影与消费+- 时间线手势提交 `timeline.adjust`;+- Inspector 参数提交 `parameter.adjust`。-时间线上的块不会被默认当成作者写下的 Selection。Studio 分开保留三个事实:具名的语义来源、组件对该来源的投影,以及组件最终消费的帧窗口。Selection 区间和 Moment 时点保留在语义泳道上;item 的投影线把该来源连到实际窗口。像 Ranking Column 这样含子调度的组件,会分开显示总窗口和各揭示阶段。+它们沿本次 Run 的真实执行谱系找到 SVML/SVS 中的作者逆像。修改后 Studio 使用同一 Run 重新编译;成功才发布新画面,失败就恢复文件并显示真实领域错误。它不会创建隐藏 Build、调用 Provider,或把 Selection 偷换成绝对帧。-当前投影视图只读。它的数据契约与尚未确定的回写问题记录在 [Studio 时间窗口](../guide/studio-temporal-windows.md)。+选择、投影、消费与写回的完整语义见 [Studio 时间谱系](../guide/studio-temporal-windows.md) 和 [Studio 作者操作](../guide/studio-timeline-operations.md)。## 声音-HyperFrames 刻意只渲染无声画面:programme audio 是一条独立的 Track,由 media pipeline 在最后 mux 进去。但把 B-roll 对着语音安放,前提就是能听见那句话,所以走带播放时 Speech Track 自己的素材允许发声。Cutaway 保持静音——除非显式声明要带音频,这和真实构建里的行为一致。喇叭按钮可以关掉。+HyperFrames 只负责画面;Programme audio 最终由媒体管线装配。为了按口播检查 B-roll 时机,Studio 播放时可以同步播放 Speech Track 的真实音频。没有显式音频的视觉素材不会被自动赋予声音。