Best way to package data with a plugin

[cgo435]

I’m currently implementing an LFO class to use in my projects. I want it to be able to load LFO shapes from a file. Currently, I’m using .wav files for this, though I realize that probably isn’t the best option.

My problem is that my current method of loading the data from the files involves using their absolute path (something like “/JUCE/Projects/myProject/Resources/sineWave.wav”) – as the File class requires – which means my plugin won’t work on a different computer.

I want to somehow package the data from these files with the build. The two methods that come to mind would be using a relative pathname (like “<resources_location>/myResource.wav”), or by including the data directly in the .vst3/.component file, but I don’t know how to do either of these.

If anyone could point me in the right direction I would very much appreciate it. I have a bit of experience with C++ and JUCE, but I’m by no means an expert on either one, so feel free to chastise me if I’ve got it all wrong.

[pizzafilms]

You could simply add the .wav files to the Projucer project. They will then be accessible to your plugin as BinaryData.

Take a look at this:

Wav assets compiling along with the plugin

I’m relatively new to JUCE and C++ I was struggling for a little while loading in a file for use as a SamplerSound in a synth that I am creating until I realised I had to use an absolute path. This is a little bit of a pain as I can’t really predict where people will install my plugins and will have to change the path for every operating system I support. So I was wondering if there was a way for me to load in all the wavs I will be using as assets and compile them into the plugin itself to byp…

[cgo435]

Thank you, this is exactly what I needed!