FR: get the location of plugin bundle [moot]

Audio Plugins
1

Now that plugin bundles are supported more or less universally, would it be possible to discover where those bundles are located from within the plugin?

The reason I would like this is that on more than one occasion I have used an installer to put some assets in a known location on disk, but it would be much better if those disk based assets could just be part of the plugin bundle itself and be able to find out that location without having to basically guess/hope they’re in one of the possible “known” locations.

If the plugin interfaces don’t support this (or it’s otherwise impossible to implement) please close this FR.

edit: I’d be more than OK with only the more modern formats supporting this if say it’s discounted because VST2 isn’t a bundle format on Windows for example. Perhaps there could also be a method along the lines of bool isPluginBundled()?

2

File::currentExecutableFile gives you the location of the plugin binary. Surely this is all you need, or am I missing something?

3

I was under the impression that that returns the host binary location, which doesn’t guarantee where the plugin might be. Happy to be corrected if I’m mistaken.

4

I’ve been using this method to locate plugin binaries for nearly 15 years :slight_smile: The only time I ever had an issue was on Linux. Once upon a time, checking the ‘standalone’ target in the Projucer caused some problems. But I haven’t noticed that issue since moving to CMake.

Seems to work as described in the docs:
https://docs.juce.com/master/classFile.html#a3e19cafabb03c5838160263a6e76313dab960741272c75e94482f295a516aae62

1 Like
5

Lol, OK, I was basing my knowledge off of forum posts from 2005 :joy:

Any idea how I can close this FR or is it something the JUCE team has to do? I think it would be useful to stay around so anyone else in future searching the forum doesn’t get massively out of date information like me!

edit: figured it out, just needed to change the category…

2 Likes