mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-08-31 02:41:44 +00:00
* docs(audio): document the audio effects system The effects feature had no documentation at all — the only mentions anywhere in docs/ were changelog entries. This adds the three pages the color-grading feature already has, one per audience, and closes a gap in the existing audio guide. - prompting/audio-effects — a new Level 5 chapter on asking for a mix in symptoms rather than in filters, with the voiceover carve as the headline, the level-before-depth check, groups, and the three requests that have no honest answer (de-essing, noise removal, tone matching). - studio/audio-effects — the rack, presets by symptom, the carve module, groups, the deliberately asymmetric mute/solo, automation lanes, and troubleshooting. - reference/audio-effects — the contract: all four attributes, every effect and parameter range, why some parameters cannot be automated, the 19 presets, the five jobs and five one-knob profiles, carve semantics, the group model, the render bus, preview/render parity, and the three lint rules. Also points the existing "duck music under important speech" advice in guides/voice-and-audio at the carve, which does that properly and was never named there. Facts verified against source rather than the shipped skill prose: the panel section is "Audio FX" (the neighbouring "Effects" section is visual effects, and an earlier draft of this page named the wrong one), MAX_AUTOMATION_POINTS is 512, fromPreset carries a preset id rather than a boolean, the leveller targets the track's own 80th percentile, group mute reaches the render while solo never leaves Studio, and the CLI carve currently writes clip ids. No screenshots in this pass, and no placeholders for them either — the pages carry concrete markup and tables instead. Screenshots of the rack, the carve module, and a group row would each earn their place later. mint validate and mint broken-links both pass. * docs(audio): give audio its own Studio group, split by task Review feedback: the audio page did not belong in Studio / Edit. That group is already one task per page — canvas, timeline, animation, captions — and a single page covering the rack, the carve, groups, and automation lanes was four tasks bundled together and dropped in beside them. Studio now has an Audio group holding four task pages: - Effects and presets — the rack, presets by symptom, adding single effects in a working order, the one-knob controls, Even Out Levels - Voiceover carve — its own page, because it is the feature people come for - Groups, mute, and solo — including why mute reaches the export and solo cannot - Automation lanes — drawing envelopes, the shape menu, and which parameters cannot move at all Not a new top-level tab: the tabs here are audience-scoped (Guides, Studio, Catalog, Developers), so a feature tab would be the only one of its kind and would strand the prompting chapter out of its Level 5 sequence and the reference page out of Developers. Repointed the deep link in guides/voice-and-audio at the carve's own page. Lane interactions verified in source before documenting: the right-click menu offers Ramp up, Ramp down, Swell, Dip, and Simplify (which needs three points). Deliberately not documented: "clicking a lane label reveals it in the rack", which is not on main. mint validate and mint broken-links both pass. * docs(audio): fix the four review blockers All four verified in source before fixing; the review was right on every count. **The registry was incomplete.** `pitchshift` ships at `audioFx.ts:509-535` (`semitones` −12–12, `mix` 0–1, worklet-backed so neither automatable) and was missing entirely — sixteen effects, not fifteen. It also joins the worklet list, so five effects expose no automatable parameters rather than four. **Three presets were missing.** `chipmunk`, `giant`, and `monster` ship at `audioFxPresets.ts:336-357`, all built on `pitchshift`. Twenty-two presets, and Character holds ten. Fixed in both the reference table and the Studio list. **The copyable markup contradicted the warning above it.** The page said `carve.mjs` only finds double-quoted attributes and then gave three single-quoted examples — copying the chain example would make a later carve miss the existing chain and overwrite it. All three are now double-quoted with `"`, each followed by its unescaped reading so it stays legible. **The attribute table over-claimed.** `data-audio-group` is a plain id, not JSON, and is ignored on `<video>`; the other three also live on `<hf-audio-group>` for a group. The table now carries shape and valid host per attribute. **The automation contract was wrong on two axes.** A clip lane's `t` is clip-relative but a GROUP lane's is composition time, because a group has no `data-start` (`webAudioTransport.ts:337-342`, `audioMixer.ts:1311-1344`) — both pages now split the two clocks. And `volume` is not 0–1: the ceiling is `MAX_AUDIO_GAIN`, +12 dB or about 3.981 (`audioGain.ts:8-9`), so a boosting lane is valid and documented. **Current-main drift.** #3416 is merged, so the CLI now records the voices' shared group when it is safe and falls back to clip ids when that group contains the bed or a music/SFX member. Documented, including why neither refusal shows up on the run that writes it, and rebased onto main. mint validate and mint broken-links both pass. * docs(audio): name the real add-menu family, and finish propagating pitchshift Second review round. All three findings were my own incomplete propagation — I corrected the reference for `pitchshift` last round and left the reader-facing pages behind it. **The add-menu family is `Time`, not `Space`.** `propertyPanelFxAddMenu.tsx:22-28` labels the four groups Filters / Dynamics / Non-linear / Time, and the time group holds pitchshift, delay, chorus, phaser, and reverb. The Studio page sent readers looking for a group that does not exist. It is now a table naming the family and its contents, and the reference's "Time — space and width" heading is retitled, since that description stopped covering the family the moment pitch shift joined it. Also from the same file: the menu offers the named jobs in place of a bare `peaking`, because picking `peaking` is picking a machine and leaving the real decision — which range — for afterwards. Worth saying on the task page. **Pitch shift was missing from both no-automation lists** that a reader actually follows — `studio/audio-automation` and, unflagged but the same defect, the prompting chapter. Five worklet effects in all four places now. Called out explicitly on the Studio page, because a rising pitch is exactly the thing someone reaches for a lane to do, and the lane will not report that it cannot. **Narrowed the group-metadata sentence.** "The other three are JSON, and on a group they live on `<hf-audio-group>`" swept in `data-fx-carve`, contradicting the table directly above it. Only `data-fx-chain` and `data-automation` are group metadata. mint validate and mint broken-links both pass.
106 lines
4.4 KiB
Plaintext
106 lines
4.4 KiB
Plaintext
---
|
|
title: "Group tracks, mute, and solo"
|
|
sidebarTitle: "Groups, mute, and solo"
|
|
description: "Give several audio clips one set of effects, one fader, and one mute — and know which of mute and solo reaches the export."
|
|
---
|
|
|
|
Five narration clips usually want one set of effects, one fader, and one mute —
|
|
not five copies that drift apart as you edit. A group gives them that: its members
|
|
sum through a single bus, and the bus carries the group's own volume, effects, and
|
|
automation.
|
|
|
|
## When to use a group
|
|
|
|
- **Narration in several clips.** One rack for the whole voice, and one thing for
|
|
a [carve](/studio/voiceover-carve) to point at.
|
|
- **More than a couple of sound effects.** One place to turn all of them down is
|
|
worth more than precise individual levels you will never revisit.
|
|
- **Anything you want to mute as a unit** — an ambience layer, a music stem.
|
|
|
|
A single clip does not need a group. Its own rack is already one place.
|
|
|
|
## Create a group
|
|
|
|
On an audio track holding more than one ungrouped clip, the **FX** button offers
|
|
to group them first: it reads "Group these clips to add effects to all of them".
|
|
Choose **Group**.
|
|
|
|
Studio creates a group behind those clips and points anything that needed it — a
|
|
carve, for instance — at the group rather than at the individual clip ids.
|
|
|
|
## Read a group row
|
|
|
|
A group gets its own timeline row, carrying:
|
|
|
|
| Control | Does |
|
|
| --- | --- |
|
|
| Caret | Shows or hides the member rows beneath it |
|
|
| `▤` and name | The group glyph and its label |
|
|
| Count | How many members it holds |
|
|
| Mute | Silences every member at once |
|
|
| **Hear only this** | Solo — listens to this group while you work |
|
|
| **FX** | Opens the group's own rack, applying to the summed bus |
|
|
| `∿` | Shows or hides [the group's own automation lanes](/studio/audio-automation) |
|
|
|
|
The caret and the `∿` toggle are independent: showing a group's members does not
|
|
open their automation lanes, and opening the group's lanes does not expand its
|
|
members.
|
|
|
|
A group-level effect hears the **sum** of its members, not each one separately.
|
|
That is the point of a bus — one compressor across a whole voiceover behaves
|
|
differently from five compressors on five clips, and usually better.
|
|
|
|
## Mute and solo are not symmetric
|
|
|
|
This is the part worth remembering:
|
|
|
|
| Control | What it does | In the export |
|
|
| --- | --- | --- |
|
|
| Mute | Silences a clip or a whole group | **Included** — muted audio is dropped from the render |
|
|
| **Hear only this** | Listens to one thing while you work | **Ignored** — solo never reaches the render |
|
|
|
|
So **mute is a mix decision and solo is a listening tool**. You can leave a solo
|
|
active, render, and get the full mix — which is deliberate, because a forgotten
|
|
solo silently shipping a one-track export would be much worse.
|
|
|
|
A group that is not soloed while one of its members is appears **half-lit**: the
|
|
display-only signal that some of what is under it still plays.
|
|
|
|
## Membership lives on the member
|
|
|
|
Worth knowing because it explains most surprises: each clip records which group it
|
|
belongs to, rather than the group listing its members. Delete a clip and it simply
|
|
disappears from the group; nothing dangles.
|
|
|
|
Groups are **audio only** and do not nest. A group marker on a video clip is
|
|
ignored.
|
|
|
|
## What should happen
|
|
|
|
- The group row appears with the members collapsed beneath it, and the
|
|
grouping offer disappears from that track's **FX** button.
|
|
- Effects added to the group apply to everything under it at once.
|
|
- Muting the group silences all members, in preview and in the render.
|
|
|
|
## Common problems
|
|
|
|
**The group's effects do nothing.** Check that the members actually carry the
|
|
group, rather than that the group appears to list them.
|
|
|
|
**Nothing happened when I grouped clips.** Grouping resolves the clips it was
|
|
given against the timeline's current rows. If the track is collapsed, or its clips
|
|
live inside a nested composition, expand it and try again.
|
|
|
|
**Clips inside a nested composition are not offered grouping.** They arrive as
|
|
separate rows rather than as one track holding several clips, so the grouping
|
|
offer does not appear. Group them in the composition that owns them.
|
|
|
|
**A soloed track was missing from the export.** It was not — solo cannot affect a
|
|
render. Look for a mute.
|
|
|
|
## Related topics
|
|
|
|
- [Make music sit under narration](/studio/voiceover-carve)
|
|
- [Automate a parameter over time](/studio/audio-automation)
|
|
- [Audio effects implementation](/reference/audio-effects#groups-mute-and-solo)
|