@d-healey

I'm facepalming so hard over here. I didn't even think to check the HISE path. I figured it would auto-fill with the location where I was building HISE from, but clearly not.

I switched to the right HISE path and it found the SDK right away. Looks like it's going to build.

Thanks!

Hello,

I'm experiencing issues with the AAX init state of my plugin. Other file types work without issue.

While I've found a few related threads, they focus on specific parameters not being set to a default value. What I am experiencing is much broader in scope.

On the first load, many of the GUI elements are not responsive. Adding EQ bands works under the hood, but don't appear. The 'randomize' buttons on my arpeggiator do randomize the corresponding settings, but it's not until you try and manually manipulate the values that the state change suddenly loads in.

There are many more similar issues which I will not detail here. They all follow the same pattern: GUI elements successfully change underlying plugin state, but do not update visually until there is some kind of manual input. A select few elements never update visually.

If I close out of the plugin window and reopen it, everything works as expected. All GUI elements update immediately. This is, as far as I can tell, the only way to resolve the issue.

I've tried rebuilding HISE from source. Using AAX SDK 2.8.1 & latest version of Pro Tools.

Any help would be greatly appreciated.

@d-healey

I'm facepalming so hard over here. I didn't even think to check the HISE path. I figured it would auto-fill with the location where I was building HISE from, but clearly not.

I switched to the right HISE path and it found the SDK right away. Looks like it's going to build.

Thanks!

@d-healey Here is the error that appears when trying to export:

The AAX SDK path in the 'Global Paths' section of Projucer is set to HISE/tools/SDK/AAX across all Projucer projects. I wasn't able to find any project-specific settings for the AAX SDK path.

@Lindon

Here is the inside of HISE/tools/SDK

And here is the full path to the .lib file

Thank you for the suggestion.

Unfortunately it's still not working. I made the changes suggested by that thread (switch 'Runtime Library' to 'Multi-Threaded (/MT) as opposed to 'Multi-threaded Dll (/MD)'.

I've tried various combinations of building HISE as debug/release, the AAX library as debug/release. I manually set the AAX SDK Path in the HISE Projucer project as well.

The LLMs are leading me in circles. No matter what I do, I continue to receive the 'AAX SDK Missing' export error.

Hello,

I am currently trying to build the Windows AAX version of my plugin. No matter what I do, I can't seem to get HISE to locate the AAX SDK. I have tried recommendations from similar threads, but to no avail. Here are the steps I have taken:

1. Unzip the AAX SDK to HISE/tools/SDK
2. Rename the unzipped directory from 'aax-sdk-2-8-1' to 'AAX'
3. Build the Visual Studio solution at AAX/Libs/AAXLibrary/WinBuild/vs/AAXLibrary.sln
4. Confirm the existence of the AAXLibrary_x64.lib file inside of AAX/Libs/Release
5. Rebuild HISE

After following these steps and trying to build my plugin, I still see an error saying the AAX SDK could not be found. Maybe I have misunderstood something, or missed a step somewhere.

Any help would be greatly appreciated.

Hello,

Is there any way in HISE to specify the AU subcategory? When adding my FX plugin to a track in Logic Pro, I currently have to navigate to Audio Units -> Developer Name -> Plugin Name. Ideally, I could also get it to appear under the Multi Effects tab.

I haven't found any relevant settings in either HISE or the corresponding Projucer project. While Projucer does contain a setting for AU category, the options are higher level in scope (i.e. effect, generator, mixer).

Am I missing something obvious? How might I go about setting this value?