Just wanted to make a post to thank Christoph Hart for creating HISE. Like many other developers here, I started making sample libraries with Kontakt. I found a lot of success within this Engine and still have clients asking me to create Kontakt instruments, but I have lost a lot of passion for these projects. A friend at Spitfire actually recommended HISE to me a few months ago and I've been obsessed with learning about this incredibly versatile engine ever since. It has been a little difficult transitioning over, but it has been made significantly easier with the the built-in API reference tab, HISE documentation, active forum, and the many generous members of this community.

I plan to release my first commercial HISE-built product before the end of this month. My excitement for this release is far greater than any of my recent releases of Kontakt instruments. Thank you Christoph for creating HISE and helping me to rediscover my passion for developing sample instruments.

@gorangrooves This was exactly the issue. You are incredible. I know you posted a similar image as this in the post you linked, but I'm posting a screenshot here for anyone else that had a similar issue.

When building the AAX SDK (in my case 2.6.0), you must change the runtime library to Multi-threaded. If you don't do this, the VS project will not work. My previous solution to this problem resulted in a bloated file that could not be signed.

This change to the SDK allowed HISE to export both an AAX and VST3 with no alterations to the built VS projects. I then ran the single line of code previously recommended by @gorangrooves

I then created an executable that a friend used to install both the VST3 and AAX. They were able to load it into Pro Tools! I am officially one of the unicorns that has confirmed that a Windows-built AAX CAN be signed using an Apple Developer Certificate. Of course I did still have to go through the process of communicating with AVID and PACE to obtain the required tools and credentials for signing AAX plugins. Thank you everyone!

Issue was unrelated to HISE. The "User Preset" folder had admin privileges set to "Read-Only". Altered the settings of the installer to fix the issue.

@Gabor-K Were you ever able to find this version of the SDK? I've been searching all over for it.

@bendurso Thank You! This helped me resolve the issue. I wrote the prompt for the LinkWindows file to look inside of the samples folder instead of the samples folder itself. Everything is working great now.

@aaronventure That was it! Thank you so much.

@aaronventure My bad. I should have made that change before the previous screenshot. I was more so focused on the fact that displayed setup continuously repeats the cycle between 0 and 1 without stopping.

Let me try again to describe what I'm looking to do. The part that I'm stumped with is making the output signal stay at 0 after a single ramp cycle is complete. It should wait for a new trigger before jumping to 1 again for the set period of time. In this case of this graphic, 1 second. Sorry for the confusion.

@aaronventure Thank you for the help! Either I'm missing something or I didn't clearly explain my goal. The current setup does restart the ramp when the resetter is triggered. This is very useful, but I'm looking for the chain to output the value of 1 only for the duration of one ramp cycle. After the cycle is complete, it will default back to 0 until the resetter is triggered again.

I'm attempting to set up a system in scriptnode where a value of 1 is sent for a limited period of time, after which the value would default to 0 until the process is triggered again via a button on the interface. Is there a node or series of nodes that could do this?

Issue was unrelated to HISE. The "User Preset" folder had admin privileges set to "Read-Only". Altered the settings of the installer to fix the issue.

@d-healey That would have made sense, but that box is not ticked.

I'm currently having an issue with an instrument not allowing users to save presets on Mac. Have any of you had this issue and found a solution?

Here's some info to possibly help determine what's causing the issue:

• Instrument was made by altering one of my previous HISE projects that does not have the same issue
• Presets CAN be made on the windows build
• Presets CAN be made within HISE on mac, but not within the exported plugin
• Project has a unique Bundle ID and Plugin Code ID
• Preset browser can be used to view and load presets, but not create. "Add" button works, but no .preset file is created after inputing a name and pressing "OK".

I believe this issue is the result of a mistake I made with the project settings. Do any of you have any guesses? Your advise is much appreciated.

@aaronventure Simply updating to the latest release did fix the issue. I can now export through HISE without having to edit the auto-built Xcode project.

BUT I was reminded of why I have been sticking with the release from September 2023. I have a separate project that uses FAUST and Scriptnodes. The newer versions of HISE crashes immediately upon trying to load this project. Can't remember if it is FAUST or Scriptnodes that causes this.

Solved one issue, and rediscovered another. I'll mark this post as solved since the main focus was resolved.

@aaronventure Sorry. I meant the release in September

@aaronventure

• Mac OS 14.2.1
• Xcode 15.3
• Yes
• Yes
• No
• I believe I'm using HISE 3.6.2 with no modifications. I did have a period of time where I was trying other versions because of issues with Faust, but came back to the 3.6.2 in the end.

Is this maybe something I can fix via extra definitions in HISE's settings window?

I do not have this issue on windows, only mac.