Smarter Template Workflow + Per-Library Kontakt Entries in Plugin Manager

Cubase
1

Hi everyone,

I’d like to propose two workflow improvements that would make Cubase significantly more powerful for users who rely on templates, large libraries, and container-style instruments like Kontakt.

Both ideas are simple, but together they would dramatically streamline genre-specific setups and large projects.

1. Smarter “Save as Template” Workflow (deferred dialog)

Currently, when selecting Save as Template, Cubase immediately opens the template dialog and interrupts the workflow.

Suggestion:
Add a checkbox inside the normal Save dialog:

“Save this project as a template”

The actual template dialog should appear only when the user presses Save.

Why this helps

This makes it possible to maintain project-dependent defaults, for example:

  • HALion Sonic → “Set this preset as the default for this project”

  • Kontakt libraries with different default patches

  • Orchestral vs. electronic vs. drum projects requiring different startup states

It makes templates more flexible and avoids breaking the creative flow whenever the user decides mid-project that this session should become a template.

2. More flexible Plugin Manager entries for Kontakt (custom name, custom icon, per-entry defaults)

Container plugins like Kontakt, HALion, Falcon, and others host multiple internal libraries.
Right now, Cubase allows adding a plugin multiple times in the Plugin Manager, but:

  • all entries share the same name

  • all entries share the same icon

  • all entries load the same default state

This limits template building massively.

Requested improvement

Allow each Plugin Manager entry to have:

  • its own custom name

  • its own custom icon/image

  • its own independent default preset / default patch

  • template-dependent visibility

So instead of a single “Kontakt” entry, users could create:

  • Kontakt – Orchestral Strings

  • Kontakt – Choir Tools

  • Kontakt – Analog Pads

  • Kontakt – Synth Leads

  • Kontakt – Drums Engine

All appearing as separate instruments in the browser, despite using the same plugin file.

3. Critical detail: Each custom Kontakt entry needs its own default library + patch

This is the essential part.

If Cubase allows Kontakt entries to be treated as separate instruments, each of these entries must remember its own default library and patch.

Example:

  • “Kontakt – Orchestral Strings” should always load the selected orchestral library and patch

  • “Kontakt – Analog Pads” should load the corresponding pad library

  • “Kontakt – Drums Engine” should recall the drum engine preset

Otherwise, multiple entries still behave like one plugin, defeating the purpose.

Why this matters

These additions would allow Cubase users to:

:check_mark: Build extremely powerful, genre-specific templates

:check_mark: Use Kontakt libraries as if they were standalone instruments

:check_mark: Maintain project-dependent defaults without workaround

:check_mark: Reduce load times by jumping directly to the right patch

:check_mark: Keep large projects clean and intuitive

For composers, electronic producers, template builders, and hybrid setups, this would be a huge workflow upgrade.

Summary

Two improvements, one goal:
Make Cubase more flexible for modern template-based production:

  1. Deferred Template Save Dialog

  2. Per-Library Kontakt Entries in Plugin Manager (with their own defaults)

These changes don’t alter Cubase’s core behavior—they simply make existing workflows smoother and far more powerful.

Would love to hear what other users think!