Override default VST plugin UI with custom UI

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
audio-video-rtc, desktop

Research direction

Start by reading the AudioProcessor.Initialize and ProcessMain entry points mentioned in the issue, along with the existing default UI integration. Determine whether replacing the default VST UI with an Uno Platform window is supported, including the required UI-thread lifecycle; done means a documented, reproducible integration path or a clearly stated limitation.

Written by the indexing model from the issue text.

Description

I wrote a bunch of classes that make up a UI that opens a window and draws graphics on its own. Where should I call the UI init code in the plugin?

I tried to call the method in a separate thread in my AudioProcessor's Initialize() method:

protected override bool Initialize(AudioHostApplication host)
{
    _ = Task.Run(() => {
        // ... UI init code here
    });

    return true;
}

...and it crashed the DAW.

I now tried to move it to the processors's ProcessMain() method without opening without a separate thread, and only the default UI for the plugin shows up.

How do I make my custom UI show up instead of the default UI?

Note: I know that this is barely even supported in the codebase but I assume that at least some people got something like this to work, so I thought to ask around here. I am using the Uno Platform to develop the custom UI for the plugin. This is such a long-shot but I figured it wouldn't hurt to try and ask here.

Thanks for any help regarding this!

Dominant language
C#
Stars
152
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xoofx/NPlug

All issues in xoofx/NPlug

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.