Communitygithub.com

HyperFrames 音频处理

用于处理已放置在 HyperFrames 合成中的音频混合:淡入/淡出、交叉淡化、音轨增益或音量、音量自动化、闪避、音乐背景与旁白竞争(旁白雕刻)、音轨效果(EQ、压缩器、限制器、门限、饱和、延迟、混响、合唱、移相器、比特压缩)、在音轨音量或任何效果参数上绘制的自动化包络,或一个子混音总线为多个音轨同时承载链、推子和自动化时钟(`<hf-audio-group>`)。

HyperFrames 音频处理 是什么?

HyperFrames 音频混合技能专注于解决已放置的音频轨道之间的冲突关系,而非简单的处理堆叠。它提供了一套完整的工具,包括淡入/淡出、交叉淡化、音轨增益/音量、音量自动化、闪避、旁白雕刻,以及一个完整的音轨效果链(EQ、压缩器、限制器、门限、饱和、延迟、混响、合唱、移相器、比特压缩)。核心原则是使用单一实现确保预览和渲染结果一致,从而避免重复调试。该技能通过 `data-fx-chain`、`data-automation` 和 `data-fx-carve` 三个属性在 HTML 元素上管理所有音频处理,并支持 `<hf-audio-group>` 子混音总线同时对多个音轨应用链、推子和自动化时钟。它不涉及音频源搜索、生成或预处理(这些由 `/media-use` 处理),也不处理片段时间轴或布局(这些由 `/hyperframes-core` 处理)。对于旁白雕刻,技能要求将所有旁白片段分组,然后对音乐背景轨道应用雕刻,以避免音频组随时间变化导致的隐蔽错误。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/1999AZZAR/designer-mcp/tree/HEAD/skills/video/engine/hyperframes-audio

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

HyperFrames 音频

混音是一组关系,而非一堆处理器。两个听起来独立的轨道放在一起可能无法入耳,解决方案很少是“调低一个”——而是找出它们在争夺什么,并将其交给需要的一方。这里的每一个工具都是为了表达其中一种关系而存在。

效果位于元素上的 data-fx-chain 中,预览和渲染通过相同的Web Audio图运行——在实时上下文中是工作室,在无头浏览器中则是离线引擎。每个效果只有一种实现,因此你在拖动时听到的就是最终写入的内容。你永远不需要调整两次。

片段时间轴仍由 /hyperframes-core 处理:音频/视频的修剪和源范围使用 data-start、data-duration 和 data-media-start,交叉淡化则重叠不同轨道上的片段。本技能负责已放置轨道的淡入/淡出、交叉淡化包络、音轨增益/音量、音量与效果自动化、闪避/旁白雕刻以及效果链。/media-use 负责素材搜索、生成和预处理。

常量 data-playback-rate(范围为 0.1..10)在匹配的音频/视频元素使用相同的时间、源偏移和速率时,对画面和音高保持的渲染是安全的。速度渐变是 data-automation 中的一个 rate 通道(参见 docs/reference/speed-ramps),它覆盖常量值,并在预览和渲染中保持音高。HyperFrames 不提供自动波形同步或漂移校正。关于可复制的剪切/交叉淡化/重新定时配方,请使用 /hyperframes-core → references/creator-editing-recipes.md。

三个属性承载所有内容,位于音频/视频元素本身——或者,对于前两个属性,位于 <hf-audio-group> 总线上(参见“一个总线处理多个轨道”):

属性作用
data-fx-chain效果,按信号顺序排列
data-automation此轨道音量或其效果参数上的包络
data-fx-carve雕刻自身的设置,以便可以重新推导

随附的效果系列包括:增益、EQ(高通、低通、峰值、搁架)、压缩器、限制器、门限、饱和、延迟、混响、合唱、移相器和比特压缩。

每个效果的精确JSON以及通道必须满足的规则:references/attributes.md。 每个效果及其参数、范围和单位:references/fx-registry.md。 如何处理无法听到的文件问题:references/diagnosis.md。 预设、命名任务和单旋钮配置文件,以及症状到修复的对照表:references/presets.md —— 在手动构建链之前请阅读该文件,因为其中一个预设或命名任务通常已经命名了问题。

各部分如何协同

两个创作界面写入这些属性;两个运行时通过相同的构建器读取它们。这种共享的中间层使预览能够预测渲染结果。

