/bc-create-plugin

What kind of audio plugin do you want to build?

**Effects:**
- **Delay** - Echo/repeat effects (ping pong, tape delay, etc.)
- **Reverb** - Space and ambience (room, hall, plate, etc.)
- **Distortion** - Saturation and grit (tube, tape, bitcrush, etc.)
- **Filter** - Frequency shaping (lowpass, highpass, resonant, etc.)
- **Compressor** - Dynamics control
- **Modulation** - Chorus, flanger, phaser, tremolo
- **EQ** - Parametric, graphic, tilt EQ
- **Utility** - Gain, pan, stereo tools

**Instruments:**
- **Synth** - Subtractive, FM, wavetable synthesizers

What sounds interesting to you?

The BeatConnect SDK currently supports **effects** and **synthesizers**.
Sample-based instruments (samplers, drum machines, ROMplers) aren't supported yet - they require a different architecture for loading and streaming audio files.

Would you like to build an effect or a synth instead?

Great choice! A delay typically has these controls:

- **Time** - How long before the echo (ms or synced to tempo)
- **Feedback** - How many repeats
- **Mix** - Dry/wet balance

Want these standard controls, or do you have something specific in mind?
(e.g., "add a filter on the feedback" or "make it a ping-pong delay")

Nice! A distortion usually has:

- **Drive** - How much saturation
- **Tone** - Brightness control
- **Mix** - Blend with clean signal

Want the standard setup, or something custom?
(e.g., "add a 3-band EQ" or "make it sound like a tube amp")

How do you want to build the user interface?

**Web UI (Recommended for beginners)**
- Uses React/TypeScript for the UI
- Hot reload during development - see changes instantly
- Modern web technologies, easier to style
- Reference: example-plugin/

**Native JUCE UI**
- Uses JUCE's C++ UI components
- More traditional approach, full C++ codebase
- Better for complex custom graphics
- Reference: example-plugin-native/

Which do you prefer?

What do you want to call your plugin?

Keep it short and catchy - this will be the name users see in their DAW.
Examples: "TapeDelay", "WarmDrive", "SpaceVerb"

Your plugin name:

Let me validate the project to make sure everything is set up correctly...

Let's build and test your plugin locally!

1. First, install web dependencies:
   cd plugin/web-ui && npm install

2. Start the web dev server (for hot reload):
   npm run dev

3. In another terminal, build the plugin:
   cd plugin
   cmake -B build -D<PLUGIN_NAME>_DEV_MODE=ON
   cmake --build build

4. Run the standalone version to test:
   ./build/<PluginName>_artefacts/Standalone/<PluginName>

You should see your plugin UI! Try the controls and make sure audio passes through.

Let's build and test your plugin locally!

1. Configure the build:
   cd plugin
   cmake -B build
   cmake --build build

2. Run the standalone version to test:
   ./build/<PluginName>_artefacts/Standalone/<PluginName>

You should see your plugin UI! Try the controls and make sure audio passes through.

Your plugin is working locally. Let's push it to GitHub so BeatConnect can build the release versions (VST3, AU, AAX) for Windows and macOS.

Ready to commit and push?

git add -A
git commit -m "Initial plugin implementation"
git push origin main

Done! Now go to your BeatConnect dashboard:
1. Create a new Project
2. Link this GitHub repository
3. BeatConnect will automatically build your plugin

You'll get downloadable installers for Windows and macOS once the build completes!

plugin/
├── CMakeLists.txt          # BEATCONNECT_USE_WEBUI=ON
├── Source/
│   ├── PluginProcessor.cpp
│   ├── PluginProcessor.h
│   ├── PluginEditor.cpp    # Creates WebBrowserComponent
│   ├── PluginEditor.h
│   └── ParameterIDs.h
└── web-ui/
    ├── package.json
    ├── src/
    │   ├── App.tsx         # Your UI components
    │   └── hooks/
    │       └── useJuceParam.ts
    └── dist/               # Built by npm run build

plugin/
├── CMakeLists.txt          # BEATCONNECT_USE_WEBUI=OFF (or not set)
├── Source/
│   ├── PluginProcessor.cpp
│   ├── PluginProcessor.h
│   ├── PluginEditor.cpp    # JUCE components (Slider, Label, etc.)
│   ├── PluginEditor.h
│   └── ParameterIDs.h
└── (no web-ui folder)

juce_add_plugin(${PROJECT_NAME}
    NEEDS_WEBVIEW2 TRUE    # Required for web UI
    # ...
)

target_compile_definitions(${PROJECT_NAME}
    PUBLIC
        JUCE_WEB_BROWSER=1
        BEATCONNECT_USE_WEBUI=1
)

juce_add_plugin(${PROJECT_NAME}
    NEEDS_WEBVIEW2 FALSE   # Not needed
    # ...
)

target_compile_definitions(${PROJECT_NAME}
    PUBLIC
        JUCE_WEB_BROWSER=0
        BEATCONNECT_USE_WEBUI=0
)

Don't worry, build errors are normal! Paste the error message and I'll help you fix it.

Let's debug this. First, try the Standalone version - if that works, the issue is with the plugin format. Check the build output for any warnings about VST3/AU.

This is usually a constructor order issue. Let me check your PluginEditor.cpp - the WebView needs to be created in a specific order.

This means the WebUI resources weren't found. VST3 bundles have a different structure - the Resources folder is a sibling of the executable folder, not inside it.

Fix: The PluginEditor.cpp must check multiple paths:
  resourcesDir = executableDir.getChildFile("Resources").getChildFile("WebUI");
  if (!resourcesDir.isDirectory())
      resourcesDir = executableDir.getParentDirectory().getChildFile("Resources").getChildFile("WebUI");

CI uses 'npm ci' for faster, reproducible builds, but it requires package-lock.json.

Fix:
1. Remove 'package-lock.json' from .gitignore (if present)
2. Run: cd plugin/web-ui && npm install
3. Commit the package-lock.json file

The validation found some issues. Let me fix them before we continue...
[Address each issue from /bc-validate output]