Getting ready for release
-
Hi everyone, im not too far of for my first product release.
However, i do have a couple of questions.- If i go with Monolith, can i go back and edit them if i later discover an issue?
- What is the benefit of Monolith vs a folder with the samples?
- When i create an installer, where should my "samples folder" by installed on the end-users computer for auto loading on first startup (if thats even possible)
-
@ThinkTank said in Getting ready for release:
What is the benefit of Monolith vs a folder with the samples?
Faster loading, vastly reduced storage footprint.
@ThinkTank said in Getting ready for release:
When i create an installer, where should my "samples folder" by installed on the end-users computer for auto loading on first startup (if thats even possible)
Your installer should create a file LinkWindows in the appdata folder %appdata%/Company/Project with a path to the location that the user specified during install. In that case, you ship monoliths directly. If it doesn't exist, the plugin will ask about samples location on first launch and then create the file. You can try that out to see how the file looks.
Plugins should always go to the default directory.
-
Thanks! Appreciate the tips!
Makes more sense now.
vst3 always go to common files/vst3 plugins right?But does that mean users can not install vst3 plugins on a secondary hdd?
-
@ThinkTank I mean you can allow them to, but the Steinberg VST3 spec specifies Common Files/VST3 as the default directory, and all DAWs scan that by default
If the user uses a different folder, they first had to manually change that in DAW settings. I don't remember the last time a plugin asked me where I want to install VST3, it just did.
For samples it makes sense to ask because they can be anywhere from 1 GB to 50GB. for a 30mb installer, it makes no sense. Apps often install much bigger payloads to appdata without even asking you about it.
https://docs.juce.com/master/tutorial_app_plugin_packaging.html