flowchart TB
  voice["语音轨道<br/>媒体文件"]
  bed["音乐背景<br/>媒体文件"]

  subgraph AUTHOR["创作 — 唯一写入属性的地方"]
    panel["工作室<br/>旁白雕刻控制"]
    script["scripts/carve.mjs<br/>检测配对,默认动态"]
    analysis["core/audioCarve.ts<br/>carveProfile · analyseCarveBands<br/>analyseCarveDuck · analyseCarveDynamics"]
    panel --> analysis
    script --> analysis
  end

  voice --> analysis
  bed --> analysis

  subgraph ATTRS["写入背景元素上的属性"]
    carveAttr["data-fx-carve<br/>源 · 强度 · 动态"]
    chainAttr["data-fx-chain<br/>峰值 xN + 增益,标记为 fromCarve"]
    autoAttr["data-automation<br/>每个雕刻参数一个通道"]
  end

  analysis --> carveAttr
  analysis --> chainAttr
  analysis --> autoAttr

  subgraph SHARED["一种实现,两者都读取"]
    build["audioFxGraph.ts · buildFxChain"]
    sched["audioFxAutomation.ts · scheduleChainAutomation"]
  end

  chainAttr --> build
  autoAttr --> sched

  build --> preview["预览<br/>实时 AudioContext<br/>attachElementFxChain"]
  sched --> preview
  build --> render["渲染<br/>无头浏览器中的 OfflineAudioContext<br/>applyAudioFxChain"]
  sched --> render

  preview --> heard["拖动时听到的声音"]
  render --> wav["处理后的 WAV<br/>+ chainTailSeconds 确保混音让尾部通过"]
  wav --> mix["引擎 · audioMixer<br/>音量通道在此处混入 PCM,而非在图谱中"]
  mix --> out["渲染的混音"]

  edit["在播放中编辑属性"] -.->|MutationObserver| preview

雕刻自身的设置永远不会在播放时读取——它生成的链和通道才是播放的内容。data-fx-carve 存在的意义是,强度可以在现有雕刻上更改,而无需从滤波器中反向猜测。

在雕刻的背景内部,信号首先经过衰减,然后是电平匹配,然后是任何你自己构建的内容——这就是为什么你添加的限制器仍然作为最后的限制器起作用:

flowchart LR
  src["解码的背景"] --> p1["峰值<br/>400 Hz"]
  p1 --> p2["峰值<br/>1 kHz"]
  p2 --> p3["峰值<br/>1.6 kHz"]
  p3 --> g["增益<br/>电平匹配"]
  g --> hand["你自己的效果<br/>例如 限制器"]
  hand --> dest["轨道增益,然后输出"]

  l1["通道 fx.n1.gain"] -.->|"语音在该频段
电平的包络"| p1
  l4["通道 fx.n4.gain"] -.->|"背景整体
闪避的程度"| g

静态雕刻是具有固定值且没有通道的相同图谱。

首先,找出问题所在

下表从“听起来有轰鸣声”开始——这假定有人听过并这么说了。如果给你一个文件并说“修复它”,你没有听到,也无法听到,所以你只能测量。有一条规则适用于所有情况:

单个未知声音的绝对频谱无法诊断。 共振峰为 ±10 dB,基频在 85–255 Hz 之间,句子在结尾时下降 5–6 dB。每一个单独来看都像是缺陷,而每一个都是说话者本身。

所以进行比较,并且要与同一文件内的某个参考进行比较:如果存在,则使用干净的原版;否则使用停顿(句间空白)——凡是间隙中可听见的内容都是附加的,而间隙的频谱是通道而非声音。与发布的平均频谱或合成的控制声音进行比较是行不通的:两个说话者之间的差异大于大多数缺陷,而本指南背后的评估中,两个错误的答案都源于此。

当没有原版也没有可用的静音时,静态音调缺陷本质上是不确定的。请如实说明,并提供合适的解读,而不是选择一个并基于它构建链。

命令、陷阱和实际配方:references/diagnosis.md。在诊断一个无人描述过的文件之前,请阅读该文件。

从症状开始

一旦你知道了频段和类型,就命名音频的问题。大多数糟糕的音频属于以下一或两种情况,每种情况都有一个现成的答案:

