daw-smoke

Automates REAPER sessions to validate audio plugin functional integrity via reload, live-swap, sequence-loop scenarios.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill daw-smoke-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daw-smoke
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/daw-smoke
Command: npx skills add https://github.com/Generous-Corp/pulp --skill daw-smoke-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the gap between headless plugin validation and real-world host behavior, ensuring that reload, editor, and format-adapter changes function correctly inside a DAW like REAPER.

Core Features & Use Cases

  • Functional Verification: Validates plugin behavior in a live host environment, catching issues like parameter contract mismatches that headless tests miss.
  • Multi-Mode Testing: Supports reload verification, live plugin instance swapping, and sequence loop seeking to ensure sample-accurate continuity.
  • Use Case: Before shipping a new version of an audio plugin, use this skill to confirm that the plugin reloads correctly and maintains sequence timing while the DAW is playing.

Quick Start

Run the daw-smoke skill to verify the current plugin build by executing the reload mode within a fresh REAPER session.

Frequently Asked Questions about daw-smoke

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

FAQPage Schema
How do I verify audio plugin behavior in a real DAW instead of headless tests?

To verify audio plugin behavior in a real DAW, you can automate REAPER sessions to validate reload, live-swap, and sequence-loop scenarios. This ensures sample-accurate behavior and parameter contract compliance for your plugin.

Why does my audio plugin pass headless validation but fail during DAW reload?

Audio plugins can fail during DAW reload due to parameter contract mismatches or format-adapter changes that headless tests miss. Automating REAPER sessions targets these specific reload scenarios to ensure functional integrity inside the host environment.

Can I automate live plugin instance swapping and sequence loop seeking in REAPER?

Yes, you can automate live plugin instance swapping and sequence loop seeking in REAPER. This multi-mode testing verifies sample-accurate continuity and confirms the plugin maintains sequence timing while the DAW is actively playing.

Do I need a local REAPER installation to automate audio plugin testing?

Yes, you need a local REAPER installation with specific configuration to perform automated audio plugin testing. This setup enables headless-safe, non-polluting verification of plugin lifecycle events within the host environment.

What is the best way to test audio plugin lifecycle events before shipping a new version?

The best way to test audio plugin lifecycle events before shipping is to execute reload mode within a fresh REAPER session. This confirms the new plugin version reloads correctly and maintains sequence timing during live playback.