Context-Aware AI Signal Chain & License Assistant

Title: Feature Request: Native-First AI Signal Chain & License Assistant

Summary: A prompt-based assistant that recommends processing chains using stock Cubase tools first, supplementing with third-party plugins as secondary recommendations.

Key Mechanics:

  • Cubase-First Recommendation Engine: Defaults to recommending native Cubase stock plugins (EQ, Frequency 2, Squasher, Magneto II, Supervision) as the primary option to achieve the mix goal. Third-party VSTs are listed as 2nd and 3rd alternatives.

  • Goal-Oriented Suggestions: Input natural prompts (e.g., “Make this bus louder” or “Smooth out this synth”).

  • Local License Scanner: Evaluates available installed licenses and suggests optimal plugin processing order and baseline parameter starting points.

  • Workflow Focus: Maximizes the value of stock tools and existing paid plugins without needing external searches.

How would you propose to explain to this AI what you are trying to accomplish so that it can make these recommendations?

I could give you some general guidelines for how processing signal chains should GENERALLY be organized. For every one of these guidelines, there are numerous examples of how musicians creatively alter these guidelines to achieve a different outcome.

Thanks much appreciated reading this. They ai would only be for a suggested signal flow based on the plugins you already own in your DAW, wether it be the native plugins or third party. But only as a suggestion the user will always have the final say. Sometimes its nice to use a different plugin that you’ve not used for a long time for more creativity :ok_hand:

What does Claude suggest when you pose the question along with the listing of what you own? I doubt SB would ever do this for a couple of really expensive reasons.

Considering that developer resources must be used economically, I would vote no on this, since it’s already possible to do, as @DosWasBest suggested, using AI agents by using your own list of plugins.

imo this is not something that fits into the Cubendo zeitgeist

Thanks all. It was just a thought on my mind. I just threw the question out there to see what real humans thought of this and what would the bottle neck be if any.:slightly_smiling_face:

Why are you quoting your own post? I understand you want to keep putting AI generated feature requests in the forums, but are you gonna automate even your answers?

Thats actually me answering. Sorry if I sound like ai. This was was only an idea I thought of as a suggestive companion it doesn’t even need to be ai at all. The companion would be for if you ask it a question based on the plugins you already have in your DAW, so its not generic but more specific