Issues in some hosts on some machines

[DavidCNAntonia]

Hi I have recently released my first plugin for windows. I’m normally at home writing for Mac/iOS so am facing some new issues.

The plugin runs fine on all hosts on my test computer - and judging by the few complaints I’ve had so far it runs fine on most users computers. However I have had 1 report from a user using Bitwig 3.0.3 saying that they get this error when they try to load the plugin (VST3, Windows 10): com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Not a plug-in file.

And another report saying that in FL Studio (again windows 10 it comes up with an error: There was a problem loading the plugin for an unknown reason.

Is this something to do with using the DLL runtime library or could it be something else?

Thanks,
David

[Achder]

When I got that error in Bitwig on Mac my plugin couldn’t find a dynamically linked library. So yeah, it may well be a problem with the runtime library.

[ImJimmi]

@DavidCNAntonia

Is this something to do with using the DLL runtime library

If your release configuration (Exporters>Visual Studio>Release) has Runtime Library set to Use DLL runtime then your users will need to install the C++ runtime to be able to use your plug-in.

There was some discussion about which option is best here:

[Request] Change the default option for "Runtime Library" on Release configurations for VS exporters to use the STATIC runtime

One of my users has alerted me to the fact that my plug-ins can’t be used by users who do not have the VS C++ runtime DDLs on their systems because my plug-ins depend on the DLL. This wasn’t something I hadn’t paid any thought to since I’d assumed the Projucer would set up the release configuration propery for a full comercial release, but upon inspection the Runtime Library option for the Release configuration for Visual Studio is set to Default (Use DLL runtime). Can we please change the def…