@Christoph-Hart Understood. Hadn't consider the length of the IR as directly proportional to the CPU consumption.
Thank you.

@Dan-Korneff Thanks for the quick reply and was just coming back to report the same thing.

I ran a test build and was surprised when it actually worked. Looks like I needed to rebuild the script as you suggested.

@Christoph-Hart ok, will do.

Is the process as simple as building the debug version in Xcode and then getting a log somewhere?

@d-healey Ah, that's the issue then! I have it working now. Thanks!

@DanH I appreciate the pointer!

I actually just figured this out with a google search and some trial and error. I'll post here in case it ends up helping anyone else in the future.

Instead of copying the whole folder I single AudioResources.dat file and created the folder with the installer.

In the "DestDir:" I used the tag {userappdata}. This allowed me to place the file in the expected located.

@gorangrooves Thanks for the detailed help on this one as well!

Just replied on my other codesigning thread and you definitely helped make this all far clearer than it was 48 hours ago!

@Christoph-Hart Tested and working as expected. Thanks again!

@optimistic You are very welcome! 🤘 I am glad to be able to contribute something here that will help others. I've gotten wonderful help over the last few years from the amazing folks here. Best of success with your products!

@Christoph-Hart Sounds good and makes sense. I think once a public version of PT is released the demand will certainly be there. I'm not sure when that will be. They are hoping for this year but could be early next.

@optimistic You need to change the name of the xml and the xml in the uidata folder, and also inside the xmls there will be references that need to be changed.

Answering my own question here as I uncover the mysteries of HISE.

On macOS holding shift while setting the routing will set the send cables.

I'm going to answer my own question for anyone looking this up in the future ...

There are two options for iLok encryption. One requires wrapping a binary that HISE creates and the other requires injecting custom code in your project but is more secure. The first option should easily be compatible with HISE and the second one I'm not so sure about it.

Likely we will end up using the first option and it is positive to see it should be possible.

@Christoph-Hart Thanks for explaining that! Makes sense and good to know

@Christoph-Hart Perfect! That did the trick. I'm now building on the macOS again.

@optimistic I wouldn't recommend taking a paid gig as your first project. HISE is very different to Kontakt, and that difference goes much deeper than scripting.

I do HISE consulting so we can definitely chat about this.

Regarding your build issues, the Develop branch is the one to use at the moment.