Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty window at startup #23

Open
oparisy opened this issue Aug 28, 2022 · 2 comments
Open

Empty window at startup #23

oparisy opened this issue Aug 28, 2022 · 2 comments

Comments

@oparisy
Copy link

oparisy commented Aug 28, 2022

Hi, I compiled clap-host under Windows following the Readme instructions.

What is its expected behavior? I tried launching it from command line, with and without the path to a clap plugin (Odin2) as the first argument, and in both case I get an empty Windows (with no available menu or action) and the following console error:
Failed to load plugin ' "" ': "The shared library was not found."

I noticed issue #15 referencing a similar error message, but seemingly later (in my case I cannot even perform the "Select File => Load Native Plugin Preset" step by lack of a menu).

@oparisy
Copy link
Author

oparisy commented Aug 28, 2022

Oh.

>clap-host.exe --help
Usage: clap-host.exe [options]
clap standalone host

Options:
  -?, -h, --help                     Displays help on commandline options.
  --help-all                         Displays help including Qt specific
                                     options.
  -v, --version                      Displays version information.
  -p, --plugin <path>                path to the plugin
  -i, --plugin-index <plugin-index>  index of the plugin to create

_pluginPath was not set in Application::parseCommandLine since I did not use the -p option, which led to trying to load a plugin with an empty path.

I guess some command line validation (displaying usage if a mandatory argument is missing) would be helpful.

@sagantech
Copy link

Adding a menu would be a better solution since many problems can also occur after one figures out how to load a plug-in. For me, the asio driver was continuously crashing and there is no way to change that. I finally installed ASIO 4 all and it started working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants