What if you use Engine.setLatencySamples(Engine.getSamplesForMilliSeconds(10))?
10ms attack is a big min value for a limiter...

@Christoph-Hart Surely, this is something we'll have to face. Better sooner rather than later.

@d-healey Thanks Dave, yet another candidate for "extra Definitions" then...

@VHO No problems 👍

Will do, thanks!

@Christoph-Hart OK will do..

@Christoph-Hart great - all good - again.

I fact the error is weirder than that. If I take an old Hise and export AU it works.
Then when I come back to the latest version, now I get an AU FX even if I export VST...
It's like the compiler takes only the last format...

Oh wait, I got a Projucer "permission denied" error with the last Hise here:
permissionDenied.jpeg

instead of this with an old version:
goodOne.jpeg

Nevermind, switching to the other thread were you posted it :)

oh, and I can't send or receive signals with the send and receive nodes from or to frameblocks.

@SteveRiggs 👍

Ooops, I meant 5 is fixed - which explains why it's magically not crashing anymore :)

On mine I have send fx on 3&4, 5&6, 7&8, and 9&10

In the exported plugin, all of those above output sound and the effects work, but everything meant to be coming out of 1&2 doesn't work anymore like it used to in the 1st test version that I exported before adding all these routings.

If the volume is above 0dB, it will result in values over 1.0. The statement

the range is between 0 and 1

means that the domain is normalised and not measured in dB or anything else.

But yes, that scientific notation is annoying. In audio DSP if you have something this low you expect it to be zero in most cases, but I didn't write the number to string converters myself.

Because the root library folder is not visible to non admin users.

I think instead of using AUDIO_FILES you should use the {PROJECT_FOLDER} wildcard like with sample maps. That may resolve the / \ issue too. I don't have a suitable project setup to test this so let me know if it solves it.

@Alex-Paradis I don't know much about that, but I've seen recently that MPE modulators never retain their state is normal behaviour. It has to be handled by the script I think, there's something about that in the doc.

No this is intended behaviour: unlike every other module in HISE the MPE modulators will not retain their state but rely on the MPE Panel to set their parameters.

I've added some MPE chapters to the documentation but @Dominik-Mayer locked me out of the server with his weird SSH fetish so I can't update it LOL.