agentcut 0.2.26 → 0.2.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +177 -177
- package/dist/studio/agents/claude.js +3 -2
- package/dist/studio/agents/claude.js.map +1 -1
- package/dist/studio/chat.js +1 -1
- package/dist/studio/chat.js.map +1 -1
- package/dist/studio/cli.js +24 -24
- package/dist/studio/download.d.ts +24 -0
- package/dist/studio/download.js +234 -0
- package/dist/studio/download.js.map +1 -0
- package/dist/studio/host.js +8 -0
- package/dist/studio/host.js.map +1 -1
- package/dist/studio/housekeeping.d.ts +2 -2
- package/dist/studio/housekeeping.js +18 -17
- package/dist/studio/housekeeping.js.map +1 -1
- package/dist/studio/release-cursor.js +21 -21
- package/dist/studio/release-video.js +10 -10
- package/dist/studio/tools.js +7 -0
- package/dist/studio/tools.js.map +1 -1
- package/package.json +56 -56
- package/template/AGENTS.md +14 -14
- package/template/components/README.md +70 -70
- package/template/components/before-after/BeforeAfter.tsx +89 -89
- package/template/components/catalog.ts +107 -107
- package/template/components/cinematic/Device3D.tsx +324 -324
- package/template/components/cinematic/devices3d/display-model.ts +184 -184
- package/template/components/cinematic/devices3d/iphone-model.ts +643 -643
- package/template/components/cinematic/devices3d/macbook-model.ts +608 -608
- package/template/components/cinematic/devices3d/models.ts +657 -657
- package/template/components/cinematic/devices3d/runtime.ts +267 -267
- package/template/components/cinematic/math.ts +100 -100
- package/template/components/color/grade-effect.ts +650 -650
- package/template/components/color/grade.ts +512 -512
- package/template/components/color/looks.ts +154 -154
- package/template/components/countdown/Countdown.tsx +166 -166
- package/template/components/dot-trace-title/DotTraceTitle.tsx +181 -181
- package/template/components/dot-trace-title/meta.json +51 -51
- package/template/components/generate/GenerateReveal.tsx +381 -381
- package/template/components/hook-card/HookCard.tsx +554 -554
- package/template/components/index.ts +199 -199
- package/template/components/lib.ts +191 -191
- package/template/components/line-diagram/LineDiagram.tsx +205 -205
- package/template/components/line-diagram/meta.json +215 -215
- package/template/components/list-card/ListCard.tsx +104 -104
- package/template/components/live-clip.ts +75 -75
- package/template/components/looks.tsx +1447 -1447
- package/template/components/loops/LoopCanvas.tsx +132 -132
- package/template/components/loops/engine.ts +184 -184
- package/template/components/loops/library.ts +667 -667
- package/template/components/loops/library2.ts +777 -777
- package/template/components/motion-loop/MotionLoop.tsx +37 -37
- package/template/components/motion-loop/meta.json +311 -311
- package/template/components/props.ts +73 -73
- package/template/components/quote-card/QuoteCard.tsx +71 -71
- package/template/components/style-layer.tsx +233 -233
- package/template/components/styles.ts +113 -113
- package/template/components/types.ts +66 -66
- package/template/components/word-pop/WordPop.tsx +59 -59
- package/template/components/word-stack/WordStack.tsx +122 -122
- package/template/presets/charcoal-sketch/PROMPT.md +48 -48
- package/template/presets/charcoal-sketch/scripts/duck_music.py +34 -34
- package/template/presets/punk-cut-paper/scenes/Motif.tsx +376 -376
- package/template/presets/punk-cut-paper/scenes/Photo.tsx +73 -73
- package/template/presets/punk-cut-paper/scenes/Ransom.tsx +119 -119
- package/template/runtime/composition.tsx +1189 -1189
- package/template/runtime/helpers.tsx +230 -230
- package/template/runtime/index.tsx +22 -22
- package/template/runtime/types.ts +315 -315
- package/template/skill/SKILL.md +186 -187
- package/template/skill/references/broll.md +44 -44
- package/template/skill/references/browser-export.md +61 -61
- package/template/skill/references/cinematic.md +206 -206
- package/template/skill/references/color.md +79 -79
- package/template/skill/references/craft.md +97 -97
- package/template/skill/references/editing-styles.md +57 -57
- package/template/skill/references/feature-launch.md +34 -34
- package/template/skill/references/footage.md +72 -72
- package/template/skill/references/format.md +142 -142
- package/template/skill/references/how-to.md +146 -146
- package/template/skill/references/launch-direction.md +89 -89
- package/template/skill/references/loops.md +151 -151
- package/template/skill/references/mcp-external.md +19 -19
- package/template/skill/references/performance.md +93 -93
- package/template/skill/references/person-cutout.md +19 -19
- package/template/skill/references/presets.md +60 -60
- package/template/skill/references/product-launch.md +134 -134
- package/template/skill/references/release-capture.md +53 -53
- package/template/skill/references/sound.md +167 -166
- package/template/skill/references/style-spy.md +160 -160
- package/template/skill/references/website-howto.md +45 -45
- package/template/starter/.studio/chat.json +1 -1
- package/template/starter/layers.json +46 -46
- package/template/starter/notes.md +4 -4
- package/template/starter/project.json +13 -13
- package/template/starter/scenes/Title.tsx +38 -38
|
@@ -1,97 +1,97 @@
|
|
|
1
|
-
# Craft: direction, layout and motion
|
|
2
|
-
|
|
3
|
-
What makes Agentcut videos work. The user's script, reference, chosen style and format come first.
|
|
4
|
-
|
|
5
|
-
## Direction: one idea, written down before you build
|
|
6
|
-
|
|
7
|
-
A video without a direction comes out as generic cards on a gradient. Before the first scene, write
|
|
8
|
-
a look sheet in `notes.md` (five to ten lines) and build from it. For a small edit to an existing
|
|
9
|
-
video, keep its direction.
|
|
10
|
-
|
|
11
|
-
- **The idea in one sentence**: what the viewer should feel and remember, and the one visual device
|
|
12
|
-
that carries it (a recurring shape, a material, a camera habit, a type treatment, a colour event).
|
|
13
|
-
Draft two different ideas and keep the one the footage and brand can actually show.
|
|
14
|
-
- **A motif that returns**: introduce it in the first two seconds, vary it through the middle, pay it
|
|
15
|
-
off on the end card. Example: the logo's corner radius becomes the mask for every transition.
|
|
16
|
-
- **Contrast is the spice**: plan where the video changes scale (wide → extreme close), density (one
|
|
17
|
-
word → a full screen), tone (dark → light → accent), speed (hold → burst) and sound (bed → silence
|
|
18
|
-
→ hit). At least one deliberate change every 3–5 s; never the same layout three shots running.
|
|
19
|
-
- **One surprise**: a single moment that breaks the pattern you set (a full-bleed colour flood, type
|
|
20
|
-
that fills the frame, a hard cut to silence). One, placed on the reveal or the drop.
|
|
21
|
-
- **The look in real values**: background, text and accent colours as hex from the brand
|
|
22
|
-
(`loops.md` › Brand palette first), font families and weights, the type scale and margins below,
|
|
23
|
-
entrance and exit timings in frames. A project `style` supplies these: use its tokens and say so.
|
|
24
|
-
- **Name what you will avoid** for this video: repeated feature cards, tiny UI on an empty stage,
|
|
25
|
-
the same spring on every element, decoration that competes with the proof.
|
|
26
|
-
|
|
27
|
-
Check the direction early: build the opening and the strongest shot first, capture both formats,
|
|
28
|
-
and only then extend the treatment to the rest.
|
|
29
|
-
|
|
30
|
-
## Layout system: every frame sits on the same grid
|
|
31
|
-
|
|
32
|
-
Define these once in a constants object the scenes share (or take them from the project style), so
|
|
33
|
-
every scene lines up with the next.
|
|
34
|
-
|
|
35
|
-
- **Margins**: 5–6% of the short side on every edge (≈ 60 px at 1080). Nothing the viewer must read
|
|
36
|
-
sits outside them. Mobile also keeps clear of the top 10% and bottom 18% (platform UI).
|
|
37
|
-
- **Grid**: 12 columns in wide, 6 in mobile, with one gutter value. Blocks start and end on column
|
|
38
|
-
lines; text aligns to the same left edge or the same centre line from shot to shot.
|
|
39
|
-
- **Type scale**: four sizes at most, in a fixed ratio (≈ 1.5): display, title, body, label. At 1080
|
|
40
|
-
short side: display 150–220, title 90–130, body 40–56, label 28–34 px. Two families at most; weight
|
|
41
|
-
and size make the hierarchy, not extra colours. Line length under about 28 characters for titles.
|
|
42
|
-
- **One focal point per frame**: the largest, brightest or only moving thing is what the shot is about.
|
|
43
|
-
Give it 40–60% of the frame; everything else is smaller, dimmer and still. Leave empty space on
|
|
44
|
-
purpose: a third of the frame clear reads as confident, not unfinished.
|
|
45
|
-
- **Spacing in steps**: one base unit (≈ 12 px at 1080) and its multiples for every gap and padding;
|
|
46
|
-
the same radius, stroke width and shadow on every card.
|
|
47
|
-
- **Both formats are designed**: wide composes left-to-right (text beside the subject), mobile stacks
|
|
48
|
-
(subject above, text below, larger type). Recompose with `variants.mobile`; never just scale down.
|
|
49
|
-
- **Check it**: a contact sheet should show the same margins and baselines in every tile. If a title
|
|
50
|
-
jumps position between two similar shots, fix the grid, not the shot.
|
|
51
|
-
|
|
52
|
-
## Structure
|
|
53
|
-
|
|
54
|
-
- **One idea per beat**, 2–6 s each. A 60 s launch spot has ~10 beats: pain → reveal → 3–6 feature beats →
|
|
55
|
-
proof/flow → end card (logo, URL, "now live").
|
|
56
|
-
- **The voice drives the cuts.** Every scene starts a few frames (≈ 8 f at 30 fps) before the word it
|
|
57
|
-
illustrates; on-screen elements pop on their keyword's start frame. Keep a word-index cue table in
|
|
58
|
-
notes.md (`reveal = word "meet" − 8f`). With no voice, the music's beats and sections drive it.
|
|
59
|
-
- **Music has a shape**: quiet intro under the hook, a drop on the reveal, a final chord on the end card.
|
|
60
|
-
Put markers on the drop and the final hit; cut and flash on them.
|
|
61
|
-
|
|
62
|
-
## Motion
|
|
63
|
-
|
|
64
|
-
- Entrances: springs. `pop` (scale 0.6→1 + rise + fade over ~5 f), `rise` (fade + 30 px rise), `land` for
|
|
65
|
-
heavy titles. Stagger lists by 3–6 frames.
|
|
66
|
-
- Exits: short eased fades with a slight scale-down / rise and blur (≈ 7 frames), overlapping the next
|
|
67
|
-
scene's entrance.
|
|
68
|
-
- After the drop, a **beat pulse** (0..1 decaying over ~8 f on each beat) drives subtle scale/brightness of
|
|
69
|
-
backgrounds and accents — never the text you need to read.
|
|
70
|
-
- Flashes: brief white overlay (opacity ≤ 0.35, ~10 f) on the drop and the final hit only.
|
|
71
|
-
- Camera moves over rebuilt UI: ease in/out between framings, hold long enough to read (≥ 1.2 s per line of
|
|
72
|
-
text the viewer must read).
|
|
73
|
-
|
|
74
|
-
## Visuals
|
|
75
|
-
|
|
76
|
-
- **Use real product evidence** for demonstrations: recorded actions and their visible results.
|
|
77
|
-
Screenshots can explain static views; crop within their available resolution and check sharpness.
|
|
78
|
-
Rebuilt UI is an illustration, not proof of an interaction. Follow the active workflow's disclosure
|
|
79
|
-
and approval rules. Do not replace real footage with a mock interface to make a camera move easier.
|
|
80
|
-
- Brand palette in one constant object; one gradient for accents; dark backgrounds with radial glows
|
|
81
|
-
(`RadialGlow`) for depth.
|
|
82
|
-
- Icons as inline SVG strokes (24×24 viewBox, round caps), not emoji.
|
|
83
|
-
- Abstract props only: no drawn hands, bodies or figure-like shapes.
|
|
84
|
-
- Lyric videos: one phrase per layout, accent words highlighted, kicker words smaller; the look follows the
|
|
85
|
-
genre (night-station LED, xerox art-punk, pastel line diagrams, tattoo flash…).
|
|
86
|
-
|
|
87
|
-
## Captions
|
|
88
|
-
|
|
89
|
-
Word-by-word for talking-head and voice-driven pieces: 2–4 words per line, the active word highlighted,
|
|
90
|
-
lines break at pauses. Check fast passages by capture; transcripts can merge or drop words.
|
|
91
|
-
|
|
92
|
-
## Before calling it done
|
|
93
|
-
|
|
94
|
-
- Contact sheet of each variant: no clipped text, no empty frames between scenes, consistent margins.
|
|
95
|
-
- `agentcut_listen_critique`: loudness near −14 LUFS after export normalization, voice clearly above
|
|
96
|
-
music, every SFX on its cue.
|
|
97
|
-
- notes.md updated: cue sheet, sound choices with their numbers, anything the user should know.
|
|
1
|
+
# Craft: direction, layout and motion
|
|
2
|
+
|
|
3
|
+
What makes Agentcut videos work. The user's script, reference, chosen style and format come first.
|
|
4
|
+
|
|
5
|
+
## Direction: one idea, written down before you build
|
|
6
|
+
|
|
7
|
+
A video without a direction comes out as generic cards on a gradient. Before the first scene, write
|
|
8
|
+
a look sheet in `notes.md` (five to ten lines) and build from it. For a small edit to an existing
|
|
9
|
+
video, keep its direction.
|
|
10
|
+
|
|
11
|
+
- **The idea in one sentence**: what the viewer should feel and remember, and the one visual device
|
|
12
|
+
that carries it (a recurring shape, a material, a camera habit, a type treatment, a colour event).
|
|
13
|
+
Draft two different ideas and keep the one the footage and brand can actually show.
|
|
14
|
+
- **A motif that returns**: introduce it in the first two seconds, vary it through the middle, pay it
|
|
15
|
+
off on the end card. Example: the logo's corner radius becomes the mask for every transition.
|
|
16
|
+
- **Contrast is the spice**: plan where the video changes scale (wide → extreme close), density (one
|
|
17
|
+
word → a full screen), tone (dark → light → accent), speed (hold → burst) and sound (bed → silence
|
|
18
|
+
→ hit). At least one deliberate change every 3–5 s; never the same layout three shots running.
|
|
19
|
+
- **One surprise**: a single moment that breaks the pattern you set (a full-bleed colour flood, type
|
|
20
|
+
that fills the frame, a hard cut to silence). One, placed on the reveal or the drop.
|
|
21
|
+
- **The look in real values**: background, text and accent colours as hex from the brand
|
|
22
|
+
(`loops.md` › Brand palette first), font families and weights, the type scale and margins below,
|
|
23
|
+
entrance and exit timings in frames. A project `style` supplies these: use its tokens and say so.
|
|
24
|
+
- **Name what you will avoid** for this video: repeated feature cards, tiny UI on an empty stage,
|
|
25
|
+
the same spring on every element, decoration that competes with the proof.
|
|
26
|
+
|
|
27
|
+
Check the direction early: build the opening and the strongest shot first, capture both formats,
|
|
28
|
+
and only then extend the treatment to the rest.
|
|
29
|
+
|
|
30
|
+
## Layout system: every frame sits on the same grid
|
|
31
|
+
|
|
32
|
+
Define these once in a constants object the scenes share (or take them from the project style), so
|
|
33
|
+
every scene lines up with the next.
|
|
34
|
+
|
|
35
|
+
- **Margins**: 5–6% of the short side on every edge (≈ 60 px at 1080). Nothing the viewer must read
|
|
36
|
+
sits outside them. Mobile also keeps clear of the top 10% and bottom 18% (platform UI).
|
|
37
|
+
- **Grid**: 12 columns in wide, 6 in mobile, with one gutter value. Blocks start and end on column
|
|
38
|
+
lines; text aligns to the same left edge or the same centre line from shot to shot.
|
|
39
|
+
- **Type scale**: four sizes at most, in a fixed ratio (≈ 1.5): display, title, body, label. At 1080
|
|
40
|
+
short side: display 150–220, title 90–130, body 40–56, label 28–34 px. Two families at most; weight
|
|
41
|
+
and size make the hierarchy, not extra colours. Line length under about 28 characters for titles.
|
|
42
|
+
- **One focal point per frame**: the largest, brightest or only moving thing is what the shot is about.
|
|
43
|
+
Give it 40–60% of the frame; everything else is smaller, dimmer and still. Leave empty space on
|
|
44
|
+
purpose: a third of the frame clear reads as confident, not unfinished.
|
|
45
|
+
- **Spacing in steps**: one base unit (≈ 12 px at 1080) and its multiples for every gap and padding;
|
|
46
|
+
the same radius, stroke width and shadow on every card.
|
|
47
|
+
- **Both formats are designed**: wide composes left-to-right (text beside the subject), mobile stacks
|
|
48
|
+
(subject above, text below, larger type). Recompose with `variants.mobile`; never just scale down.
|
|
49
|
+
- **Check it**: a contact sheet should show the same margins and baselines in every tile. If a title
|
|
50
|
+
jumps position between two similar shots, fix the grid, not the shot.
|
|
51
|
+
|
|
52
|
+
## Structure
|
|
53
|
+
|
|
54
|
+
- **One idea per beat**, 2–6 s each. A 60 s launch spot has ~10 beats: pain → reveal → 3–6 feature beats →
|
|
55
|
+
proof/flow → end card (logo, URL, "now live").
|
|
56
|
+
- **The voice drives the cuts.** Every scene starts a few frames (≈ 8 f at 30 fps) before the word it
|
|
57
|
+
illustrates; on-screen elements pop on their keyword's start frame. Keep a word-index cue table in
|
|
58
|
+
notes.md (`reveal = word "meet" − 8f`). With no voice, the music's beats and sections drive it.
|
|
59
|
+
- **Music has a shape**: quiet intro under the hook, a drop on the reveal, a final chord on the end card.
|
|
60
|
+
Put markers on the drop and the final hit; cut and flash on them.
|
|
61
|
+
|
|
62
|
+
## Motion
|
|
63
|
+
|
|
64
|
+
- Entrances: springs. `pop` (scale 0.6→1 + rise + fade over ~5 f), `rise` (fade + 30 px rise), `land` for
|
|
65
|
+
heavy titles. Stagger lists by 3–6 frames.
|
|
66
|
+
- Exits: short eased fades with a slight scale-down / rise and blur (≈ 7 frames), overlapping the next
|
|
67
|
+
scene's entrance.
|
|
68
|
+
- After the drop, a **beat pulse** (0..1 decaying over ~8 f on each beat) drives subtle scale/brightness of
|
|
69
|
+
backgrounds and accents — never the text you need to read.
|
|
70
|
+
- Flashes: brief white overlay (opacity ≤ 0.35, ~10 f) on the drop and the final hit only.
|
|
71
|
+
- Camera moves over rebuilt UI: ease in/out between framings, hold long enough to read (≥ 1.2 s per line of
|
|
72
|
+
text the viewer must read).
|
|
73
|
+
|
|
74
|
+
## Visuals
|
|
75
|
+
|
|
76
|
+
- **Use real product evidence** for demonstrations: recorded actions and their visible results.
|
|
77
|
+
Screenshots can explain static views; crop within their available resolution and check sharpness.
|
|
78
|
+
Rebuilt UI is an illustration, not proof of an interaction. Follow the active workflow's disclosure
|
|
79
|
+
and approval rules. Do not replace real footage with a mock interface to make a camera move easier.
|
|
80
|
+
- Brand palette in one constant object; one gradient for accents; dark backgrounds with radial glows
|
|
81
|
+
(`RadialGlow`) for depth.
|
|
82
|
+
- Icons as inline SVG strokes (24×24 viewBox, round caps), not emoji.
|
|
83
|
+
- Abstract props only: no drawn hands, bodies or figure-like shapes.
|
|
84
|
+
- Lyric videos: one phrase per layout, accent words highlighted, kicker words smaller; the look follows the
|
|
85
|
+
genre (night-station LED, xerox art-punk, pastel line diagrams, tattoo flash…).
|
|
86
|
+
|
|
87
|
+
## Captions
|
|
88
|
+
|
|
89
|
+
Word-by-word for talking-head and voice-driven pieces: 2–4 words per line, the active word highlighted,
|
|
90
|
+
lines break at pauses. Check fast passages by capture; transcripts can merge or drop words.
|
|
91
|
+
|
|
92
|
+
## Before calling it done
|
|
93
|
+
|
|
94
|
+
- Contact sheet of each variant: no clipped text, no empty frames between scenes, consistent margins.
|
|
95
|
+
- `agentcut_listen_critique`: loudness near −14 LUFS after export normalization, voice clearly above
|
|
96
|
+
music, every SFX on its cue.
|
|
97
|
+
- notes.md updated: cue sheet, sound choices with their numbers, anything the user should know.
|
|
@@ -1,57 +1,57 @@
|
|
|
1
|
-
# Reusable editing styles
|
|
2
|
-
|
|
3
|
-
An editing style is a named prompt that describes **how to edit different footage**. It is separate from
|
|
4
|
-
the built-in talking-head looks and the scene/asset kits in `library/presets/`.
|
|
5
|
-
|
|
6
|
-
## Save current style
|
|
7
|
-
|
|
8
|
-
The plus action beside Styles in chat, or Save current style in the gallery, sends a save request with a name.
|
|
9
|
-
Saving must not change the source video.
|
|
10
|
-
|
|
11
|
-
1. Inspect the named source project's `project.json`, `layers.json`, relevant scene code, captions, video cuts,
|
|
12
|
-
effects and audio settings. Read available conversation/history from this editing session. Do not claim access
|
|
13
|
-
to unavailable history. MCP file tools do not expose private chat state.
|
|
14
|
-
2. Extract supported rules. Consider speech cleanup (duplicate/repeated takes, filler words and pauses), B-roll
|
|
15
|
-
selection and placement, zoom emphasis, transitions, caption appearance, pacing, graphics and sound balance.
|
|
16
|
-
These are inspection topics, **not defaults**. Include only choices shown by the project or confirmed in history.
|
|
17
|
-
A cut timeline alone does not prove that filler words or duplicate takes were removed. Distinguish observed
|
|
18
|
-
settings from confirmed intent. Do not infer a fixed transition interval, such as five seconds, from an example.
|
|
19
|
-
3. Write a standalone reusable prompt. Include a short purpose, evidence-backed rules, inputs needed for another
|
|
20
|
-
video, review steps and limits/unknowns. Preserve exact settings where useful (caption fonts/colors/position,
|
|
21
|
-
audio levels, a built-in style ID); turn source timestamps into content-based placement rules only where supported.
|
|
22
|
-
If the evidence is too weak to identify an editing style, explain what is missing instead of inventing rules.
|
|
23
|
-
4. Require fresh content: inspect the new footage and transcript, choose relevant new B-roll, and create text,
|
|
24
|
-
animations and sound to fit it. Do not copy the source's scenes, footage, B-roll, transcript, names, personal facts
|
|
25
|
-
or fixed timeline positions. The saved prompt must work without access to the original project.
|
|
26
|
-
5. Call `agentcut_save_editing_style` with `name` (1–80 characters), `description` (1–500) and `prompt` (1–64,000).
|
|
27
|
-
The helper validates input, creates a unique folder (adds a number on a name collision), writes PROMPT.md then
|
|
28
|
-
style.json, and reads both back. The source timeline is unchanged. Never say a style is saved if this fails.
|
|
29
|
-
If the tool is unavailable but workspace disk access is available, create a new unique folder yourself; do not
|
|
30
|
-
overwrite an existing folder. Write the prompt first and the metadata last. With neither method, report the limit.
|
|
31
|
-
6. Read back both files, check for source-specific content and unsupported claims, and report the saved path plus
|
|
32
|
-
the main rules and any unknowns. The gallery discovers complete pairs under **Styles → Saved editing styles**.
|
|
33
|
-
Sending the request is not completion; the chat must report success or the actual failure.
|
|
34
|
-
|
|
35
|
-
```
|
|
36
|
-
library/editing-styles/<id>/
|
|
37
|
-
PROMPT.md standalone editing instructions, evidence notes and limits
|
|
38
|
-
style.json { "version": 1, "name": "My interview edits", "description": "A short summary." }
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
IDs use lowercase ASCII letters, digits and hyphens, start with a letter or digit and have at most 64 characters.
|
|
42
|
-
No copied scenes/assets, form fields, render or preview are needed. MCP reads use `scope: "library"` and
|
|
43
|
-
`path: "editing-styles/<id>/PROMPT.md"` (or `style.json`).
|
|
44
|
-
|
|
45
|
-
## Apply to another video
|
|
46
|
-
|
|
47
|
-
1. Read the named style's PROMPT.md. Inspect the **current target project**, its footage, transcript and audio.
|
|
48
|
-
The source project is not needed. The gallery's Apply to this video action edits the current project.
|
|
49
|
-
2. Use the saved rules with the new content. Obtain missing required footage or information before editing.
|
|
50
|
-
State rules that cannot apply. A style is not permission to invent a script or duplicate source content.
|
|
51
|
-
3. Make the actual timeline edits. A `project.json` style ID alone does not remove speech, choose B-roll or add
|
|
52
|
-
shot-level effects. Keep captions, source offsets, graphics and audio aligned when cutting or changing pacing.
|
|
53
|
-
Read `references/style-editing.md`, `format.md` and `sound.md` as needed for implementation and review.
|
|
54
|
-
4. Review frames, playback, captions and sound with the normal editing loop. Report changes and limits.
|
|
55
|
-
|
|
56
|
-
Existing video presets remain supported. Read `references/presets.md` for explicit scene/asset kit requests.
|
|
57
|
-
Do not convert or reinterpret existing `library/presets/` entries as editing-rule prompts.
|
|
1
|
+
# Reusable editing styles
|
|
2
|
+
|
|
3
|
+
An editing style is a named prompt that describes **how to edit different footage**. It is separate from
|
|
4
|
+
the built-in talking-head looks and the scene/asset kits in `library/presets/`.
|
|
5
|
+
|
|
6
|
+
## Save current style
|
|
7
|
+
|
|
8
|
+
The plus action beside Styles in chat, or Save current style in the gallery, sends a save request with a name.
|
|
9
|
+
Saving must not change the source video.
|
|
10
|
+
|
|
11
|
+
1. Inspect the named source project's `project.json`, `layers.json`, relevant scene code, captions, video cuts,
|
|
12
|
+
effects and audio settings. Read available conversation/history from this editing session. Do not claim access
|
|
13
|
+
to unavailable history. MCP file tools do not expose private chat state.
|
|
14
|
+
2. Extract supported rules. Consider speech cleanup (duplicate/repeated takes, filler words and pauses), B-roll
|
|
15
|
+
selection and placement, zoom emphasis, transitions, caption appearance, pacing, graphics and sound balance.
|
|
16
|
+
These are inspection topics, **not defaults**. Include only choices shown by the project or confirmed in history.
|
|
17
|
+
A cut timeline alone does not prove that filler words or duplicate takes were removed. Distinguish observed
|
|
18
|
+
settings from confirmed intent. Do not infer a fixed transition interval, such as five seconds, from an example.
|
|
19
|
+
3. Write a standalone reusable prompt. Include a short purpose, evidence-backed rules, inputs needed for another
|
|
20
|
+
video, review steps and limits/unknowns. Preserve exact settings where useful (caption fonts/colors/position,
|
|
21
|
+
audio levels, a built-in style ID); turn source timestamps into content-based placement rules only where supported.
|
|
22
|
+
If the evidence is too weak to identify an editing style, explain what is missing instead of inventing rules.
|
|
23
|
+
4. Require fresh content: inspect the new footage and transcript, choose relevant new B-roll, and create text,
|
|
24
|
+
animations and sound to fit it. Do not copy the source's scenes, footage, B-roll, transcript, names, personal facts
|
|
25
|
+
or fixed timeline positions. The saved prompt must work without access to the original project.
|
|
26
|
+
5. Call `agentcut_save_editing_style` with `name` (1–80 characters), `description` (1–500) and `prompt` (1–64,000).
|
|
27
|
+
The helper validates input, creates a unique folder (adds a number on a name collision), writes PROMPT.md then
|
|
28
|
+
style.json, and reads both back. The source timeline is unchanged. Never say a style is saved if this fails.
|
|
29
|
+
If the tool is unavailable but workspace disk access is available, create a new unique folder yourself; do not
|
|
30
|
+
overwrite an existing folder. Write the prompt first and the metadata last. With neither method, report the limit.
|
|
31
|
+
6. Read back both files, check for source-specific content and unsupported claims, and report the saved path plus
|
|
32
|
+
the main rules and any unknowns. The gallery discovers complete pairs under **Styles → Saved editing styles**.
|
|
33
|
+
Sending the request is not completion; the chat must report success or the actual failure.
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
library/editing-styles/<id>/
|
|
37
|
+
PROMPT.md standalone editing instructions, evidence notes and limits
|
|
38
|
+
style.json { "version": 1, "name": "My interview edits", "description": "A short summary." }
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
IDs use lowercase ASCII letters, digits and hyphens, start with a letter or digit and have at most 64 characters.
|
|
42
|
+
No copied scenes/assets, form fields, render or preview are needed. MCP reads use `scope: "library"` and
|
|
43
|
+
`path: "editing-styles/<id>/PROMPT.md"` (or `style.json`).
|
|
44
|
+
|
|
45
|
+
## Apply to another video
|
|
46
|
+
|
|
47
|
+
1. Read the named style's PROMPT.md. Inspect the **current target project**, its footage, transcript and audio.
|
|
48
|
+
The source project is not needed. The gallery's Apply to this video action edits the current project.
|
|
49
|
+
2. Use the saved rules with the new content. Obtain missing required footage or information before editing.
|
|
50
|
+
State rules that cannot apply. A style is not permission to invent a script or duplicate source content.
|
|
51
|
+
3. Make the actual timeline edits. A `project.json` style ID alone does not remove speech, choose B-roll or add
|
|
52
|
+
shot-level effects. Keep captions, source offsets, graphics and audio aligned when cutting or changing pacing.
|
|
53
|
+
Read `references/style-editing.md`, `format.md` and `sound.md` as needed for implementation and review.
|
|
54
|
+
4. Review frames, playback, captions and sound with the normal editing loop. Report changes and limits.
|
|
55
|
+
|
|
56
|
+
Existing video presets remain supported. Read `references/presets.md` for explicit scene/asset kit requests.
|
|
57
|
+
Do not convert or reinterpret existing `library/presets/` entries as editing-rule prompts.
|
|
@@ -1,34 +1,34 @@
|
|
|
1
|
-
# Feature Launch
|
|
2
|
-
|
|
3
|
-
Use this guide for the Feature Launch chat action or a request to announce one new feature or capability. Also read `product-launch.md` for brand, capture, visual, sound and final review standards. Feature Launch has its own brief and story; it is not a whole-product introduction or a step-by-step lesson.
|
|
4
|
-
|
|
5
|
-
## Identify the feature before work
|
|
6
|
-
|
|
7
|
-
For a bare request, ask which feature is new and what people can now do. A product URL or an old launch alone does not identify the feature. Ask locally before an agent run when possible. Do not scan other projects or shared libraries to guess. Preserve deliberate attachments, current brief, selected style and music. With supplied context, inspect it first and ask only for missing facts that affect the video.
|
|
8
|
-
|
|
9
|
-
Use the assigned canvas video. A populated source gets a separate target, timeline and chat; keep the source unchanged. Reuse a truly empty video. Explicit edits keep their target. This is the standard creative workflow, not the limited release-job API.
|
|
10
|
-
|
|
11
|
-
## Plan the story
|
|
12
|
-
|
|
13
|
-
Write the audience, one new benefit, one verified claim and a shot list in notes.md. Default flow:
|
|
14
|
-
|
|
15
|
-
1. **New benefit.** Open with what people can now do. Name the feature when it helps recognition.
|
|
16
|
-
2. **Feature in action.** Show a real action and its visible result, with enough context to understand what changed.
|
|
17
|
-
3. **Outcome.** Make the benefit visible. Use a supported before/after only when the evidence exists. Do not invent time savings, performance figures or customer claims.
|
|
18
|
-
4. **Next step.** End with one useful action: try the feature, open its location, or read the announcement. State verified availability or plan restrictions when relevant.
|
|
19
|
-
|
|
20
|
-
The problem statement is optional. Existing users often know the problem; do not delay the feature with a repeated product introduction. For a new audience, add only the context required to understand the benefit. Keep one main feature; do not turn the video into a feature list. Choose duration from the material and channel rather than a fixed formula. Respect requested length, aspect ratios, voice, captions and music.
|
|
21
|
-
|
|
22
|
-
For example, a canvas-versions announcement could show making two independent versions, then switching between their timelines and chats. The visible result supports “explore another version while keeping the original.” A How-to would instead explain each step needed to complete that task.
|
|
23
|
-
|
|
24
|
-
## Build and verify
|
|
25
|
-
|
|
26
|
-
Read `references/launch-direction.md` before building a new film or a major revision. Use its
|
|
27
|
-
concrete visual settings, shot table, early proof captures and transition checks with this feature's
|
|
28
|
-
brief. Keep an approved script or existing direction when the request is a small edit.
|
|
29
|
-
|
|
30
|
-
Follow the full Agentcut skill: inspect real assets and the component/3D libraries, plan intentional motion and camera changes, use editable tracks, coordinate music and sound effects, and retain final full-picture and audio review. Do not replace the process with a fixed animation recipe. Use the user's own footage or safe real-app capture. If proof or access is missing, ask for it before building a false demonstration.
|
|
31
|
-
|
|
32
|
-
Use `sound.md` for voice and music. Generic voice-over uses local Kokoro; a paid voice requires explicit user selection. A silent announcement is valid when requested. If voice is used, inspect the take, check its words and use transcription timings for accurate captions. Music must support the action and leave the message clear.
|
|
33
|
-
|
|
34
|
-
Before delivery, verify that viewers can identify the feature, understand its new benefit, see evidence in the actual demonstration, and know the next step. Check small-screen readability, output formats, timing, asset paths, picture and sound. Deliver the editable result only after the normal final review passes.
|
|
1
|
+
# Feature Launch
|
|
2
|
+
|
|
3
|
+
Use this guide for the Feature Launch chat action or a request to announce one new feature or capability. Also read `product-launch.md` for brand, capture, visual, sound and final review standards. Feature Launch has its own brief and story; it is not a whole-product introduction or a step-by-step lesson.
|
|
4
|
+
|
|
5
|
+
## Identify the feature before work
|
|
6
|
+
|
|
7
|
+
For a bare request, ask which feature is new and what people can now do. A product URL or an old launch alone does not identify the feature. Ask locally before an agent run when possible. Do not scan other projects or shared libraries to guess. Preserve deliberate attachments, current brief, selected style and music. With supplied context, inspect it first and ask only for missing facts that affect the video.
|
|
8
|
+
|
|
9
|
+
Use the assigned canvas video. A populated source gets a separate target, timeline and chat; keep the source unchanged. Reuse a truly empty video. Explicit edits keep their target. This is the standard creative workflow, not the limited release-job API.
|
|
10
|
+
|
|
11
|
+
## Plan the story
|
|
12
|
+
|
|
13
|
+
Write the audience, one new benefit, one verified claim and a shot list in notes.md. Default flow:
|
|
14
|
+
|
|
15
|
+
1. **New benefit.** Open with what people can now do. Name the feature when it helps recognition.
|
|
16
|
+
2. **Feature in action.** Show a real action and its visible result, with enough context to understand what changed.
|
|
17
|
+
3. **Outcome.** Make the benefit visible. Use a supported before/after only when the evidence exists. Do not invent time savings, performance figures or customer claims.
|
|
18
|
+
4. **Next step.** End with one useful action: try the feature, open its location, or read the announcement. State verified availability or plan restrictions when relevant.
|
|
19
|
+
|
|
20
|
+
The problem statement is optional. Existing users often know the problem; do not delay the feature with a repeated product introduction. For a new audience, add only the context required to understand the benefit. Keep one main feature; do not turn the video into a feature list. Choose duration from the material and channel rather than a fixed formula. Respect requested length, aspect ratios, voice, captions and music.
|
|
21
|
+
|
|
22
|
+
For example, a canvas-versions announcement could show making two independent versions, then switching between their timelines and chats. The visible result supports “explore another version while keeping the original.” A How-to would instead explain each step needed to complete that task.
|
|
23
|
+
|
|
24
|
+
## Build and verify
|
|
25
|
+
|
|
26
|
+
Read `references/launch-direction.md` before building a new film or a major revision. Use its
|
|
27
|
+
concrete visual settings, shot table, early proof captures and transition checks with this feature's
|
|
28
|
+
brief. Keep an approved script or existing direction when the request is a small edit.
|
|
29
|
+
|
|
30
|
+
Follow the full Agentcut skill: inspect real assets and the component/3D libraries, plan intentional motion and camera changes, use editable tracks, coordinate music and sound effects, and retain final full-picture and audio review. Do not replace the process with a fixed animation recipe. Use the user's own footage or safe real-app capture. If proof or access is missing, ask for it before building a false demonstration.
|
|
31
|
+
|
|
32
|
+
Use `sound.md` for voice and music. Generic voice-over uses local Kokoro; a paid voice requires explicit user selection. A silent announcement is valid when requested. If voice is used, inspect the take, check its words and use transcription timings for accurate captions. Music must support the action and leave the message clear.
|
|
33
|
+
|
|
34
|
+
Before delivery, verify that viewers can identify the feature, understand its new benefit, see evidence in the actual demonstration, and know the next step. Check small-screen readability, output formats, timing, asset paths, picture and sound. Deliver the editable result only after the normal final review passes.
|
|
@@ -1,72 +1,72 @@
|
|
|
1
|
-
# Footage sent from the editor
|
|
2
|
-
|
|
3
|
-
"Send to Agentcut" in the ScreenSlick editor renders the user's edit and opens it here as a new
|
|
4
|
-
project sized to the video:
|
|
5
|
-
|
|
6
|
-
- **Footage** track: one video clip `footage` with `src: "assets/footage.<ext>"`, `fit: "contain"`,
|
|
7
|
-
covering the whole project. Its audio is the user's voice and the editor mix.
|
|
8
|
-
- **Captions** track (when the edit had subtitles): one captions clip with the editor's words, timed in
|
|
9
|
-
frames. Restyle it with `style`; don't retype the words.
|
|
10
|
-
- `notes.md` says what came over.
|
|
11
|
-
|
|
12
|
-
The user finishes the video here: cuts, color, motion graphics, sound, then exports from the studio.
|
|
13
|
-
|
|
14
|
-
## Remove silences / tighten pacing
|
|
15
|
-
|
|
16
|
-
1. `agentcut_transcribe` on `assets/footage.<ext>` for word timings (or
|
|
17
|
-
`agentcut_analyze_audio` for per-frame energy when there is no speech).
|
|
18
|
-
2. Find gaps longer than ~0.6 s between words (keep ~0.15 s of air before and after each word; never cut
|
|
19
|
-
inside a word). Keep breaths that land on a beat or a reveal.
|
|
20
|
-
3. Replace the single footage clip with one clip per kept range, back to back on the Footage track:
|
|
21
|
-
each clip has `src` of the footage, `trimStart` = range start (frames in the file), `from` = where it
|
|
22
|
-
lands on the timeline, `duration` = range length. Give them ids `footage-1`, `footage-2`, …
|
|
23
|
-
4. Move every caption word with its range (subtract the time removed before it), drop words in removed
|
|
24
|
-
ranges, and set the project `durationInFrames` to the new end.
|
|
25
|
-
5. Tell the user how much you cut ("removed 14 pauses, 0:52 → 0:41"), then check the cut points with
|
|
26
|
-
`agentcut_capture_frames` and `agentcut_listen_critique`.
|
|
27
|
-
|
|
28
|
-
Cuts "by transcript" ("remove the part where I say …") work the same way: find the words, cut their range.
|
|
29
|
-
|
|
30
|
-
## Color
|
|
31
|
-
|
|
32
|
-
Read `references/color.md`. Measure with `agentcut_color_check`, even out shots with `agentcut_match_shots`,
|
|
33
|
-
then put one look over the whole video (`grade` in `project.json`). Check before and after.
|
|
34
|
-
|
|
35
|
-
## Motion graphics over footage
|
|
36
|
-
|
|
37
|
-
Add tracks above Footage (text, scenes, images) and keep the footage readable: lower thirds and callouts
|
|
38
|
-
at the edges, punch-in zooms by splitting the footage and giving that piece a bigger `box`, never covering
|
|
39
|
-
the speaker's face for long.
|
|
40
|
-
|
|
41
|
-
## Raw takes
|
|
42
|
-
|
|
43
|
-
"Send to Agentcut → Raw takes" sends the untouched recordings instead of a render. The project is
|
|
44
|
-
sized to the screen recording:
|
|
45
|
-
|
|
46
|
-
- **Screen** track: one clip per take (`screen`, or `screen-1`, `screen-2`, … back to back), `src:
|
|
47
|
-
"assets/screen.<ext>"`, `fit: "contain"`. Its audio is the user's voice: the only audio in the project.
|
|
48
|
-
- **Camera** track (when they recorded one): clip `camera`, `src: "assets/camera.<ext>"`, `fit: "cover"`,
|
|
49
|
-
a `box` where the editor showed it and a `radius` for its rounded corners. It is `muted` (the voice is on
|
|
50
|
-
the screen file) and already synced: its `from`/`trimStart` line it up with the screen. Keep it muted.
|
|
51
|
-
- **Captions** track (when the editor had subtitles): words timed to the raw recording.
|
|
52
|
-
- **Cursor** (Companion recordings): `assets/screen.cursor.json` with the mouse path, clicks and scrolls,
|
|
53
|
-
and a `cursor` field on the screen clip that draws the pointer. Copy that field to every piece you cut.
|
|
54
|
-
See `references/cursor.md`; it also finds zoom, cut and speed-up candidates for step 1.
|
|
55
|
-
- `notes.md` lists the files and whether the user had the camera mirrored.
|
|
56
|
-
|
|
57
|
-
Nothing is cut yet, so a raw take is usually long. Ask what the video is for when it isn't clear, then:
|
|
58
|
-
|
|
59
|
-
1. **Cut both tracks together.** Work out the kept ranges on the screen take (silences, retakes, "by
|
|
60
|
-
transcript" cuts, as above). For every range, add a screen piece *and* a camera piece with the same
|
|
61
|
-
`from` and `duration`. With the range start `R` in frames on the *original* timeline, the screen
|
|
62
|
-
piece's `trimStart` is `R` − its take's original `from`, and the camera piece's `trimStart` is
|
|
63
|
-
`R` − camera's original `from` + camera's original `trimStart` (skip camera pieces where that is
|
|
64
|
-
negative: the camera wasn't rolling yet). Ids: `screen-1…`, `camera-1…`. Move the captions with the cuts.
|
|
65
|
-
Spot-check sync after cutting with `agentcut_capture_frames` (lips vs. the voice).
|
|
66
|
-
2. **Frame the screen.** A `box` is fixed for the whole clip, so a zoom is a cut: split the screen piece
|
|
67
|
-
where the action starts and give that piece a bigger box (width/height 1.5–2, x/y negative to keep the
|
|
68
|
-
area of interest in frame), then cut back. Hold each zoom long enough to read.
|
|
69
|
-
3. **Place the camera.** Bubble in a corner (keep `radius` at half the short side for a circle), full frame
|
|
70
|
-
for an intro or outro (camera `box` to the whole frame; the Camera track sits above Screen), or
|
|
71
|
-
side by side (shrink the screen `box`, give the camera the rest). Change layouts at cuts, not mid-sentence.
|
|
72
|
-
4. Then grade, captions, music and motion graphics as for any footage.
|
|
1
|
+
# Footage sent from the editor
|
|
2
|
+
|
|
3
|
+
"Send to Agentcut" in the ScreenSlick editor renders the user's edit and opens it here as a new
|
|
4
|
+
project sized to the video:
|
|
5
|
+
|
|
6
|
+
- **Footage** track: one video clip `footage` with `src: "assets/footage.<ext>"`, `fit: "contain"`,
|
|
7
|
+
covering the whole project. Its audio is the user's voice and the editor mix.
|
|
8
|
+
- **Captions** track (when the edit had subtitles): one captions clip with the editor's words, timed in
|
|
9
|
+
frames. Restyle it with `style`; don't retype the words.
|
|
10
|
+
- `notes.md` says what came over.
|
|
11
|
+
|
|
12
|
+
The user finishes the video here: cuts, color, motion graphics, sound, then exports from the studio.
|
|
13
|
+
|
|
14
|
+
## Remove silences / tighten pacing
|
|
15
|
+
|
|
16
|
+
1. `agentcut_transcribe` on `assets/footage.<ext>` for word timings (or
|
|
17
|
+
`agentcut_analyze_audio` for per-frame energy when there is no speech).
|
|
18
|
+
2. Find gaps longer than ~0.6 s between words (keep ~0.15 s of air before and after each word; never cut
|
|
19
|
+
inside a word). Keep breaths that land on a beat or a reveal.
|
|
20
|
+
3. Replace the single footage clip with one clip per kept range, back to back on the Footage track:
|
|
21
|
+
each clip has `src` of the footage, `trimStart` = range start (frames in the file), `from` = where it
|
|
22
|
+
lands on the timeline, `duration` = range length. Give them ids `footage-1`, `footage-2`, …
|
|
23
|
+
4. Move every caption word with its range (subtract the time removed before it), drop words in removed
|
|
24
|
+
ranges, and set the project `durationInFrames` to the new end.
|
|
25
|
+
5. Tell the user how much you cut ("removed 14 pauses, 0:52 → 0:41"), then check the cut points with
|
|
26
|
+
`agentcut_capture_frames` and `agentcut_listen_critique`.
|
|
27
|
+
|
|
28
|
+
Cuts "by transcript" ("remove the part where I say …") work the same way: find the words, cut their range.
|
|
29
|
+
|
|
30
|
+
## Color
|
|
31
|
+
|
|
32
|
+
Read `references/color.md`. Measure with `agentcut_color_check`, even out shots with `agentcut_match_shots`,
|
|
33
|
+
then put one look over the whole video (`grade` in `project.json`). Check before and after.
|
|
34
|
+
|
|
35
|
+
## Motion graphics over footage
|
|
36
|
+
|
|
37
|
+
Add tracks above Footage (text, scenes, images) and keep the footage readable: lower thirds and callouts
|
|
38
|
+
at the edges, punch-in zooms by splitting the footage and giving that piece a bigger `box`, never covering
|
|
39
|
+
the speaker's face for long.
|
|
40
|
+
|
|
41
|
+
## Raw takes
|
|
42
|
+
|
|
43
|
+
"Send to Agentcut → Raw takes" sends the untouched recordings instead of a render. The project is
|
|
44
|
+
sized to the screen recording:
|
|
45
|
+
|
|
46
|
+
- **Screen** track: one clip per take (`screen`, or `screen-1`, `screen-2`, … back to back), `src:
|
|
47
|
+
"assets/screen.<ext>"`, `fit: "contain"`. Its audio is the user's voice: the only audio in the project.
|
|
48
|
+
- **Camera** track (when they recorded one): clip `camera`, `src: "assets/camera.<ext>"`, `fit: "cover"`,
|
|
49
|
+
a `box` where the editor showed it and a `radius` for its rounded corners. It is `muted` (the voice is on
|
|
50
|
+
the screen file) and already synced: its `from`/`trimStart` line it up with the screen. Keep it muted.
|
|
51
|
+
- **Captions** track (when the editor had subtitles): words timed to the raw recording.
|
|
52
|
+
- **Cursor** (Companion recordings): `assets/screen.cursor.json` with the mouse path, clicks and scrolls,
|
|
53
|
+
and a `cursor` field on the screen clip that draws the pointer. Copy that field to every piece you cut.
|
|
54
|
+
See `references/cursor.md`; it also finds zoom, cut and speed-up candidates for step 1.
|
|
55
|
+
- `notes.md` lists the files and whether the user had the camera mirrored.
|
|
56
|
+
|
|
57
|
+
Nothing is cut yet, so a raw take is usually long. Ask what the video is for when it isn't clear, then:
|
|
58
|
+
|
|
59
|
+
1. **Cut both tracks together.** Work out the kept ranges on the screen take (silences, retakes, "by
|
|
60
|
+
transcript" cuts, as above). For every range, add a screen piece *and* a camera piece with the same
|
|
61
|
+
`from` and `duration`. With the range start `R` in frames on the *original* timeline, the screen
|
|
62
|
+
piece's `trimStart` is `R` − its take's original `from`, and the camera piece's `trimStart` is
|
|
63
|
+
`R` − camera's original `from` + camera's original `trimStart` (skip camera pieces where that is
|
|
64
|
+
negative: the camera wasn't rolling yet). Ids: `screen-1…`, `camera-1…`. Move the captions with the cuts.
|
|
65
|
+
Spot-check sync after cutting with `agentcut_capture_frames` (lips vs. the voice).
|
|
66
|
+
2. **Frame the screen.** A `box` is fixed for the whole clip, so a zoom is a cut: split the screen piece
|
|
67
|
+
where the action starts and give that piece a bigger box (width/height 1.5–2, x/y negative to keep the
|
|
68
|
+
area of interest in frame), then cut back. Hold each zoom long enough to read.
|
|
69
|
+
3. **Place the camera.** Bubble in a corner (keep `radius` at half the short side for a circle), full frame
|
|
70
|
+
for an intro or outro (camera `box` to the whole frame; the Camera track sits above Screen), or
|
|
71
|
+
side by side (shrink the screen `box`, give the camera the rest). Change layouts at cuts, not mid-sentence.
|
|
72
|
+
4. Then grade, captions, music and motion graphics as for any footage.
|