听起来像使用什么
下面有嗡嗡声或重击声rumble-cut,或 80 Hz 的 highpass
有轰鸣声、胸腔声Tame Boominess 任务(200 Hz)
发闷、像隔了层纸板Reduce Mud 任务(250 Hz)
很难听清词语Add Clarity 任务(3 kHz),或雕刻背景
刺耳且令人疲劳Soften Harshness 任务(3.2 kHz)
有些词比其他词响亮得多在压缩器上使用 Evenness,或 Even Out Levels
句子之间的房间音room-gate
人声和音乐在打架旁白雕刻 — 不是对任一轨道 EQ
听起来像没地方录room-tight 或 room-natural
只是听起来“业余”voice-clean,按顺序包含上述四项

完整目录、每个预设包含的内容、频段词汇,以及故意不覆盖的内容(去咝声、降噪、音色匹配):references/presets.md。

先减法,再加;滤波后处理电平;电平后处理关系;特性和限制器最后。每一步都改变下一步听到的内容——在高速滤波之前设置的压缩器会浪费精力追踪隆隆声。

根据问题而非名称选择效果系列

滤波器(highpass、lowpass、peaking、lowshelf、highshelf)决定允许一个轨道占据哪些频率。这是解决两个源冲突的首要工具,因为冲突发生在频段中:背景和人声都想要 1–3 kHz,从背景中拿走这个频段对背景的影响远小于整体调低对整个混音的影响。对人声使用高通滤波器是解决隆隆声的标准方法;低通滤波器则有意使声音变暗或发闷。

动态处理器(gain、compressor、limiter、gate)决定一个轨道的电平随时间如何变化。压缩缩小了大声与小声之间的距离,使安静部分能够凸显出来。限制器是一个上限——它不塑造任何东西,它保证没有东西能超过它。门限移除低于阈值的声音,这是你在短语之间消除房间音的方法。gain 是一个简单的电平级,当一个轨道需要让出位置时,自动化通道就在其上工作。

非线性处理器(saturate、bitcrush)改变波形的形状,从而增加原本不存在的谐波。当某个轨道需要个性或质感而非校正时,可以使用它们——但要记住,它们是生成性的:它们使稀疏的声源变得更密集,而非更干净。

时间类效果(delay、reverb、chorus、phaser)将轨道置于一个空间或赋予其宽度。这些效果最容易破坏混音,因为一个尾部或失谐的副本会挤占人声所需的同一空间。在应该放在其他东西后面的东西上使用它们,并使湿声量低于孤立听起来合适的水平。

链是串行的:每个效果处理前一个效果产生的结果。因此,校正性滤波放在前面,个性在中间,限制器放在最后,它才能实际起到上限的作用。

旁白雕刻

它解决的问题。 人声下的音乐背景使人声难以听清。本能反应是闪避整个背景,这样有效但会使背景失去所有存在感——音乐在整个旁白期间变得无力。但是人声并不需要整个频谱。它只需要它实际占据的少数几个频段。雕刻只拿走这些频段,背景保留其低频和高频,因此在人声仍然清晰可辨的同时,背景仍然是音乐。

它是一种关系,而非一种效果。 设置位于背景上——即被处理的轨道——并且它们指定要监听的人声,就像侧链压缩器一样:你选择被处理的轨道,并选择使其变小的来源。永远不要将雕刻放在人声轨道上。 人声对着自己雕刻是一个错误,而非微妙的混音选择。

针对每一个人声,而不是其中一个。 sources 是一个列表,因为一个背景通常运行在一整个序列之下——一个旁白、一个采访回答、第二个主持人。它们在测量之前被求和到背景自己的时钟上(mixCarveSources),因此一次分析覆盖所有声音:频段来自所有存在的语音,而包络在语音发生的任何地方上升。从不与背景同时播放的人声被排除在外;它们无法掩盖它。

针对多个片段 ID 而不是一个组的雕刻是错误的。将片段分组并针对组进行雕刻。 这是一个不变规则,而非建议。逐个命名片段必须完全正确,且只在下次编辑前保持正确——后来添加的第四个旁白片段会在雕刻的感知范围外播放,而背景会无声地无法在其下进行闪避。相反,命名组可以在分析时解决归属问题,因此后来添加到组中的片段无需修改 sources 即可被覆盖:

<!-- 将旁白分组,然后针对组进行背景雕刻 -->
<audio id="vo-intro" data-audio-group="voiceover" …></audio>
<audio id="vo-middle" data-audio-group="voiceover" …></audio>
<audio id="vo-outro" data-audio-group="voiceover" …></audio>

