@lalalandsynth The background is transparent by default when you export. 👍

@Esaú_DFG Try a different version of xcode

Glad you found the root cause, will make things much easier. I'll see if I can do the same with bash.

@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) });

@justinfitzmusic

All a user preset does is store/restore the state of controls on the UI. So to get a sample map to change when a preset changes you need to script one of your UI controls to change the sample map when its value changes.

I have a video here that shows how to do it using a combo box - but you can use any control.

https://youtu.be/eQ7YvIeS5lY

@dannytaurus ah that makes sense. I'm just getting Claude to help with small little tasks so I haven't gone to the trouble of setting up a remote repo, etc.

@Lurch It's part of the alert window system so you need to use functions like drawAlertWindow

@Christoph-Hart i figured out that the jucer file didn't have the hi_faust module included, but it exported fine after adding that

@Chazrox Thx, it was kind of tricky to code but makes it fun.
I thought about making it grabbable for potential updates.

I did it with Claude in two days. Most of the time was actuallly spend on a bug in the Juce module though, that david helped to fix. In the end I have 3 files in the Hise Source that needed changing.

Its not a gracious proces though.

I need to export first so it creates the batch file and set all files up from hise but it will choke on the Juce module missing. Then switch to Juce 8 (trivial, I have a script to switch easily), add the module / flag in Juce and start the batch file again.

There is some other stuff to set up like an encoded file so the connection can be set up secure and some settings on the Hise side need to be hooked up if you want the screen to dim and audio to block, but you do this once per product in Moonbase.

Honestly it works for me, but looking forward to supported integration. Moonbase is a great platform.