@Lunacy-Audio Looks like a good solution, thanks!

@gorangrooves

Perhaps this - https://woocommerce.com/products/software-add-on/

I think I might use this myself actually, looks simpler than my original idea...

@gorangrooves said in Export tool:

You would not want users to login for every single plugin that they need to download samples for (eg. 15 times). Also, this would also kind of limit that the only place you sell your plugins is your own store.

If you use a serial code then it doesn't matter where it is sold. The user just enters the serial code, your server verifies it and provides the download link. This also means they don't have to log in each time, they just enter a serial code which isn't uncommon already.

@Lunacy-Audio

I'm planning on using a shell script in the installer

So it's possible to have Packages run a shell script automatically after installation? What about InnoSetup?

However, most of the producers / composers I've worked with in Los Angeles are fairly opposed to this as it feels too intrusive.

The system I'm thinking of is not much different to them logging into my website to access the download links as they currently do. The only change is they won't need to open a web-browser.

@gorangrooves

The issue I am seeing with downloading the samples from within a plugin is that you have no control over how many times it is downloaded or who is downloading it.

Sure you do, there are a number of methods that you could use (these are all server side).

You can track the number of downloads from a particular IP.

You can limit downloads to only the IP that the customer purchased from (probably not a good idea).

You can limit the number of downloads in a set time period.

If you want to get fancy with some PHP (and this is what I intend to do). You can have your user enter login details in your plugin which connects to their account on your server to access the files they have purchased, at the same time you can check on your server how many times they have downloaded the files.

If you don't want the whole login details thing you can use a simple serial key instead.

There are other techniques and you can of course combine multiple methods.

Where and when would this download dialog of yours appear? What if a user needs to re-download?

The implementation if up to you. Christoph will (I assume) just be providing an API.

@Lunacy-Audio How do you handle this currently?

@Christoph-Hart When using the CLI exporter what option should be used for plugin type in order to output a VST3 plugin? Should I just use VST and enable the VST3 option in the project_settings xml?

I've tried this on GNU/Linux but it results in both VST and VST3 flags in the jucer file being set to 0, but I figure this could be an OS dependent thing.

@DanH https://forum.hise.audio/topic/1206/installing-samples-dialog/102

@orange said in Export tool:

AAX

On Windows: It's a folder that has .aaxplugin extension and also it has sub folders. The signed file is (if it is a 64bit plugin): PluginName.aaxplugin\Contents\x64\PluginName.aaxplugin

Thanks, what needs to be included in the installer, is it just the file or the whole folder?

What file extensions do AAX plugins have on Window and Mac?
Do VST3 plugins have a different extension to VST2 plugins?