AU Effect Plugin Opportunity [PAID]

Concept:
Develop a plugin effect that, when inserted on any channel in a DAW, dynamically controls that channel’s volume gate based on external MIDI note events. The plugin listens for MIDI input from a user-specified source (MIDI channel) and triggers its gating behavior based on a designated note (or note range).

Key Features & Functionality:

MIDI Source Configuration:
MIDI Channel Selection:
The plugin provides a UI option to select which external MIDI channel to listen to. This allows the effect to be controlled by any available MIDI source in the DAW
Note Filtering:
Users can specify a single note or a note range (e.g., C1, or C1–E1) as the trigger. The plugin should filter incoming MIDI events so that only those that match the set key trigger the effect.

Volume Gate Behavior:
Triggering Mechanism:
On receiving a MIDI note-on event (for the specified note/key), the plugin immediately opens the volume gate on the host channel. Conversely, a corresponding note-off event closes the gate.

Envelope Parameters:
Offer adjustable parameters for attack, hold, and release times. For a “hard” gate effect, defaults can be set to zero or near-zero values, but users should have the flexibility to adjust these settings to shape the gate’s response.

Instance Independence & Routing:
The plugin is designed as an effect insert, so multiple instances can run simultaneously on different channels. Each instance operates independently, allowing the user to bind different channels to different MIDI trigger sources.

Cross-Channel Triggering:
For example, one instance on Channel A could be set to trigger on MIDI Channel 1’s C1, while another instance on Channel B might trigger on MIDI Channel 2’s C1. Despite the same note (C1) being used, the plugin instances remain independent due to their distinct MIDI channel assignments.
Flexible Mapping:
The plugin’s design should allow any MIDI channel and any key to be chosen as the trigger, giving complete control over how various MIDI piano rolls (or controllers) drive different gating effects across the project.

Example Use Case:

When a MIDI note C1 is played on Channel 1, Instance 1’s gate opens. Simultaneously, if a separate C1 note is played on MIDI Channel 2, Instance 2’s gate opens. Meanwhile, a D1 note on Channel 1 triggers Instance 3.

This setup lets the producer control the volume gating of different channels independently, all through distinct key mappings and MIDI channels from one or multiple MIDI sources.

Topics in the JUCE Jobs section of the forum are automatically closed to prevent a lot of spam replies. Please use any links in the original post to contact the poster, or use the forum’s direct messaging system.

This topic was automatically closed after 2 minutes. New replies are no longer allowed.