Standalone App vs. Plugin Standalone app: what's the difference?
When exporting a virtual instrument from HISE, we have the option to export in various plugin formats, as well as a standalone app. The standalone app is what you would expect it to be.
However, when opening up an "export as a plugin" project in ProJucer and looking at the various plugin formats which can be selected, we have the option to export as a "plugin standalone."
The wonderful thing that I noticed is that this "plugin standalone" format contains a built-in File menu with audio settings in it, something that we normally have to implement on our own using a floating tile.
Other than that, is anyone aware of any other differences, and is there any reason to use the "regular standalone app" as opposed to the "plugin standalone app"?
@gorangrooves The option in the Projucer was introduced by the JUCE team after I've implemented the standalone version export and I didn't find any reason to update it - the settings dialogue is nice, but it's stock JUCE UI and everybody and their mother wants to customize those dialogues anyway.
So I would suggest to avoid that route as it's not tested at all and might interfere with some things I did in the HISE codebase...
@Christoph-Hart Got you. Thank you.