Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions skills/raea/motion/delivery.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@
`raea check out/launch-9x16.mp4 --manifest out/render.json --shape 9:16 --platform tiktok`.
- Captions: burn them in for feeds that play without sound, unless the delivery controller says captions off; then
burn none, and leave the words file beside the export for the platform's own captions.
- Sound to -14 LUFS integrated with true peak at or below -1 dBTP: one `<Mix lufs={-14} ceiling={-1.5} />` per
composition does it (`motion/sound`). A spec that names another number wins.
- Sound to -14 LUFS integrated with true peak at or below -1 dBTP: raea's mix and master do it on every render
(`motion/sound`). A spec that names another number wins: `<Mix lufs={…} ceiling={…} />` sets it.
- Render the export at `--quality master` (motion graphics and type) or `--quality high` (a film), and versions made
for notes with no `--quality` flag; name it in lowercase letters, digits and hyphens, with its shape and length:
`spring-launch-9x16-15s.mp4`. Each version is a new file beside the last, never written over it.
Expand Down
17 changes: 12 additions & 5 deletions skills/raea/motion/rendering.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,10 @@
It measures clipped text, text under a platform's buttons, text over the face, captions on too briefly to read,
caption contrast against the pixels behind them, frozen stretches, flashing past the limit, cues that miss their word, loudness, a sound that
stops dead or (with `--words`) fights the voice, and encoder blotching in the darks. Each finding is ranked P0 to P3
with its fix; it exits 1 while a P0 or P1 stands, and `-o check.json` writes them for the critique. An
with its fix; it exits 1 while a P0 or P1 stands, and `-o check.json` writes them for the critique. Fix every error
in one pass before rendering again. A finding that ends `[also in …]` was in the earlier export too: what you changed
didn't move it, so don't repeat that change; try another, or say why it stands. A note is for the person, not a
reason to render again. An
exception in the composition (an unclamped value going NaN, keyframes out of order, a phrase `word()` can't find, a
missing prop) fails the render and names the line.
- **Watch it as a viewer would once the piece is close.** `raea check` measures; it can't judge a frame cropped too
Expand All @@ -21,7 +24,10 @@
- **Without `--manifest`**, `raea render` writes the export alone, without the measurements `raea check` reads. Render
another deliverable from its own file the same way (`raea render NAME.tsx -o NAME.mp4 --manifest NAME.json`) and
check it.
- **Loudness** comes out at -14 LUFS integrated (±1) with true peak at or below -1 dBTP when `<Mix>` is in the tree.
- **Loudness** comes out at -14 LUFS integrated (±1) with true peak at or below -1 dBTP: raea levels each line of
dialogue (the `voice` bus, or footage on no bus) to the same loudness and masters the piece, so don't measure lines
or set `gainDb` to level them, and don't master the voice outside raea. `gainDb` is for a deliberate change, on top
of raea's level. `<Mix lufs={…} ceiling={…}>` sets another target.

## Why

Expand All @@ -45,9 +51,10 @@ looking again, finds more than a still per change and costs less.
A video's bitrate follows its size and frame rate (about 20 Mbit/s at 1080p30, 80 at 4K30; VideoToolbox spends less on
flat pictures), and `--kbps N` sets it. `--quality draft|high|master` (or 0..1: 0.6, 0.85, 0.95) asks for constant
quality instead, each frame getting the bits it needs: `master` keeps thin type and hard vector edges clean at 4K
(about 31 Mbit/s on flat motion graphics). Blotching in dark areas is the encoder, not the composition: export dark
material as PNG frames (`RAEA_READBACK=rgba raea render piece.tsx -o piece.frames/`) and encode them with more bits for
the darks. A `NAME.frames/` folder is never committed, and raea's storage dry run lists it a day after
(about 31 Mbit/s on flat motion graphics). Blotching in dark areas is the encoder's or the footage's own, and on a
render made in a project `raea check` says which: the footage's is a note to pass on, never a reason to render again;
for the encode's, render with `--quality master`. Dark material can also go out as PNG frames
(`RAEA_READBACK=rgba raea render piece.tsx -o piece.frames/`). A `NAME.frames/` folder is never committed, and raea's storage dry run lists it a day after
the render unless something names it.

Which to ask for. A version made for notes (a cut to review, a shot that will be joined, a preview) takes no
Expand Down
10 changes: 6 additions & 4 deletions skills/raea/motion/sound.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,11 +36,14 @@
- Narration over the picture, when the footage has no voice for it, is
`<Speech text="the words" start={frame} />` from `raea/speech` (Pocket TTS, on this computer; `voice` picks a
Pocket voice or a WAV of one).
- Master the sum with one `<Mix lufs={-14} ceiling={-1.5} />` per composition. It brings the whole mix to -14 LUFS
integrated and limits true peaks under the ceiling, which is what the floor's loudness defect asks for.
- raea mixes and masters every render: each line of dialogue (the `voice` bus, or footage on no bus) comes to the same
loudness, a join into dead silence gets the room's tone, and the whole mix comes to -14 LUFS integrated with true
peaks under -1 dBTP, which is what the floor's loudness defect asks for. Don't level lines with `gainDb` or master
the voice outside raea. One `<Mix lufs={…} ceiling={…} />` per composition sets another target.
- Put the sounds in the tree in time order. The engine keys a sound's stretch by its place in the tree, so adding a
sound in the middle of the list can split the ones after it.
- Balance relative to the voice. The approved pieces, mastered by `<Mix>` to -14 LUFS, sit like this:
- Balance relative to the voice. The approved pieces, mastered to -14 LUFS, sit like this (each a `gainDb` on top of
raea's level for the voice, or on the sound's own level for the rest):

| sound | with a voice | without one (promo, deck, game) |
|---|---|---|
Expand Down Expand Up @@ -110,7 +113,6 @@ ends up shouting over the narrator while another is inaudible.
- `loop` on an `<Audio>` without `endAt` to stretch a short ambience: nothing loops, it plays once and stops dead
(the render warns). With `endAt` it repeats with a hard jump at each loop; tile copies with crossfades instead.
- Two `<Mix>` in one composition: it throws.
- No `<Mix>`: the sum plays as it is, at whatever loudness it adds up to.
- Rewording a `sao()` prompt on every pass. Each new prompt makes a new sound.
- `style` on an `<Audio>`: Audio has no picture and takes no style.
- Hand-placing dozens of game sounds from a log. Cue them from `useGameEvents` (`motion/games`).
Expand Down