@d-healey you can put them in sub folders. I do that with my plugs.
ProTools isn't linux compatible, so AAX is only PC and MAC.

@griffinboy After building Rhapsody I went off the idea. Managing one site's downloads is enough work for me. If I was doing it as a commercial product then it might be worth my time, but then I'd probably have to make it closed source which I'm not going to do.

@d-healey I had to specify the custom font in each instance of text, as "default" settings would not render any text, even though the default font was set in the script.
This is a quirk that didn't exist at first, but then got introduced at some point. Not sure if it is still present.

Now that I've reverted to using the hr1 system I ran into this issue again.

I have a library that is going to be about 20GB compressed and when I send out an update to my users that changes only the data (hxi) I don't want them to have to redownload the entire 20GB all over again.

So I worked with Claude to implement a split archive solution.

The default behaviour is the current behaviour, bundle everything together into one set of hr files - works for expansions and regular plugins as before. I did change the default split size to 2GB as that seems to me to make sense.

Then there are two new options:

Split Data From Samples: This will put the data into its own .hr1 file with the suffix _data. The samples will then be bundled into .hr2, .hr3, etc. as needed. If the user only needs the data (because they installed the samples previously) then they just download and extract the .hr1. As it extracts it will still check for the next archive as before but will fail silently if its not there. However if one of the other archives is missing it will report an error as expected - I also improved the error message so instead of just saying Read Error, it tells the user which archive is missing. Data Only Update: This just compresses the data into an .hr1 archive and assumes the samples haven't changed and have already been compressed using the split option.

bumpty dumpty :)

@d-healey You can do this using the file and file system APIs.