Here's an extensive report on how to achieve this:

AU_MULTI_OUTPUT_LOGIC_PRO.txt

It worked!

This is what I changed in JUCE/modules/juce_audio_plugin_client/AU/juce_AU_Wrapper.mm

-       #ifdef JucePlugin_PreferredChannelConfigurations
+       // HISE multi-output AU support: Advertise specific supported configurations
+       #if defined(HISE_NUM_PLUGIN_CHANNELS) && HISE_NUM_PLUGIN_CHANNELS > 2
+        {
+            AUChannelInfo info;
+
+            // Advertise stereo configuration (main bus only)
+            info.inChannels = 0;
+            info.outChannels = 2;
+            channelInfo.add (info);
+
+            // Advertise full multi-output configuration (all buses)
+            // This shows in Logic as "Multi-Output" option
+            info.outChannels = -HISE_NUM_PLUGIN_CHANNELS;
+            channelInfo.add (info);
+        }
+       #elif defined(JucePlugin_PreferredChannelConfigurations)

To enable only the stereo options, like in the picture:

+            info.outChannels = HISE_NUM_PLUGIN_CHANNELS;

Thanks @dannytaurus.

It worked well on Reaper, but not in Logic.
Somehow, Logic needs to be told the output options it should offer. I've tried to use these posts you've mentioned with ChatGPT, but after trying many different things, I still couldn't figure it out.

I'm trying my plugin to have a multi-output option.

I've built HISE with these Preprocessor Definitions:

NUM_MAX_CHANNELS = 10
HISE_NUM_PLUGIN_CHANNELS = 10

I can see the multiple outputs in HISE:

But when I export the plugin, Logic only shows the Stereo options.

Does anyone know what else I need to do to enable multi-output options?

@resonant ARM64 (Windows on ARM), Windows 11, 24H2 branch (build 26100)

I've build HISE from source on Windows 11 (UTM virtual machine, Mac M1). It builds OK, but when I try to open, the cursor changes to detault/loading for a few seconds, then goes back to normal, and HISE doesn't open.

I was able to build from source on an M2 OK, but this one just doesn't open.

I've tried mulitple flags and configurations, no luck. Any clues?

Solved it. Created a junction to "remove" this 18 folder:

mklink /J "C:\Program Files\Microsoft Visual Studio\2022" "C:\Program Files\Microsoft Visual Studio\18"

I've built HISE from source, and when I clicked "Save Project and Open in IDE..." Projucer found Visual Studio no problem.

I've installed MS Build checking every single option mentioning C++.

HISE is still not recognizing MS Build installed. The path it was installed is C:\Program Files\Microsoft Visual Studio\18\Community\MSBuild, so I'm wondering if this 18 is an issue.

Any clues, anyone?

@David-Healey awesome, thanks!

@David-Healey

I've just managed to export my instrument as aaxplugin.

When I open Pro Tools (Developer Build) my plugin is not listed in the instruments list, but it's listed as instrument under the AudioSuite menu.

Any clues on how to fix this?

@David-Healey when I try to export as AAX on HISE, I get this error:

❌   "AAXStartup(IACFUnknown*)", referenced from:
❌   "AAXShutdown(IACFUnknown*)", referenced from:
❌   "AAXCanUnloadNow(IACFUnknown*)", referenced from:
❌   "AAXGetSDKVersion(unsigned long long*)", referenced from:
❌   "AAXRegisterPlugin(IACFUnknown*, IACFPluginDefinition**)", referenced from:
❌   "AAXGetClassFactory(IACFUnknown*, _acfUID const&, _acfUID const&, void**)", referenced from:
❌   "AAXRegisterComponent(IACFUnknown*, unsigned int, IACFComponentDefinition**)", referenced from:
❌ ld: symbol(s) not found for architecture x86_64
❌ clang++: linker command failed with exit code 1 (use -v to see invocation)

When I then open the Xcode project and compile it, it works. So I was wondering if there is an option in HISE to generate the Projucer and Xcode files without compiling them

@David-Healey when I try to build for AAX in HISE, I get an error, while in Xcode I can build successfully and have more control over it.

Is there a way to just generate the jucer and the xcodeproj files, without actually building them in HISE?

Hello everyone,

I have been studying HISE and developing my first plugin for the past six months, with great help from this community, especially @David-Healey and @Christoph-Hart.

I have partnered with a Brazilian Grammy winner and professional drummer to create Odara Sounds, and we are building Brazilian Percussion, a plugin host designed to receive expansion packs. The first one, which will come with the plugin, is called Brazilian Percussion 101 and features five Brazilian percussion instruments.

The main feature that I'm looking forward to hearing some feedback on, which I know some of you here won't like , is a section called Rhythms, where you can choose ready-made Audio and MIDI loops from a list, and play them by hitting one note per instrument. The idea came from the fact that Brazilian rhythms may not be easy to reproduce by non-Brazilian musicians. For now, we have created just a few MIDI rhythms, but the idea is to have that list grow exponentially.

The project is now nearing completion, and I would really appreciate some feedback.

For now, we can only export to Mac, AU and VST, unless you have a Developer Build of Pro Tools.

If you are interested, please fill out the form below. We are going to give full licenses to anyone who helps us in this early stage.

https://forms.gle/chH55ksidpecaA7Z9

PS: I'm planning to make the project open-source once it's completed.

Thanks, @David-Healey!

I'm just finishing my first plugin, so I'm new to the exporting process.

What's the difference between choosing Compile project and Export as..., apart from a different UI (one has a built-in terminal pop-up and the other opens the external terminal)?

@David-Healey I have an Utils.js file where I create abstractions for every tedious thing like this, but a native function would be useful indeed

@JamesC if I understand correctly, you want the loops to follow the DAW tempo, but the Sampler’s tempo-sync won’t time-stretch them. Wouldn’t be better to use an Audio Loop Player module instead?

@David-Healey wouldn't .get('x') and .get('y') be enough?