daisy-seed-effect

Guide audio effect development for Daisy Seed firmware and VST/AU plugins.

1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/chrfalch/daisymultieffect --skill daisy-seed-effect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daisy-seed-effect
Source: https://github.com/chrfalch/daisymultieffect/tree/main/.github/skills/effect
Command: npx skills add https://github.com/chrfalch/daisymultieffect --skill daisy-seed-effect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides tools and documentation for how effects are created and managed within the DaisySeed Multi-Effect pedal project.

Core Features & Use Cases

  • Cross-platform architecture covering firmware and VST/AU plugins.
  • Metadata-driven design with effect metadata, parameters, and a clear workflow to add new effects.
  • Guidance on implementing DSP, registering effects in the audio processor, and testing across firmware and desktop environments.

Quick Start

Add a new effect by defining its metadata in core/effects, implementing the DSP in a new header, and registering it in the audio processor, then test in firmware and VST/AU.

Frequently Asked Questions about daisy-seed-effect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new audio effect to the Daisy Seed multi-effect pedal?

To add a new audio effect, define its metadata in core/effects, implement the DSP in a new header, register it in the audio processor, and test across firmware and VST/AU environments.

What is metadata-driven effect development for Daisy Seed firmware?

Metadata-driven effect development uses structured effect metadata and parameters to guide the creation and registration of audio DSP algorithms in the Daisy Seed audio processor.

Does this Daisy Seed workflow support both firmware and VST/AU plugin development?

Yes, this workflow supports cross-platform audio effect development by ensuring consistency between Daisy Seed firmware implementations and desktop VST/AU plugin builds.

How do I map DSP parameters for effects across firmware and desktop plugins?

Parameter mapping is handled through a structured metadata framework that ensures cross-platform consistency between Daisy Seed firmware and VST/AU plugin implementations.

What is the best way to test Daisy Seed audio effects across different platforms?

The best way to test audio effects is to follow the structured workflow to verify DSP implementation and metadata registration across both Daisy Seed firmware and VST/AU desktop environments.

Why do I need to register effects in the audio processor for the Daisy Seed?

Registering effects in the audio processor is required to integrate the new DSP algorithms and metadata into the Daisy Seed multi-effect pedal's active audio processing chain.