Hey everyone, I’ve noticed that a lot of plugins online don’t seem to support the latest macOS version. I haven’t updated yet, so I’m wondering if anyone here has upgraded and successfully tested whether HISE-exported plugins work? Both VST and AU formats.

@Lindon Hi, pardon me! how could i save and load the midi cc value individually like a preset using this script, and i can replace the default values by right clicking midi assignment on the knob UIs. Thanks, seriously I'm willing to pay for a good solution if you don't mind.

@HISEnberg Hi, finally I've gotten back to you now. Thanks so much!

1. I don't know if I need to change something inside the HISE or JUCE project first.
   After testing it again, I found that I got some errors about "MD_DynamicRelease" issues as I exported the AAX directly from HISE. So I re-exported it by opening the autogenerated project from Juce. I fixed from "MD_DynamicRelease" to "MT_StaticRelease" in Visual Studio 2022. Then it seemed to build successfully. Now the Pro Tools DEV detected the plugin.

But I wonder if there's a way I can directly export AAX from HISE.

2. When I do it on my MacBook, I find I meet the other problem. (AAX SDK 2.4.1, HISE 4.1.0, M4, Xcode 16.1, sequoia)
   I can only compile the ARM version for the AAX plugin in Xcode, which warned me I could not compile the universal AAX for both Intel and ARM MAC.

Big thanks again, I believe that you must have experience with it.

@HISEnberg It's really nice of you.

@d-healey thanks a lot, I will watch it tomorrow!

@d-healey yes, this is for the user to load their IRS instead of right click the convolution "waveform".

Hi everyone. I dont know how to add a load button for convolution reverb to load custom IRs. could you help me?
thanks a lot!

@d-healey Thanks again, i will give it a try.

@d-healey so i need to recompile HISE so i can directly export as the Universal Binary AU plugin from HISE. Am I right? Thanks so much!

@HISEnberg Thanks Mate! Do you use the Hise 4.1.0 on Windows? I'm sure I'm having a hardtime compiling an AAX plugin, including getting it signed.

Hi Everyone.
I'm currently using an M4 Macbook to compile an AU plugin for the ARM version.
Since I don't have access to an Intel Mac, I'm wondering if I need to recompile the Intel Mac version of the AU plugin in Hise.
Any advice would be greatly appreciated!

Hi everyone! I'm currently working on compiling the AAX SDK 2.4.0 version on Windows. The process of exporting the AAX plugin format seems to go smoothly, but I haven't conducted any tests on a Mac yet.

The main issue I'm facing right now is that the Pro Tools Developer version can't detect my AAX plugin. I'm not sure which step I might have skipped during the process.

It's worth noting that I haven't signed the AAX plugin. However, I've heard from some people that the Pro Tools Developer version allows us to test unsigned AAX plugins.

Any insights or suggestions would be greatly appreciated. Thanks in advance!

@Gabor-K thanks, i dont have an intel Mac. Have no chance to test my plugin on the intel Mac. But i wonder if i recompile the HISE on the right setting to support "Standard Architectures (Apple Silicon, Intel)"...

@bendurso Thanks so much, and really kind of you

@d-healey You're awesome Thanks

I want to use midi cc to control (select) the preset i like in the preset folder by toggling my midi switch pedal, how to achieve that. Thanks guys, i have no clue. Hopefully any of you genius could help me with it dropping me a snippet!

Hello, guys!

I currently have over 100 Impulse Responses (IRs) stored in the audiofiles folder. However, this volume appears to be too large to efficiently compile into a plugin. Does anyone have experience addressing this issue? Any insights or solutions would be greatly appreciated. If possible, please drop me a
Snippet.
Thank you in advance for your help.