example-podcast-visualizer
Skill130 starsChanged 38 days agoApache-2.0View on GitHub
Workflow for creating a podcast visualizer with multi-track audio mixing and DOM-based synchronization. Use when building audio-reactive compositions.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- skill-creatorSkill
- helios-coreSkill
- animated-video-philosophySkill
- cinematic-product-promo-planSkill
- motion-stylesSkill
- example-canvasSkill
- example-chartjsSkill
- example-d3-animationSkill
- example-framer-motionSkill
- example-gsapSkill
- example-lottieSkill
- example-p5-animationSkill
- example-pixiSkill
- example-reactSkill
- example-signals-animationSkill
- example-solidSkill
- example-svelteSkill
- example-tailwind-animationSkill
- example-threejsSkill
- example-vanillaSkill
- example-vueSkill
- helios-getting-startedSkill
- guided-brand-videoSkill
- guided-cartoon-shortSkill
- motion-design-rulesSkill
- guided-music-videoSkill
- guided-video-recipesSkill
- helios-playerSkill
- helios-rendererSkill
- helios-skillsSkill
- helios-studioSkill
- archive-brollSkill
- create-compositionSkill
- render-videoSkill
- workflow-visualize-dataSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 63
Use helios.subscribe to drive visual elements based on currentFrame.
- Distinctive: line 84
Ensure your audio formats (MP3, WAV, AAC) are supported by the browser and FFmpeg.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Podcast Visualizer Workflow
This workflow demonstrates how to build a podcast visualizer that mixes multiple audio tracks (e.g., background music, voiceover) and drives visualizations based on timing.
Quick Start
<!-- Background Music (Loops, Starts at 0s) -->
<audio src="music.mp3" loop data-helios-offset="0"></audio>
<!-- Voiceover (Starts at 2s) -->
<audio src="voice.wav" data-helios-offset="2"></audio>
<!-- Muted Track (For analysis only) -->
<audio src="sfx.wav" muted></audio>const helios = new Helios({
duration: 60,
fps: 30,
autoSyncAnimations: true // Required for DOM audio sync
});
// React to time
helios.subscribe((state) => {
const time = state.currentFrame / state.fps;
if (time >= 2) {
showVoiceVisualizer();
}
});Key Patterns
1. DOM-Based Audio Mixing
The Helios Renderer (in dom mode) automatically discovers <audio> and <video> elements in your DOM and mixes them into the final video.
- Discovery: Any element present in the DOM is eligible.
- Attributes:
src: The audio source.loop: If present, the audio loops.muted: If present, the audio is excluded from the mix (useful for logic-only tracks).volume: Not supported as an attribute for mixing yet (defaults to 1.0). Use RendereraudioTracksoption if precise volume control is needed, or bake it in.
2. Timing Control
Control when audio starts playing relative to the timeline using data-helios-offset.
<!-- Starts playing at T=5 seconds -->
<audio src="intro.mp3" data-helios-offset="5"></audio>- Positive Offset (
5): Delays start by 5 seconds. - Negative Offset (
-5): Starts playing immediately, but from the 5-second mark of the audio file (Seek).
3. Visual Synchronization
Use helios.subscribe to drive visual elements based on currentFrame. Since audio is handled by the browser/Renderer, you just need to ensure your visuals match the expected timing.
helios.subscribe(({ currentFrame, fps }) => {
const time = currentFrame / fps;
// Simple time-based trigger
if (time > 10 && time < 20) {
// Animate visualizer
}
});Common Issues
Browser Preview Sync
In the browser (Studio/Player), data-helios-offset is NOT automatically applied by the standard <audio> element. The DomDriver attempts to sync it, but precise start/stop behavior for offsets might vary compared to the frame-perfect Renderer.
Workaround: For perfect preview sync, you may need custom logic to play()/pause() audio elements in your subscribe loop, or rely on the Renderer verification.
Audio Format
Ensure your audio formats (MP3, WAV, AAC) are supported by the browser and FFmpeg.
Reference
- Example:
examples/podcast-visualizer/ - Renderer:
packages/renderer/src/strategies/DomStrategy.ts
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