<audio id="music" data-fx-carve='{"enabled":true,"sources":["voiceover"],"strength":0.8}' …></audio>

一个包含两个或多个普通片段ID而不是一个组的 sources 列表会被 audio_carve_ungrouped_sources lint 规则捕获——它仍然有效,但在添加片段时会静默失效。

保持雕刻组为人声组:不要包含背景、SFX或音乐。 sources 中的组ID在每次分析时解析为其当前所有成员,因此你命名的组就是你稍后将得到的组——而不是编写它时测量的轨道。两种可能会出问题的情况:

  • 背景在其自己的源组中。 它将自己作为人声传递给自己,并针对自己的内容进行雕刻——"永远不要针对自身雕刻轨道"的规则在下次重新分析时出现。
  • 人声组中的SFX或音乐片段。 它在下次分析时进入侧链,背景开始在各种音效下闪避,即使编写属性时从未测量过它。

这两种情况在雕刻写入时都是不可见的:分析将它检测到的人声求和,并永远不会通过组解析进行往返,因此第一次遍历确实是正确的,只有下一次才是错的。因此,为每个角色分配自己的组——music 用于背景,voiceover 用于旁白,sfx 用于音效——并保持 sources 中命名的组只包含人声。

carve.mjs 在看到任一情况时拒绝写入组形式,记录片段ID,并在 stderr 上输出是哪个成员阻止了它。然后 audio_carve_ungrouped_sources 规则指向此安排,而非 CLI 静默地持久化比其测量的更宽的雕刻。

此次运行未包含的人声不是这些情况之一,并且…

[翻译截断]

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

1999AZZAR/designer-mcp

SOTA animation and physics heuristic guide using motion.dev

1999AZZAR/designer-mcp

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

1999AZZAR/designer-mcp

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → reconstructed motion (frames read as states, not slides) (REST/CLI), connector-assisted motion when available, and shaders from a connector or native export. Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.

1999AZZAR/designer-mcp

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

1999AZZAR/designer-mcp

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

1999AZZAR/designer-mcp

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.

1999AZZAR/designer-mcp

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

1999AZZAR/designer-mcp

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

1999AZZAR/designer-mcp

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

1999AZZAR/designer-mcp

Search, install, and wire registry blocks and components into HyperFrames compositions. Use BEFORE hand-building any named visual — whenever a brief, a user, or a storyboard names a look, effect, treatment, or transition such as CRT scanlines, glitch, chromatic aberration, film grain, a shimmer sweep, a chart, a code or terminal window, a map, or a confetti burst — because roughly 400 hosted items already cover many of them and the search ranks all of them with nothing installed, no project, and no account. Also use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

1999AZZAR/designer-mcp

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

1999AZZAR/designer-mcp

Use when building or editing a HyperFrames project that people open in Studio: how the timeline should be laid out so it reads well (one caption track, one element kind per track, every scene a sub-composition) and where captions and key content may sit (safe zones). Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is `creator-editing-recipes.md` in `/hyperframes-core`.

1999AZZAR/designer-mcp

Agent Media OS, the single skill for every media need in a HyperFrames project. Resolve BGM, SFX, image, icon, brand logo, voice, color grade, or LUT into a frozen local file or paste-ready block + ledger record (one verb, `resolve`); generate via TTS / music / image models when the catalog misses; produce voiceover, transcription, captions, and background removal through one shared audio engine; operate on media (cut / reframe / transform); and reuse assets across projects. Also use for vague feedback that real footage looks dark, flat, boring, should feel retro/camcorder/print/ASCII, needs privacy, or needs a media reveal.

1999AZZAR/designer-mcp

Turn a music track (an audio file, a video to pull audio from, or a track generated from a mood brief) into a beat-synced video — lyric video, slideshow, or kinetic promo. The music drives all pacing; any user-supplied images/videos are cut onto the same beat grid, and a complete video needs zero assets. Narrated pieces → the input-matched workflow (see /hyperframes). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Port an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

1999AZZAR/designer-mcp

Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.

1999AZZAR/designer-mcp

Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on "graphic overlays", "on-screen graphics", "package / dress up my video". Not plain subtitles (/embedded-captions). Unclear → /hyperframes.

1999AZZAR/designer-mcp

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

相关技能