@David-Healey also don't forget the buddy of HISE_MACROS_ARE_PLUGIN_PARAMETERS:

HISE_NUM_MACROS. Help text in the upcoming docs:

HISE_MACROS_ARE_PLUGIN_PARAMETERS

Publishes every macro control as a dedicated plugin parameter in front of the scripted automation slots.

Default Hot Reload Auto Config 0 yes no

When enabled, the exported plugin advertises one plugin parameter per active macro slot before any custom automation slot or scripted plugin parameter, which lets the host automate macros directly instead of routing through a UI component. The plugin parameter index reported to the host changes because the macro slots occupy the first positions, and macro state no longer restores from user presets when the preset system is running in exclusive mode (which matches how plugin parameters are normally managed by the DAW rather than by the preset). Combine this with a reduced macro count to keep the parameter list compact.

Read at runtime from the Extra Definitions, so no HISE rebuild is required. Pair it with HISE_NUM_MACROS so the number of exposed plugin parameters matches the macros you actually use.

See also: $API.MacroHandler$ -- macro slots exposed as plugin parameters are the ones managed through this scripting object, $MODULES.MacroModulationSource$ -- every macro slot is mirrored as a front-of-list plugin parameter when this is on, $PP.HISE_NUM_MACROS$ -- determines how many macro plugin parameters the host sees

HISE_NUM_MACROS

Number of active macro control slots that the project exposes on the master chain.

Default Hot Reload Auto Config 8 yes no

Sets how many macro slots are visible to scripts, to the macro handler, to the Macro Modulation Source synthesiser and to the macro plugin-parameter publishing path. The default of 8 matches the original HISE layout and the UI panels that show a fixed eight-knob strip; values between 1 and the project-wide ceiling let you trim a compact product or scale up to a modular rig with many assignment targets. The value is read at runtime, so changing it in the Extra Definitions and reopening the project is enough to see the new slot count without a HISE rebuild.

Must not exceed the project-wide macro ceiling of 64, otherwise compilation fails with a hard error.

See also: $API.MacroHandler$ -- slot count seen by every scripting call that enumerates macros, $API.Engine.setFrontendMacros$ -- setFrontendMacros expects a name list sized to this value, $MODULES.MacroModulationSource$ -- chain count of the macro modulation source synthesiser matches this value, $MODULES.MacroModulator$ -- macro modulator slot index is validated against this value, $PP.HISE_NUM_MAX_MACROS$ -- hard upper ceiling that this value must not exceed, $PP.HISE_MACROS_ARE_PLUGIN_PARAMETERS$ -- determines how many plugin parameters are published when macros become plugin parameters

@David-Healey Killin it.

@David-Healey Looking forward to getting into expansions. Glad you're around for questions! 😂

@d-healey I'll have a look at that thankyou. I may have set it/not set it correctly from one OS to another maybe

@d-healey i must of mistyped it cause i just retyped it and its better than before your a genius you have no idea how much i appericate you taking your time with me. Im sure you have a million other things you could be doing right now, I JUST WANT YOU TO KNOW THAT I TRULY AND GRATELY APPERICATE YOU THANK YOU VERY MUCH I SINCERLY MEAN THAT

@Lindon yes that what I have done. The panel is above the preset browser in my project.
That panel is essentially a 2 x 4 grid of 'buttons' (one for each tag) inside that panel and when the 'buttons' are clicked currently it prints a list of all presets that have that tag to the console depending on which button was clicked. This is working correctly so the tags are being picked up and read correctly by hise which is good.

What I'm looking to try and do ultimately is have the preset browser filter to show only the bass presets if I click the bass tags button, only the bells presets if I click the bells tag button and so on.

Bump again

@d-healey giphy.gif

Never mind: expHandler.setAllowedExpansionTypes([expHandler.Encrypted]);

@Christoph-Hart Ah nice, ok. I'll make that change and create a pull request. Thanks for your help!

@Christoph-Hart Ok I figured out how to trigger it consistently. Run this snippet in any project that has expansions. It's the call to refreshExpansions after the call to unloadExpansion that is causing problems.

HiseSnippet 862.3ocsU01aSiDDdcZMhj6EARv2s3SoRPTxAWAIDhRSR4xczRzkB5jPmPaWOtYUWuq0tqKMBUo6m78OfaFa2XmR.ghNhhhyLyyy5mY7LimZMBv4LVVP6iWjArfeLb1Bse9v4bolMYDK3tg4ZkgGO9hLt1IM5iAmms+hLtyAwrffsdIAMn81rhO+6y2mq3ZAT6hwdqQJfWISk9ZuS26OjJ0A7X3XYZCzOZuIBidnQYxQYsUXeVFWbF+T3HNAqUHK3Fiikdiclm6AGKX68MwKlM27AcI92JcxST.YLfMCOnR2GXTwjhIurgykp3oWk9NFdJSqKFaUVLtS3gxX4R+0EkaUDHplQy5QPqUk2VqHuAMkW+FxaMRJngj1tTR2NblvJy70QH87CgSzdvlvwxdSoThk05AsBGZPDZeuT9YvAVzXIit61u+8ive14oc5fkdmOBtH6235XEXidVzX8oRMzSXALeV1FTEuKRZImWIwqOqA6dmB9kLnnD7NRsBOvnjbsvi9iL58y8did.oQqQ0UXRyLZTs2O5btJG1oyG6zVlD0sxpMZ1VYDbUDTd+ny9c8+6mh9wuDToaDjf2l3tvNHiBJsgdWqYlzC4uVwVHwBt4KQ3JgbIAqCd4RLAtpVhY2vqjZ26UkD2amdNxeQpLjqTmfsucudNhGZi7+HiGdMJFJO6bYmnqGJIYswpNqhGCqILMWY+ZD6pySOArMqxDPrYa0N3vubGbyALQYYoAPidhV5ecFn+RicrpZI9u2LYD2yo19JeHtLv5kjDBFAmi6PJGBZGNBbm4MYEXqd.fqE7EQ+4pQjxBNSFSDpp9rKpWz7t8Vrz3e988jtCMo34vsn6fVN94vD8TrW.7znD6ymEws.l3bE2u5pAZeXU.rZux7HMygcU9EM2W9+19huUId6voRuX950Xq0nQ7Yx2CMVsk8mBGmj.Bes.2N7f+56yJU1eZx8R8oGx8VI1KDdTd5L7EMB.u6ZMnnt8fVTeYocexlp.y.cbgwmvOUAGP1AUAGbUPVJWXMuWTNiQ6wuYgGTS5hWg0N7PxNZ.qXtC4E1uWeVJ9Jk2KDT5+.bTY8b9kMfyC2.NOZC37qa.mc2.NOdC37juJG5s4uH2aRKGGPGSGWrLJHXrlicVEcgr+CVvzhhC

@iamlamprey No that's a different issue which I'm waiting on a fix for as well :)

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.

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