@gonzalo Welcome, !

@David-Healey Yeah, even though the UK government is doing all it can to erode them away year after year 😂

Aside from tax efficiency, the main reasons I'm doing it are for plugins:

Ability to use Azure cloud-signing on Windows, and Ability to have Meat Beats Ltd as my Apple signing ID instead of my full name.

@Chazrox yeah, no doubt. Its not essential.

@lalalandsynth ahh yup. 👍

Update: Claude-generated gist here of the suggested patch: https://gist.github.com/weavermedia/3fc4a419920fcda8de389a89d7aec68d

This is Claude's minimal fix: https://github.com/christophhart/HISE/pull/1003

I've tested it and it appears to work. The fix just closes each file reader after reading the data into the preload buffer.

You're trying to build the Faust build without having installed Faust. Select another Scheme to build that doesn't include Faust (or use the hise-cli for setting this all up).

@ustk Just the ever-tightening security of OS vendors. Privacy is a selling point now, as is anti-machine-fingerprinting.

A user account authentication system, via the browser, feels much more lightweight, predictable and more transparent to the user.

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.

With the mod matrix system each connection can have a intensity and you should also be able to set it programmatically without the matrix floating tile using the API.

For targets that dont expose a mod chain you can just define a UI knob and give it a matrixTargetId. You‘ll loose the precision of the real mods but if it‘s acceptable then fine.

The modwheel could also be a global source modulator using a control modulator.

@bashfulsound It's a bug. I submitted a PR here but not sure if Christoph has seen it yet.

https://github.com/christophhart/HISE/pull/962

@David-Healey cool. thanks!

@Bart I get inspiration from everywhere, having said that I have a massive PureRef file with all kinds of designs.

@Christoph-Hart I've merged the new commit and it no longer crashes, just shows some ugly errors. Is this intended as a stop-gap solution? Because isDefined() still returns true for the none-existent function.

Edit: Oh I see, it just stops the execution at the "error"

Tried your suggestion and appears to be working here, maybe a preprocessor definition (default true) to protect older buggy projects?

@David-Healey That's fixed now, it now respects the scope of anonymous functions within a namespace like this.

@Christoph-Hart

The newly built HISE version creates a new RHAPSODY template

0.png

1.png

2.png

3.png

@dannytaurus Yeah this is what I'm doing

const automationDataFile = Expansions.getAppDataFolder().getChildFile("automation.xml"); const automationDefaults = Engine.createMidiAutomationHandler().getAutomationDataObject(); // Pulls the defaults from the project on first run const uph = Engine.createUserPresetHandler(); uph.setStateManagerProperties({ SubStates: { MidiAutomation: "External", MPEData: "External", macro_controls: "External" }, ExternalFileDefault: { MidiAutomation: automationDefaults }, ExternalFile: automationDataFile.toString(automationDataFile.FullPath) });