mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-01 19:42:03 +00:00
ukimsanov
72d4016f5f
**Color grading** was the worst page in the docs by the measure that matters: 33 table rows against one image, for the most visual feature in the product. Four of the five tables were restating jargon in a grid — "Waveform | Brightness by horizontal image position" tells you nothing you could act on. Those are prose now, and the scopes section explains what each one is *for* (skin tones land on one known line of a vectorscope, so faces are quick to check). The control lookup stays a table, because that one is a genuine lookup. Four factual errors in the old page, each verified at source before changing: Studio's group is **Grade** in the flat Inspector, not "Color grading" in Design; the controls are `whites`/`blacks`, not "white point/black point"; LOG and HDR were conflated into one sentence when they are different cases; and the project-wide LUT copy refuses a relative path in favour of a URL or data URL, not a "project-root path". Two things the page never mentioned and should have: `hyperframes grade-compare`, which renders every candidate look onto one reference frame, and the fact that `data-color-grading` nests under adjust/details/effects — a flat object renders nothing at all. **vs Remotion** argued for 851 words with nothing to look at and no code. It now carries the same three-second title card written both ways. The HyperFrames one is a real composition, not illustrative markup: extracted and run through lint (0/0) and the full browser gate — runtime, layout, motion and contrast all pass. It also concedes what Remotion genuinely does better, because a comparison page that only flatters us is not worth reading. **Choose how to create** never said what the four options were before comparing them. It opens with the actual decision now — they all give you a video, the difference is what you keep — and a four-row table of what you walk away with. **Bring in a design** loses the 7-row keep-vs-rebuild table for one plain rule, and the bullet list that used semicolons. Every internal link on all four checked against the real page set. Where a visual belongs but no approved asset exists, there is a JSX comment marking the spot rather than a URL that would 404.
59 lines
2.3 KiB
Plaintext
59 lines
2.3 KiB
Plaintext
---
|
|
title: "Choose how to create"
|
|
sidebarTitle: "Choose how to create"
|
|
description: "Four places to make a HyperFrames video, and how to tell which one is yours."
|
|
---
|
|
|
|
There are four places to make a HyperFrames video. They all give you a video.
|
|
The difference is what you keep afterwards. Unsure? Take the first one.
|
|
|
|
| Start here | You end up with |
|
|
| --- | --- |
|
|
| A coding agent on your computer | A project folder you own and keep editing |
|
|
| An AI chat | A video made and kept in your HeyGen account |
|
|
| A design tool | A look to finish on your computer |
|
|
| HeyGen Video Agent | A finished video, assembled for you |
|
|
|
|
## Start on your computer if the video will change
|
|
|
|
A coding agent — an AI assistant that works in a folder on your machine, like
|
|
Claude Code or Cursor — writes a plain HTML project. Revise it with the agent,
|
|
open it in Studio, read the source, make the MP4 locally.
|
|
|
|
```text
|
|
Using /hyperframes, make a 10-second product intro for https://example.com.
|
|
```
|
|
|
|
[Make your first local video →](/quickstart)
|
|
|
|
## Start in an AI chat if you want nothing installed
|
|
|
|
The hosted HyperFrames connector (an MCP connector — a plug-in an AI chat can
|
|
use) builds and renders through your HeyGen account. You give up the project
|
|
folder, Studio, and local rendering.
|
|
|
|
[Connect HyperFrames to an AI chat →](/guides/mcp)
|
|
|
|
## Start in a design tool if the look is the open question
|
|
|
|
Figma, Claude Design, and Open Design settle brand, layout, and scene direction
|
|
first. Hand that draft to a coding agent for the motion, media, and rendering —
|
|
no design tool can tell you whether the movement works.
|
|
|
|
[Bring a design into a project →](/guides/design-tools)
|
|
|
|
## Start in HeyGen if you want it done for you
|
|
|
|
HeyGen Video Agent takes a prompt and assembles the script, visuals, narration,
|
|
avatar, and motion. It stays inside HeyGen — no folder, no source, no CLI — and
|
|
it can draw on your account allowance or credits. Rendering on your own computer
|
|
never does.
|
|
|
|
[Learn how HeyGen Video Agent works →](https://help.heygen.com/en/articles/12402907-how-to-get-started-with-video-agent)
|
|
|
|
## Related topics
|
|
|
|
- [Make a first local video](/quickstart)
|
|
- [Add an avatar presenter to a project you can still edit](/guides/avatar-presenter)
|
|
- [Build an app or a pipeline instead of one video](/developers)
|