@Christoph-Hart Thank you very much Christoph! I really appreciate it!

@dustbro thanks for the tip with the »no-optimisation« setting! loading loops and impulses works with this on mojave.

@Lindon thanks for your time figuring it out!!!

@Christoph-Hart after working with HISE for over a year on my day off for 12-hours every week I was so frustrated by this, that i bought kontakt. believe me, i had a quite a few of this ******-moments, and i´m not a guy that easily gives up. i really love what your doing and i love the project and all the guys/girls around here, but, at in the end i want to spend time creating instruments and not fiddling around with random-settings for hours/days just to get HISE to work (again). It was a pain to get it to work the first time on mac. It was a pain getting it kinda to work on windows. It was a pain trying to get it to work after I had to update my mac to handle my dayjob. and, believe me, I delayed that os-update as long as possible.

ok, with this off my chest: do you see any chance to get this heavyweight off the shoulders of the not-so-c++sy-users, like me?

I am thinking of a HISE-build-server:

1. you connect your instruments github-repo
2. you merge your dev-branch to release-branch
3. which triggers automatic builds for any target platforms (windows, mac, and linux...)
4. you receive the links to the builds

You would use it to build new HISE-updates, which would ensure that it works. No user would have to compile HISE or their own instruments ever again.

You said once in a post: »Life/time is too precious to rebuild the pool files on every compile« which made me smile. I think: Lifetime is too precious to setup build environments at all!

Christoph, what do you think? Can i help to set something like this up? Would it be possible with something like:
https://azure.microsoft.com/de-de/services/devops/pipelines/

Cheers
Peter

@Lindon i gave it another try today, after i saw your post.
deleted and reinstalled the ipp library and compiled hise from the master-branch (downloaded today).
I am on Mojave 10.14.4.
It is still not possible to load the files into impulse-reverb and looper.
guess it´s kontakt time. : (

@dustbro thanks for checking!

@Lindon, thanks! Do you mean something like

Engine.loadAudioFilesIntoPool('{PROJECT FOLDER}/impulse.wav');

I can´t find any hint in the api, like »registering« pool-files first.
Thought this would be done »automagically« after I created »Exported Pooled Files to Binary Ressource«.

Can you please show me what I´m missing?

@Lindon it´s not working in HISE 2.1.0 itself.

I updated HISE yesterday because the impulse reverb didn't work after compiling my instrument as plugin.
I tried your great tip

Engine.loadAudioFilesIntoPool();

in my old version from February but without success.

@dustbro Did you had the time to check your 2.1.0 mac version?

same here